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

SCCM Versions - Updated


ProductRevisionReleasedService PackFeature PackVersion/BuildNotes
Systems Management Server (SMS)1.01994
Systems Management Server (SMS)1.11995
Systems Management Server (SMS)1.21996
Systems Management Server (SMS)2.01999
Systems Management Server (SMS)20032003
Systems Management Server (SMS)2003 R22006
System Center Configuration Manager (ConfigMgr)20072007Beta 14.00.5135.0000
System Center Configuration Manager (ConfigMgr)20072007RTM4.00.5931.0000
System Center Configuration Manager (ConfigMgr)20072008 (May)SP14.00.6221.1000
System Center Configuration Manager (ConfigMgr)20072010SP1KB9772034.00.6221.1193This update (KB 977203) may be run against SP1 or SP2 clients.
System Center Configuration Manager (ConfigMgr)20072008R2no changeThe R2 feature add-on requires at least SP1, and can be installed after SP2.
System Center Configuration Manager (ConfigMgr)20072009SP24.00.6487.2000
System Center Configuration Manager (ConfigMgr)20072010SP2KB9772034.00.6487.2111This update (KB 977203) may be run against SP1 or SP2 clients.
System Center Configuration Manager (ConfigMgr)20072010R34.00.6487.2157The R3 update requires SP2 Client.
System Center Configuration Manager (ConfigMgr)20072012/12/03KB27507824.00.6487.2207This SP2 update (KB 2750782) adds support for Windows 8-based client computers. Supersedes R3 update.
System Center 2012 Configuration Manager (ConfigMgr)2012
(Formerly "v.Next")		2010/05/26Beta 1
System Center 2012 Configuration Manager (ConfigMgr)20122011/03/23Beta 25.00.7561.0000
System Center 2012 Configuration Manager (ConfigMgr)20122011/10/28Release Candidate 15.00.7678.0000
System Center 2012 Configuration Manager (ConfigMgr)20122012/01/17Release Candidate 25.00.7703.0000
System Center 2012 Configuration Manager (ConfigMgr)20122012/03/31RTM5.00.7711.0000
System Center 2012 Configuration Manager (ConfigMgr)20122012/08/20Cumulative Update 15.00.7711.0200
System Center 2012 Configuration Manager (ConfigMgr)2012Cumulative Update 25.00.7711.0301
System Center 2012 Configuration Manager (ConfigMgr)20122012/09/11SP1 Beta5.00.7782.1000
System Center 2012 Configuration Manager (ConfigMgr)20122012/12/20SP15.00.7804.1000
System Center 2012 Configuration Manager (ConfigMgr)20122013/03/23SP1 Cumulative Update 1KB28172455.00.7804.1202To apply this update, you must have System Center 2012 Configuration Manager SP1 installed.

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