This article guides you through the process of creating an SCCM package to deploy an Adobe deployment package. Because both Adobe and Microsoft use the term package and because there are currently two versions of the Microsoft software in use, we use the following naming conventions for clarity in this article:
- When referring to a package created with SCCM 2007, we say SCCM package unless the context is very clear, when we may say just package.
- When referring to a package created by the Adobe® Creative Cloud™ Packager, we say Adobe deployment package or Adobe package. We never use the term package alone to mean an Adobe package.
SCCM is designed for a great variety of network configurations. The best choice of deployment configuration for the Adobe package and its product install folder is the TS option, where the Adobe package and its product install folder are placed together on the same distribution server or servers.
When you create a package for deployment in Windows, Creative Cloud Packager creates two folders in your specified Save to location, Exceptions and Build.
The Exceptions folder contains folders with installers of various kinds (EXE, AIR, MSI) that cannot be deployed using the main MSI installer (because it cannot contain an embedded installer). You must create separate SCCM installers for each of these, using instructions in the ExceptionInfo.txt file at the top level of the Exceptions folder. The folder can be empty if your package has no dependencies on other installers.
The Build folder contains an MSI file whose filename uses the Package Name that you specified, and a subfolder named Setup. The subfolders are required to run the MSI file and install the product successfully.
Note: The packages created by Creative Cloud Packager silently use the Adobe installer subsystem, which in turn uses the native Windows installer, MSI. Therefore, you cannot wrap an Adobe install package inside of a Windows package for use with MSI because Windows prohibits such a recursive use of MSI.
Creating an SCCM package is a two-step process. First create a new SCCM package, then create install and uninstall programs.
Specify the data source for the SCCM package.
On the Data Source tab:
- Select This Package Contains Source Files.
- Click Set to the right of the Source Directory field. In the Set Source Directory dialog, select the type of path you want to use (UNC or local) and browse for or type in the path to the Build folder that contains the .msi file and supporting folders. Click OK.
- On the Data Source tab, the path you just selected will show in the Source Directory field. Below that field, select Always obtain files from the source directory.
Set the other choices as appropriate, then click Next.
Specify distribution settings.
- On the Distribution Settings tab, choose a sending priority. Select the Preferred Sender, if desired. Select other settings as appropriate, then click Next.
- On the Reporting tab, select settings as appropriate, then click Next.
- On the Security tab, select settings as appropriate, then click Next.
Creative Cloud Packager generates a single MSI file in the Build folder, which you use for both installation and uninstallation of the product or suite. (Uninstall is not available for update packages, only for installation packages.)
If you want, you can create two separate SCCM programs for an installation package: one for installation and another for uninstallation. Name these programs to make it obvious to the users on the target systems who choose what the commands will do.
In the New Program wizard, specify the command line for the program.
On the General tab:
Enter a descriptive name (such as install_PS_1 or uninstall_PS_1) in the Name field, and an explanatory comment that describes what the program does.
Click Browse. In the Open File dialog, choose the file type All Files (*.*), then browse to and select the MSI/EXE file. The details of this step vary for each command you create.
For the install package, browse to your .exe file.
When you return to the New Program wizard, append appropriate flags or options to the command after the filename in the Command Line text box.
You can use the “ silent” parameter for unattended installation.
setup [--silent] [--ADOBEINSTALLDIR=] [--INSTALLLANGUAGE=]
setup.exe --silent --ADOBEINSTALLDIR="C:\InstallDir" --INSTALLLANGUAGE=fr_CA
For more details on using this command, see Deploy using command line on Windows machines.
For enabling the user interface of the installer:
- Do not specify the --silent parameter.
- Specify “Run with administrative rights” in the Run mode of the Environment tab.
For the uninstall package, browse to your .MSI file.
For the uninstall package, use the msiexec command with the /uninstall parameter.
msiexec.exe /uninstall PS_1.msi /quiet
On the Environment tab:
- In the Program Can Run field, select Whether or not a user is logged in.
- In the Run mode section, select Run with administrative rights. Be sure Allow users to interact with this program is turned OFF.
Note: If you do not choose to run with administrative rights, the Application Manager writes its log file to a different location. See “Installation logs.”
To create install and uninstall programs for the MSI, EXE, or AIR installers that are present in the Exceptions folder, use the commands described in the ExceptionInfo.txt file at the top level of the Exceptions folder.
For example, to create an SCCM install package for an MSI installer such as Adobe Flash Player 10, use this command:
msiexec.exe /i AdobeFlashPlayer10_plRel_mul.msi /qn
To create the uninstaller, use /uninstall instead of /i
msiexec.exe /uninstall AdobeFlashPlayer10_plRel_mul.msi /qn
Warning: For AIR-based installers, you can create a silent installer the same way, using the command listed in the ExceptionInfo.txt file. For these components, however, you cannot create a silent uninstaller. When uninstalling, you may need to uninstall AIR applications manually.
In the New Distribution Points wizard, select the distribution points to which you want to copy the SCCM package.
It is assumed that at this point the distribution points you want to use for this SCCM package have already been created. You can select one or more distribution points for this package.
Follow the directions in this section once for each SCCM package program you want to advertise.
These directions assume you already have a collection with target systems where you will advertise the SCCM package programs.
In the Distribute Software to Collection wizard, choose the SCCM package to advertise.
On the Package tab:
- Turn on Select an existing package.
- Click the Browse button next to the text field. In the Select a Package dialog, locate the desired SCCM package and select it. Then click OK. Your selection will appear in the text field on the Package tab.
- Click Next.
Set advertisement characteristics.
On the Advertisement Name tab:
- Enter a name for the advertisement in the Name field.
- Optionally, enter a comment that describes the advertisement in the Comment field.
- Click Next.
On the Advertisement Subcollection tab:
- The name of the collection you chose for this advertisement is displayed in the Collection field. Choose whether you want this advertisement to be sent to any subcollections of this collection. The results of your choice are displayed in the field at the bottom of the tab.
- Click Next.
On the Advertisement Schedule tab:
- Set the date and time you want the advertisement to occur.
- Specify whether the advertisement will expire. If you want it to expire, set the expiration date and time.
- Make any other settings as necessary and click Next.
On the Assign Program tab:
- Choose whether you want running this program to be mandatory. If you do, specify the date and time to force its execution. Notice the advertisement date from the previous tab is displayed here.
- Set an expiration date if you want.
- Choose other options as desired.
- Click Next.