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

Definition: Software Update point is a site system role which is used to manage patch deployment using SCCM on the endpoints in the infrastructure. It provides a robust experience and extensive options to manage and deploy software updates to computers. SCCM is integrated with WSUS. The minimum version of WSUS  supported is WSUS 3.0 SP2.

 Pre-requisites:

 1. WSUS 3.0 SP2 Minimum supported version.

 http://being-sccmadmin.blogspot.in/2013/04/installation-of-wsus-for-sccm-software.html

 2. General supported configurations for Configuration Manager 2007.

 Creating a Software Update Point:

 1. In SCCM console, go to System CenterConfiguration Manager / Site Database / Site Management / <site code> - <site name> / Site Settings / Site Systems. Click on the Server where SUP has to be installed and select "New Roles". 
 General :
Enter the  FQDN of the server and click next.


2. System Role selection:
Select " Software Update Point".

3. Software Update point: Specify the server name and port if proxy server usage is required.Click Next.

 4. Active Settings: Check the option " Use this server as the active software update point" and also specify the ports.
Recommended port numbers - 8530 and 8531
Note : We can specify these settings even after creating the software update point in  software update component configuration.

5 . Sync source :  Since this is first active software update point in the heirarchy , the sync source should be "Microsoft Update" otherwise select the "Upstream WSUS Server'.

6. Sync Schedule : Specify how often the server can synchronize with the "Microsoft update" or the "Upstream server". By default  it is  7 days.

7. Classifications :   Configure the classifications as required appropriately.



 8. Products: Select the applicable products that you want to patch.

9. Languages: Select the appropriate languages, here I have selected only English.Click Next.
10. Review the summary page and click close to complete the wizard.

 Verifying the installation of SUP:

 1. SUPSETUP.log : Check the supsetup.log file to verify whether the SUP is installed successfully or not.

 Location : Configuration manager installation Path\Logs folder

 Search string : Installation was successful.

Now that the SUP is installed, we can configure the software update point from component configuration if required to change any settings.

Comments

  1. Unknown6 April 2016 at 16:13

    When I don't how to install a software, I am lucky to have my brother beside me because he knows a lot about computer than me.
    Software Installation

    ReplyDelete
  2. Robert Gilims25 July 2019 at 11:37

    Really wonderful post! I am glad that I came across your article. Thanks for sharing. software installation near me

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