SCCM – How to Distribute Software Packages

What is a software package in Configuration Manager?

One of the primary features of System Center Configuration Manager is its ability to distribute software packages to client computers.

A software package gives an administrator the ability to systematically distribute updates to clients. The updates can be new software, command lines, registry modifications, scripts etc. This gives you the ability to centrally manage and standardise an entire network of client computers.

 

There are three components involved in a software distribution-

The package

This is the ‘what’ of the distribution and can be anything from a software package to a command line.
The package consists of four parts, the source files, the package definition, the program and the distribution points.

The collection

This is the ‘who’ of the distribution and is where you specify who receives the update. Normally we would target workstation computers, but you can also target groups or particular users. These are defined by “membership criteria” within the collection and for the update to be received the client must meet one or more of the criteria.

The advertisement

This is the ‘when’ of the distribution and is how you specify when the update runs. The advertisement is a process of applying a specific package to a specific collection. Advertisements can be set to start as soon as possible or at some point in the future and can be set to expire at a specific time.

Note:

The following steps will detail how to create a software package. It will add the software to the ‘Run Advertised Programs’ list in control panel of each of the targeted client computers.

If you want the software to install automatically on the client computer, continue through to ‘How to set a mandatory assignment’

 

 

Step1: Creating the Package

Source Files:

Source files are the installation files for the package. You will need to save these files to a shared folder which can be access by the Configuration Manager computer account.

In this example our source files will be saved to \SCCMSEVERSMS_Source

Before you can create the package, you will need to obtain the required .exe or .msi files for the installation. You will also need to know the installation switches to use to make the installation automated. If you are unsure where to get the files or how to do a silent install see http://itsupportguides.com/configmgr-sccm.html or http://www.appdeploy.com

In this example we will be creating a software package for Mozilla Firefox 3.6

The source file has already been downloaded and saved the source folder, which will be \SCCMSERVERSMS_SOURCEMozillaFirefox3.6

 

  1. Open the System Centre  Configuration Manager console
  2. Expand ‘Computer Management’
  3. Expand ‘Software Distribution’
  4. Expand ‘Packages’
  5. Right Click on the folder which corresponds to your software update. (e.g. Mozilla)
  6. Select ‘New’ and then ‘Package’
  7. SCCM-DistributePackage1
  8. Enter in the required information
  9. SCCM-DistributePackage2
  10. Click ‘Next’
  11. Select ‘This package contains source files’
  12. Click on ‘Set’ and browse to the source file folder
  13. SCCM-DistributePackage3
  14. Click ‘OK’ and ‘OK’ again
  15. Click ‘Finish’, ‘Next’ and then ‘Close’.

 

Step 2: Create the program

  1. Expand the new package, right click on ‘Program’ and select ‘New’ then ‘Program’
  2. SCCM-DistributePackage4
  3. Enter in the same name as the package (e.g. Mozilla Firefox 3.6)
  4. Under ‘Command line’ enter in the command which starts the installation (e.g. install.cmd )
  5. Under ‘Run’ select ‘Hidden’
  6. SCCM-DistributePackage5
  7. Click ‘Next’
  8. Enter in an estimate required disk space (e.g. 20 MB)
  9. Select ‘This program can run only on specified client platforms’ and select the required platforms, e.g.
    • All x64 Windows 7
    • All x64 Windows Vista
    • All x64 Windows XP Professional
    • All x86 Windows 7
    • All x86 Windows Vista
    • All x86 Windows XP Professional

SCCM-DistributePackage6

  1. Click ‘Next’
  2. Under ‘Program can run:’ select ‘Whether or not a user is logged on’
  3. Click ‘Next’, ‘Next’, ‘Next’, ‘Next’, ‘Next’ and then ‘Close’.

 

Step 3: Distribute the software

 

  1. Right click on the package and select ‘Distribute’ and then ‘Software’
  2. SCCM-DistributePackage7
  3. Click ‘Next’
  4. SCCM-DistributePackage8
  5. Click ‘Select All’ and then ‘Next’
  6. When asked ‘Do you want to create a program from this package’ select ‘No’
  7. Select ‘Finish’, ‘Next’ and then ‘Close’

 

Step 4: Create advertisement

 

  1. Expand ‘Advertisements’ and right click on the relevant folder (e.g. Mozilla)
  2. Select ‘New’ and then ‘Advertisement’
  3. SCCM-DistributePackage9
  4. Under ‘Name’ enter in the name of the advertisement (e.g. Mozilla Firefox 3.6)
  5. Under ‘Package’ select ‘Browse’ and select the relevant package (e.g. Mozilla Firefox 3.6)
  6. Click ‘OK’
  7. Under ‘Collection’ select ‘Browse’ and select the targeted collection
  8. Click ‘OK’
  9. SCCM-DistributePackage10
  10. Click ‘Next’
  11. Click ‘Next’
  12. For both options select ‘Download content from distribution point and run locally’
  13. Click ‘Next’, ‘Next’, ‘Next’, ‘Next’, and then ‘Close’

 

Step 5 (optional): How to set a mandatory assignment

Mandatory assignments are used to force the package to install automatically at a selected time.

With a mandatory assignment the package will start to run at the indicated time, which can be As Soon As Possible or a given time.

 

  1. Open the System Centre Configuration Manager console.
  2. Expand ‘Computer Management’
  3. Expand ‘Software Distribution’
  4. Expand ‘Advertisments’
  5. Open the required container, (e.g.Mozilla)
  6. Double click on the advertisement, (e.g. Mozilla Firefox 3.6)
  7. Under ‘Collection’ select ‘Browse’
  8. From the list, select the ‘All Windows Workstations or Professional Systems’ collection and click ‘OK’
  9. Select the ‘Schedule’ tab
  10. Click on the yellow star icon
  11. Either select a start time or choose ‘Assign immediately after this event’ and then ‘As soon as possible’
  12. SCCM-DistributePackage11
  13. Click on ‘OK’ to save the changes

Tagged in

11 comments on “SCCM – How to Distribute Software Packages

  1. [quote name=”florin”]One problem: I have to deploy a package in 3 different locations – 3 distribution points – one collection that include computers from all 3 locations.
    How can I make sure that computers from one site will access only the distribution point from their location and not go through global wan to another site distribution point? So how can I tell computers to use only a specific distribution point?[/quote]

    Create a Protected Distribution Point Point so that your clients will only download packages to ther assigned distribution points.

  2. [quote name=”florin”]One problem: I have to deploy a package in 3 different locations – 3 distribution points – one collection that include computers from all 3 locations.
    How can I make sure that computers from one site will access only the distribution point from their location and not go through global wan to another site distribution point? So how can I tell computers to use only a specific distribution point?[/quote]

    Setup boundaries.

  3. One problem: I have to deploy a package in 3 different locations – 3 distribution points – one collection that include computers from all 3 locations.
    How can I make sure that computers from one site will access only the distribution point from their location and not go through global wan to another site distribution point? So how can I tell computers to use only a specific distribution point?

  4. Zack,
    this depends on the package type. and if it has a uninstall ability. most MSI based installs have the ability but not all do.
    you would have to investigate each product.
    the uninstall registry keys can help

    HKLMSOFTWAREMicrosoftWindowsCurrentVersionUninstall

    sometime adding a /QN to the commnad is all you need for a silent uninstall script

Leave a Comment

Your email address will not be published. Required fields are marked *