System Center Essentials 2007 Wiki

Software Deployment Using System Center Essentials

Using SCE you can deploy software to client and server computers from a centralized source.  You can create a software package, then deploy it to specified groups of computers.  There are different instructions for deploying different types of software packages.  Be sure you understand what type of package you are deploying before trying a deployment.  The answers to the following questions will tell you which process you should follow:

1.  The "setup" file for your software package, does it have a .EXE extension (for example, Setup.exe)?

A.) Yes - Go to question #2.

B.) No - Use the MSI-based instructions

2.  If your setup file has a .EXE file extenstion, does it also have files with a .MSI extension in the setup folder?

A.) Yes - Use the EXE-wrapped-MSI instructions

B.) No - Use the EXE-based instructions

 

Deploying .MSI Software Packages

In this scenario we will deploy Microsoft’s Anti-spyware application (Windows Defender) to a group of computers in your company.  To prepare for this scenario, navigate here and download the MSI Setup for Windows Defender:

http://www.microsoft.com/athome/security/spyware/software/default.mspx

Click “Download it here” and follow the steps to download the software package.

1. Navigate to the “Software Space” and click on “New Software Package”
2. Browse for the “WindowsDefender.MSI” you just downloaded.
3. Verify the name of the software package is correct and provide a description.  For MSI files, the name of the software package should be automatically detected and populated for you, verify this is correct.
4. Verify the size of your software package
5. Verify the contents of your software package
6. Since the software setup is self-contained, uncheck the checkbox “Include files and folders…”
7. On the following screen, specify the following installation parameter:   /quiet

8. Complete the wizard to create the package and verify the package was created successfully. Once the package is created, check the option to approve for install for the group that was created in previous exercises.
9. Specify the computer group which should receive this package and click “OK”.

Deploying .EXE Software Packages

This scenario will assist you in deploying software packages to your client and server computers.  To prepare for this exercise, download a software package which contains a Setup program that has a .EXE file extension (for example Winzip www.winzip.com). 

In this example, we will use the trial version of Winzip and deploy it to desktops.

1. Download the Winzip Evaluation Version from the following location: http://www.winzip.com/downwzeval.htm?wzdm
2. Install Winzip on the local machine (this is required to extract the proper deployment files, and is not typically necessary for installation packages).
3. Navigate to the “Software Space” by clicking “Software” in the lower left-hand corner of the console.
4. Click on “New Software Package” on the Overview page.
5. Browse for the setup file for your software application, in this example, the Winzip setup file can be located in your “Program Files\Winzip\” directory. 
6. Choose your setup file (Winzip32.exe)
7. Give your software package an name and description, example: “Winzip Test Deployment”
8. Make sure the “Include files and folders” option is selected on the first screen.
9. On the following screen, specify any command-line parameters to install your software package silently.  Your software manufacturer can provide you with the commands you will need to specify a “silent” or “unattended” install.  Common parameters are “/s” or “/qn”.  In the Winzip example, the silent install parameter is “/autoinstall”  (without the quotes).
10. Complete the wizard to create the package and verify the package was created successfully. Once the package is created, check the option to approve for install for the group that was created in previous exercises.

Deploying EXE-wrapped-MSI Software Packages (such as Office 2003)

 

Site

Changes
Index
Search

 

User

 

Log In

 
 

Last Modified 9/29/06 1:34 PM