Skip to main content

Software Update Management- SCCM 2012

The below post explains the end to end process of software updates management in SCCM 2012 Pre-requisites: 1.  WSUS Server (WSUS 3.0 SP2 ) should be installed on the SCCM site server or if you want to install WSUS on another server, it is important that you install WSUS administration console as the SCCM Server uses API. This  link explains the step by step procedure to install WSUS 3.0 SP2 2. Install SUP-Software Update Point on the SCCM Server . 3. Reporting Services Point: Install reporting services point role as described in this link . 4. Client agent: The software update client agent should be enabled(will be enabled by default) and the settings have to specified as per the requirement. On SCCM console, go to Administration>Site Configuration>Client settings>Right click on Default client settings> Click on Properties. If required, we can create custom client settings and then enable client settings for that settings. ...

Creating a Collection in SCCM 2012

The good thing about collections in SCCM 2012 is we have separate nodes for Users and Devices Collections helping us to segregate in a better way. There is a new node called “Assets and Compliance” that deals with the users, systems, metering and compliance settings.
While creating collections, we now have an option to include or exclude certain collections from the newly created collection. This is highly useful when you have to maintain an infrastructure where there are validated machines and the management doesn’t want to bring those machines under the radar.
Here, I am creating a device collection that consists of Windows 7 operating system machines.

1.Go to Assets and Compliance> Right click on Device collections> Click on Create Device collection.



2.   General tab:
Enter the collection name: here it is “All Windows 7 Systems”
Enter description, and most importantly click on browse and select a limiting collection.
Limiting collection has to be specified in CM 2012 to create a collection, it is mandatory.
Click Next.



3.  Membership rules:

Click on “Add Rule”, there are 4 options
·         Direct Rule- equivalent of “direct membership rule in SCCM 2007”
·         Query Rule- creating collection based on a “query or criteria”
·         Include collections: we can include collection using this option
·         Exclude collections: we can exclude collection using this option.

“Dynamically add resources” that was available in SCCM 2007 has been changed to “Use incremental updates for this collection”.
            Schedule a full update as desired



4. Query rule properties:

Enter the query rule name. Here it is “Windows 7 System”
Select the resource class; here I have selected “system resource”.
Click on Edit query statement to write a query or define a criterion.
Click on “Show query language” to write a query or click on “criteria” to define a criterion.



5.  Enter the query statement in query language as shown. 
     Click OK and click next
         Here, I am creating a windows 7 collection and so the below query is used.
         We can also use “criteria” method if we are not sure of the query.


Review summary and click Next to proceed. Click on Close to complete the wizard.

6. The collection is created now and available under “Device collections” node as shown.
Right click on the collection and click on “show members” to see the computers that are part of this collection.






Comments

Popular posts from this blog

Software Update Management- SCCM 2012

The below post explains the end to end process of software updates management in SCCM 2012 Pre-requisites: 1.  WSUS Server (WSUS 3.0 SP2 ) should be installed on the SCCM site server or if you want to install WSUS on another server, it is important that you install WSUS administration console as the SCCM Server uses API. This  link explains the step by step procedure to install WSUS 3.0 SP2 2. Install SUP-Software Update Point on the SCCM Server . 3. Reporting Services Point: Install reporting services point role as described in this link . 4. Client agent: The software update client agent should be enabled(will be enabled by default) and the settings have to specified as per the requirement. On SCCM console, go to Administration>Site Configuration>Client settings>Right click on Default client settings> Click on Properties. If required, we can create custom client settings and then enable client settings for that settings. ...

Operating System Deployment-SCCM 2007 Step By Step Procedure

This post explains the step by step by procedure (flow) to build, capture and deploy Operating System to a bare metal machine. It covers: A] Preparing SCCM Server for OSD B] Building and capturing OS image C] Deploying Operating Systems. There are two methods to capture OS image. a] Using Task sequence to capture  the OS from a reference machine.(Automating BUILD as well) b] Using Manual method.( build an operating system and then capture using SCCM) Here, I am building and capturing the image through Task Sequence. And also not using any USMT to migrate data since it is a plain bare metal deployment, not an upgrade. A]. Preparing SCCM Server for OSD: 1. Install WDS server role WDS 2. Install and configure PXE service point. PXE Service Point 3. General Supported Configurations. 4. Create and set Network access account.  5. Create and distribute the Configuration Manager 2007 package, all the relevant KB updates as packages. This post helps to create...

Consistency validation for SQL Server registry keys failed error -SQL for SCCM

During installation of SQL server, "Consistency validation for SQL Server registry keys failed” error pops up in the below scenarios. 1.   Previous installation of SQL exists. 2.   Inappropriate permissions on the registry keys of Microsoft SQL server. Solution that worked me is explained below. A. Identify the issue: 1. Go to %Program Files%\Microsoft SQL Server\100\SetupBootstrap\Log\”date  and time of installation” 2. Search (in Detail_GlobalRules.txt) for lines containing the following string "Could not fix registry key" 3. Run “regedit”, s et full control permissions for the appropriate registry keys mentioned in "Detail_GlobalRules.txt" file. Re-run the installation. B. Modifying the registry: 1. Locate HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server in registry. (To open registry, run “regedit”) 2. Right click and go to Permission 3. Click on Advance tab and c heck the below options.     i. Include i...