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. Unde

Collections-SCCM 2007


This article is a step by step procedure to create collections in SCCM 2007.

Definition:

Collections are nothing but the logical grouping of resources like computers or users. For example, if we need to target only Windows 7 machines for software distribution; we can create a group of Windows 7 machines with some logic or query and use this group( called collection) to be targeted for software distribution.

We can create collections in two ways:


A]       Query based collection-

Query-based membership is a dynamic method, meaning that you do not define the resources that are to be members of the collections; rather, you define the rules by which those members are placed in the collections. These rules form a query, and Configuration Manager periodically reruns the query to keep the collection up to date.


B]       Direct rule membership-

Direct membership is a manual membership method, meaning that you specifically define which resources are to be members of the collection. As a result, direct membership collections must updated manually as new resources are added or removed.
We can also create collections within collections and these are called as “sub collections”.

Pre-defined collections:

There are  17 default pre-defined collections available in SCCM 2007 SP2 R3 version with “All Unknown Computers” collection being added with the R3 release.
Pre-defined collections cannot be modified from Child sites.

Creating Collections:

A] Query Based Collection:

1. In the Configuration Manager console, navigate to System CenterConfiguration Manager / Site Database / Computer Management
From Collections Actions menu click NewCollection. A new collection wizard will open up, enter the collection name and description.


  2.Click on ‘yellow’ colored button as shown that will pop up “query rule properties” window where you can enter the appropriate name and query.
Here, I am creating a collection based on the query to find out all the Windows XP machines.

There are few other points to note here
·     Update this collection on a schedule-when this option is checked, it will update the collection on the specified schedule
·     Dynamically add resources- this option is new in SCCM 2007 R3. When this option is checked, the collection will be dynamically add resources as and when the requirement is met with the query
·     Limit to collection: We can limit the collection to other collections so that the resources are discovered only in the limited collection.
·     Enter the query rule name :
·     Click on Edit Query Statement to proceed further.


3. Click on “show query language” to input the query.




4. Enter the appropriate query:

Here, the query is to find out the machines with the Windows XP Operating system.
Click OK, click Next , next , next and close the wizard





5.Update Collection membership:

After the collection is created, we need to update the collection so that the collection is populated with the resources.

Here, the Windows XP machine in the lab is appearing once I updated the collection membership.




B] Direct rule membership-


1. In the Configuration Manager console, navigate to System CenterConfiguration Manager / Site Database / Computer Management
From Collections Actions menu click NewCollection. A new collection wizard will open up, enter the collection name and description.

2. Click on ‘blue computer icon’ to open the “create direct membership rule wizard”. Optionally, you can check the ‘update this collection on a schedule’ to update the collection created on a scheduled time. 

Click next on the “Create Direct Membership Rule Wizard”.






3. Search for resources:

Depending on the requirement, we can select the “Resource Class”. Here, I am trying to create a collection that has all Windows XP machines. The resource class selected is “System Resource”

Attributes: There are lots of attributes that can be used to search for the resources like AD Site, status of the resource, IP address. Here, I have selected “NetBIOS Name”

Value: enter the appropriate value for the attribute selected. Click next.





4. Collection Limiting: If you do not have sufficient permissions on the entire database, limiting to a collection on which we have permission helps find the resources.

This helps us to limit the collection to target only the specified collection mentioned.

Here, I am limiting it o “All Windows XP Systems” collection.



5. Select Resources: Based on the criteria selected in the “Search for Resources” window, the resources will appear here.

Since, I have criteria to get Windows XP machines, “WINXP” machine is populated as shown. Select all, click next and Click Finish to close the wizard.

Then it is just next, next, next and close. If required, the security settings can be reviewed.


Dont forget to update the collection membership after the creation of the collection. The collection will not populate with resources unless it is updated.

Comments

Popular posts from this blog

Registering SPN for SQL Server for SCCM

If using a domain account to install SQL server 2008 R2 for SCCM, you have to register a SPN (Service Principal Name) in Active Directory for that domain account. Two SPNs for the account should be registered,     1. For NETBIOS name of the SQL Server     2. For the FQDN of SQL server. The procedure to do that is as follows 1. Log on to a domain controller; open a command prompt with administrative privileges. 2. Type the below commands replacing SQL server name. setspn –A MSSQLSvc/< SQL Server NETBIOS name >:1433<Domain\Account> setspn –A MSSQLSvc/< SQL Server FQDN >:1433 <Domain\Account> 3. As shown in the below screenshot, the server name here is  CM2012 for NETBIOS name and CM2012.CONTOSO.COM 4.  Verify the registration of SPN by typing the below command Setspn –L  <domain\account>

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

Collection query to find Machines--based on GUID Criteria

You can use the below SQL query to create a new collection based on GUID. select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.SMBIOSGUID = " 18764D56-C91F-83A5-51FB-4AD4B6699D04 " Replace the GUID with the one that you intend to delete. This is particularly useful when performing OSD related tasks. To know how to create a collection , go through this link .