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

Upgrading from SCCM 2012 R2 SP1 to SCCM 1702

SCCM 1702 is a baseline version now, we can upgrade directly from below versions:
  • System Center 2012 Configuration Manager with Service Pack 1
  • System Center 2012 Configuration Manager with Service Pack 2
  • System Center 2012 R2 Configuration Manager
  • System Center 2012 R2 Configuration Manager with Service Pack 1
Prerequisites:
Install ADK 10
General prerequisites will already be met as it is an upgrade. 
Note:Perform a backup of the site and disable backup site server and other maintenance tasks.

 Following are no longer supported in SCCM 1702
Windows Server 2008/2008R2 except for DPs
SQL Server 2008R2

Supported OS and DB versions:
Microsoft checklist


 Installation:

Download SCCM 1702 from Microsoft site, extract the contents and double click on splash.hta
Click on Install.



Click Next



 Select upgrade Configuration site and Click Next 

Choose options appropriately.





Click Next and download prerequisite files or use previously downloaded files

Select required langauges

Click Next on Diagnostic and Usage data



Select Skip this for now, will add service connection point later.
Note: We can do it during the installation as well, I have chosen to do it later after the installation.


See that it is mentioned as upgrade and select next
Reviews warnings and Errors- warnings can be fixed later after installation as well

Click on Begin Install
Review configmgrsetup.log file for any issues or errors.
It will take around 30-45 minutes to complete the upgrade. Click close after verifying the log file.


The site has been upgraded to SCCM 1702          
Version: 5.00.8498.1000 






Post Installation tasks

Installing Service connection point:
This is a new site system role for updating the SCCM Current branch and other features. 
More info on Microsoft site- Service connection point

Select online persistent
Click next and click close on completion summary window
Now, you can check updates from Updates and Servicing as shown below
Review monitoring and check dmpdownloader.log & hman log files for any issues.

 Review database replication for any issues under Monitoring> Database replication


You can use replication analyzer tool as well for any issues.

Labels:

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