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
4 comments

Installation of Software Update Point-SCCM 2012

Below steps explain the installation and verification of SUP creation in SCCM 2012 SP1

 Pre-requisites:

1. WSUS 3.0 SP2 Minimum supported version.

Link

 2. The below patches have to be installed after WSUS SP2 installation

      WSUS-KB2720211

      WSUS-KB2734608

 3. General supported configurations for Configuration Manager 2007.

 Creating a Software Update Point:

 1. On SCCM Console,go to Administration>>>Site Configuration>>>>Sites>>>>Right click and select “Add site system roles”.



2. On General tab, select the server that has to be set up as SUP and verify or enter the active directory forest & domain.Click Next.
3. Proxy: Enter proxy address if required.

4. System role selection: 

Here, select Software update point site system role.


5. Specify Software update settings:

Select the option with the ports 8530 and 8531, click next.



6. Proxy and account settings:

Use a proxy if required to synchronize from a proxy server.Here, it is not selected.Click Next.


7. Synchronization source:

If it is the first site in the infra, select first option " Synchronize from Microsoft update" or accordingly select upstream server if it is a child site.


8. Synchronization schedule:

Select "enable synchronization on a schedule" and leave default 7 days. Click Next.



9. Supersedence rules:

This tab is a new one in SCCM 2012 that helps to delete expired updates automatically after specified duration of time. In this case , 3 months as shown in the below screenshot.


10. Classifications:

Select the appropriate options to download critical, security and other updates and update roll ups.


11. Products:

Select the products and click next.


12. Languages: select the required languages.



13. Summary : Review the summary and click on Next.



14. Click Close to complete the wizard.



Verification of installation of SUP:

1. Under the Configuration manager installation directory, logs folder, check for supsetup.log file.

It would say "Installation was successful" or provides any errors in case of any issues.



2. WCM log file

Provides information about the software update point configuration and connecting to the Windows Server Update Services (WSUS) server for subscribed update categories, classifications, and languages.
Search string : Successfully connected to server. Verify upstream server etc..Location: Configuration manager Installation Directory/ Logs folder



3. WSUSCTRL.LOG 

Provides information about the configuration, database connectivity, and health of the WSUS server for the site.
Search string: "There are no unhealthy components"
Location: Configuration manager Installation Directory/ Logs folder


To configure Software update point at a latter stage, we have to browse through the below path to configure the SUP,

On console, Site configuration>Sites>Right click on the site> Configure components> Software update point.

We can modify products, classifications, language or sync settings from here.






Comments

Post a Comment

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>
1 comment
Read more

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
6 comments
Read more

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 .
3 comments
Read more