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

Software Distribution-SCCM 2007


This article addresses the step by step procedure for Software distribution feature in SCCM 2007 .

Software Distribution Process
Pre-requisites:

1. There should be an installation media or Network installation share of the software that has to be advertised.
2. Appropriate permissions are required to perform the following actions.


A] Creating a collection of Target systems
B] Creating a package for software distribution.
C] Creating one or more programs specific to the package.
D] Distribute the packages to the required distribution points
E] Advertise the programs to the systems of the collection created in the 1st step.

A] Creating a collection of target systems :

Create a collection as per the requirements. You can use this post to understand how to create a collection.

B] Creating a package for software distribution.

1. On SCCM console, go to Software Distribution node, right click on Packages and select New -> Package. The New Package Wizard will start. Enter the required information.
       Here, I am creating a package of Microsoft SCCM log viewer ' Trace32'




2. On Data Source tab, check This package contains source files and click Set to select a source directory. On Set Source Directory window, select the appropriate path. Following is an example to select a network share as a source: \\sccm1\sw\trace32.
Select “Use a compressed copy...“option to use the compressed copy of the package when updating distribution points later.
Enable “Binary differential compression" option.
If the package has to stay in the cache on the client system, check "persist content in the client cache".
Note that, by default content in the cache will be deleted after 24 hours.( i.e. after the program is  run on the client system)


3. On Data Access tab Select Access the distribution folder through common ConfigMgr package share.
Common ConfigMgr Package share is nothing but SMSPKG(Drive letter)$  like 
SMSPKGE$ where E is the drive letter. It stores  all the packages that are distributed.
Additional information:
SMSPKG folder contains the compressed packages
SMSPKG(drive letter)$ and SMSPKG are different folders.


4. Set the sending priority of this package between other packages when advertising multiple packages to a same collection. The priority will be ignored if a collection is expecting to receive only one package at a time.
The three types of levels are:
High, medium and low. Here, the default one 'Medium' is selected.


5. Select the default Use package properties for status MIF matching.


6. The next screen will show the security rights for this package. Click next
Summary page will appear next. Click Next.
SCCM will process the new package creating and you will see the Wizard Completed page.



C] Creating programs specific to the package:

Go to the package created -> right click on Programs -> new -> program 
Name the program, and click on browse. Browse to the location of the installable and choose the executable that you intend to run. Click open.

Choose how you would want the installation to be carried out. In this case we have chosen “Normal” option. Click next.



Requirements: Enter the estimated disk space that is required to run the program and the time limit for the program to run.
And also specify the platform on which the program can be run, there are various supported client platforms available to use.

Here, I have specified the estimated disk space as 2 MB ,the time limit as 2 hours and the compatibility for all the platforms.


Specify conditions for running the program. In this case I choose “Whether or not the user is logged on” and “run with administrative rights” options. Choose these options at your own discretion to meet organizational requirements. Click next. 


In the advance settings, below options are available.

· Run another program first- if we need to run another program before running the current program, this option can be checked and the appropriate package can be selected.

· Suppress program notifications- the program notification can be suppressed on the advertised clients.

· Disable this program…: this program can be disabled on the advertised clients.

· Allow this program to be installed using task sequence….. : When this option is selected, the program can be advertised using Task sequence.
Here, we are not running any program first and the programs are also not suppressed.
Click next, since this application is not .msi file, I am skipping this. Click Next.




On the MOM maintenance mode, check the options if there are monitoring setup.




Click Next and Click Close to complete the creation of the program.


D] Distribute the packages to the required distribution points

Go to the package created -> Distribution Points-> Manage Distribution Points-> select “Copy the package to new distribution points” option.



Select all or Select the specific distribution points that you want to copy the package to.


Click Next and Verify the Package name:


Check the summary and click on close to complete the Distribution.



E] Advertise the programs to the systems of the collection created in the 1st step.

Go to site database -> Computer management -> Software Distribution -> Advertisements -> Browse to the appropriate sub folder or create e new one if needed. Here we have “Test Advertisement” folder. Right click on the folder-> new -> Advertisement.

New Advertisement Wizard will open up as shown below. Enter the appropriate name, browse through the packages & select appropriate package (program will be auto populated)

Select the specific collection that has to be targeted; here we are targeting ‘All Windows XP Systems’. Click Next.


Schedule

On Schedule, we specify the “when” of a program. We can specify the following settings on this tab.

1. Advertisement start time: mention at what time the advertisement should start

2. Advertisement expiry: mention the time of advertisement expiration.

3. Mandatory assignment: After a specific period of time or ASAP, we can make the advertisement run mandatorily. This helps in keeping the computer compliance levels and thwarting any virus or malware attacks.

4. Enable WOL: Wake on LAN allows us to wake up the computer at specific time if power management feature is enabled.

5. Priority: Three levels- low, medium and high are available, select as per the requirements.

6. Program re-run behaviour helps in running the program as desired.

We can also schedule to run the program ignoring maintenance windows and allowing system restart outside maintenance windows.



Distribution Points:

On Distribution Point tab, we specify how the program will run. Whether the program can run locally after the download or run directly from distribution point in fast and slow boundaries.
We can also specify whether the clients can fall back to unprotected DP’s when the content is unavailable.





Interaction
Here, we can specify how the users will interact with the program. Check the required selections and proceed by clicking next.


Click Next, review the security, review the summary and then finally click on close to complete the advertisement process.

Once this software distribution process is complete, we have to check for the status on the above mentioned package, program and advertisement components to ensure that the software distribution is happening as desired.
The detailed troubleshooting, logs and status checking will be published in the coming articles.

Comments

  1. Excellent procedures, I used this blog as a reference of a Program I recently configured and Advertised on SCCM 2007..Thank you for the confirmation..

    ReplyDelete
  2. Wonderful blog! I found it while browsing on Yahoo News.
    Do you have any suggestions on how to get listed in Yahoo News?
    I've been trying for a while but I never seem to get there!
    Thank you

    My blog; menuisier colmar

    ReplyDelete
  3. Appriciate your Efforts!!!!!
    Its very much easy after reading and understanding each option.
    Thank you very much and keep posting such a wonderful blog!!!!

    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

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 .