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

How to create SCCM 2007 Client Package

To deploy SCCM 2007 Client agent using software distribution or OSD, we have to create a package for it.
As the client source files already exists on the server, we have an option called " Package from Defintion" on the software distribution >> packages node. This "Package from definition" can be used to create the SCCM 2007 Client package.
There is no need to create  additional program, it will be created automatically and just needs to be distributed to DP's for installing on clients.
The program name that will be created is " Advanced Client Silent Upgrade". We can further customize this program to suit the organizational requirements.

Creating the SCCM Client package:

The procedure to create SCCM 2007 client package :

1. In the SCCM 2007 Console, go to Site Database / Computer Management / Software Distribution/ Packages node> Right click on it and select " Package from definition" as shown.


2. On Create Package from Definition Wizard”, Welcome screen, click Next.On the “Package Definition” screen, select the Configuration Manager Client Upgrade definition and click Next.


3. On the source files,select “Always obtain files from a source directory” and then click Next.


4. On the Source Directory screen, select Network Path and browse to <ConfigMgr Installation Folder>\Client and then click Next.



Click Finish on the next summary screen and the SCCM 2007 Client package is created successfully.

Distributing the Client Package:

Once the client package is created, we have to distribute it to all the available DP's. Steps to do that :

1. In the ConfigMgr console, expand the package for the Configuration Manager Client Upgrade, right-click the Distribution Points node, and select New Distribution Points. 
2. On the New Distribution Points wizard, click Next.
3. On Copy package tab, select all the available DP's where the package has to be distributed.
4. Click Close on the "confirmation screen" to complete the distribution.




distmgr.log is useful to check whether the package has been distributed successfully or not. We can also check the package status from the Package status node under the same package or "System status " node.


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>

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

Checking MSXML Version

Below steps explain on how to check the version of the MSXML 1.        Go to Run , type “%windir%\System32” 2.        Search for the dll file “msxml(NUMBER).dll”, right click on it and select properties. (Where number= the version ,   check for the highest number available in system32 folder) 3.        Click on Details tab, it will show the version of the MSXML. Here, the product version is 6.30.7601.17988. The minimum MSXML version should be 6.0.3883.0 for SCCM .