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

Installation of WSUS for SCCM Software Update Point

This article explains the steps on how to install WSUS for SCCM.

Pre-requisites for Installing WSUS:

1. IIS 6.0 or later versions
2. .Net framework 2.0 or later versions
3. MMC 3.0
4. Windows Internal Database

Before software update point can successfully be installed and configured on a site system server in Configuration Manager 2007, Windows Server Update Services (WSUS) 3.0 must be installed on the server.

WSUS Software Download link:

http://www.microsoft.com/en-us/download/details.aspx?id=5216

Download the appropriate 32 bit or 64 bit WSUS software.

Installation:

1. Initiate the WSUS SP2 application from the media.


2. Click Next, select Full server installation including Administration Console, and then click Next.


3. Click I accept the terms of the License agreement, and then click Next.


4.Select Store updates locally, specify the path, and then click Next.

   Here the path used is WSUS folder in E Drive.

5.Select “Install Windows Internal Database on this computer” and specify path to install WSUS. Here it is again E:\WSUS


6.Specify whether to use the existing Internet Information Services (IIS) Default Web site or to create a custom WSUS 3.0 Web site. When using the WSUS server for a software update point, it is recommended that Create a Windows Server Update Services 3.0 Web site is selected. By default, the custom WSUS Web site uses HTTP port 8530 and HTTPS (SSL) port 8531. Click Next.
Here, I have selected Create a Windows Server Update Services 3.0 Web site



7. Review the specified settings, and then click Next. When the wizard completes, click Finish.



Notes:

1.The WSUS 3.0 configuration wizard automatically starts after the Setup wizard completes. Because Configuration Manager 2007 manages the WSUS settings, you should exit the configuration wizard after it opens.

2.When the active software update point for a site is installed on a remote site system server, the WSUS 3.0 Administration Console must be installed on the site server.

Reference: http://technet.microsoft.com/en-us/library/bb693980.aspx








Comments

  1. Hi Santhosh,

    I am Sujith, hope you are doing good, Just need your help on Wsus synchronization part, I have configured SUS in my centeral server & I have configured the same with a valid user credentials (Via Proxy).I can also see the Wsus is successfully synchronizing with micrsoft & I can see all the details of MS Updates.But Unfortuanately Its is not snchronizing with SCCM console even after applying 'run synchronization' option. When I checked Syncmanager logs it just says 'Sync failed, Wsus not configured' status msg ID 6703", I have checked & verified IIS part but still no luck. Any suggestion on the same please...(SCCM2007)

    ReplyDelete

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>

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 .