Share via

  • Article

How to Create Packages and Programs in Configuration Manager

 

Updated: May 14, 2015

Applies To: System Center 2012 Configuration Manager, System Center 2012 Configuration Manager SP1, System Center 2012 Configuration Manager SP2, System Center 2012 R2 Configuration Manager, System Center 2012 R2 Configuration Manager SP1

You can create or import a Microsoft System Center 2012 Configuration Manager package and program by using one of the following procedures in this topic:

  • How to Create a Package and Program by using the Create Package and Program Wizard

  • How to Create a Package and Program from a Package Definition File

  • How to Import a Package and Program

How to Create a Package and Program by using the Create Package and Program Wizard

You can create a new package and program by using the Create Package and Program Wizard. To do so, use the following procedure.

To create a package and program

  1. In the Configuration Manager console, click Software Library.

  2. In the Software Library workspace, expand Application Management, and then click Packages.

  3. In the Home tab, in the Create group, click Create Package.

  4. On the Package page of the Create Package and Program Wizard, specify the following information:

    - **Name:** Specify a name for the package with a maximum of 50 characters.

- **Description:** Optionally specify a description for this package with a maximum of 128 characters.

- **Manufacturer:** Optionally specify a manufacturer name to help you identify the package in the Configuration Manager console. This name can be a maximum of 32 characters.

- **Language:** Optionally specify the language version of the package with a maximum of 32 characters.

- **Version:** Optionally specify a version number for the package with a maximum of 32 characters.

- **This package contains source files** - This setting indicates whether the package requires source files to be present on client devices. By default, this check box is cleared and Configuration Manager does not use distribution points for the package. When this check box is selected, distribution points are used.

- **Source folder:** If the package contains source files, click **Browse** to open the **Set Source Folder** dialog box and specify the location of the source files for the package.

  <div class="alert">


  > [!NOTE]
  > <P>The computer account of the site server must have read access permissions to the source folder that you specify.</P>


  </div>

  5. On the Program Type page of the Create Package and Program Wizard, select the type of program to create, and then click Next. You can create a program for a computer or device, or you can skip this step and create a program later.

    Important

    You can only create packages and programs for devices running Windows CE.

    Note

    To create a new program for an existing package, select the package, and then, in the Home tab, in the Package group, click Create Program to open the Create Program Wizard.

  6. Use one of the following procedures to create a standard program or a device program.

To create a standard program

  1. On the Program Type page of the Create Package and Program Wizard, select Standard Program, and then click Next.

  2. On the Standard Program page of the Wizard, specify the following information:

    - **Name:** Specify a name for the program with a maximum of 50 characters.

  <div class="alert">


  > [!NOTE]
  > <P>The program name must be unique within a package. After you create a program, you cannot modify its name.</P>


  </div>

- **Command Line:** Enter the command line to be used to start this program, or click **Browse** to browse to the file location.

  If a specified file name does not have an extension specified, Configuration Manager attempts to use .com, .exe, and .bat as possible extensions.

  When the program is run on a client, Configuration Manager first searches for the command-line file name within the package, searches next in the local Windows folder, and then searches in local %path%. If the file cannot be found, the program fails.

- **Startup folder:** Optionally use this field to specify the folder from which the program runs, up to 127 characters. This folder can be an absolute path on the client or a path relative to the distribution point folder that contains the package.

- **Run:** Specifies the mode in which the program will run on client computers. Select one of the following:

    - **Normal** - The program runs in the normal mode based on system and program defaults. This is the default mode.

    - **Minimized** – The program runs minimized on client devices. Users might see installation activity in the notification area or taskbar.

    - **Maximized** – The program runs maximized on client devices. Users will see all installation activity.

    - **Hidden** – The program runs hidden on client devices. Users will not see any installation activity.

- **Program can run:** Specify whether the program can run only when a user is logged on, run only when no user is logged on, or run regardless of whether a user is logged on to the client computer.

- **Run mode:** Specify whether the program will run with administrative permissions or with the permissions of the currently logged on user.

- **Allow users to view and interact with the program installation** - Use this setting, if available, to specify whether to allow users to interact with the program installation. This check box is available only when **Only when no user is logged on** or **Whether or not a user is logged on** is selected for **Program can run** and **Run with administrative rights** is selected for **Run mode**.

- **Drive mode:** Specify information about how this program will runs on the network. Choose one of the following:

    - **Runs with UNC name** - Indicates that the program runs with a Universal Naming Convention (UNC) name. This is the default setting.

    - **Requires drive letter** - Indicates that the program requires a drive letter to fully qualify its location. For this setting, Configuration Manager can use any available drive letter on the client.

    - **Requires specific drive letter (example: Z:)** - Indicates that the program requires a specific drive letter that you specify to fully qualify its location. If the specified drive letter is already used on a client, the program does not run.

- **Reconnect to distribution point at log on** - Use this check box to indicate whether the client computer reconnects to the distribution point when the user logs on. By default, this check box is cleared.

  3. On the Requirements page of the Create Package and Program Wizard, specify the following information:

    - **Run another program first** – You can use this setting to identify a package and program that will be run before this package and program will be run.

- **Platform requirements** – Select **This program can run on any platform** or select **This program can run only on specified platforms** and then choose the operating systems that clients must be running to be able to install the package and program.

- **Estimated disk space:** Specify the amount of disk space that the software program requires to be able to run on the computer. This can be specified as **Unknown** (the default setting) or as a whole number greater than or equal to zero. If a value is specified, units for the value must also be specified.

- **Maximum allowed run time (minutes):** Specify the maximum time that the program is expected to run on the client computer. This can be specified as **Unknown** (the default setting) or as a whole number greater than zero.

  By default, this value is set to 120 minutes.

  <div class="alert">


  > [!IMPORTANT]
  > <P>If you are using maintenance windows for the collection on which this program is run, a conflict may occur if the <STRONG>Maximum allowed run time</STRONG> is longer than the scheduled maintenance window. However, if the maximum run time is set to <STRONG>Unknown</STRONG>, the program will start to run during the maintenance window and will continue to run as needed after the maintenance window is closed. If the user sets the maximum run time to a specific period that exceeds the length of any available maintenance window, then the program will not be run.</P>


  </div>

  If the value is set as **Unknown**, Configuration Manager sets the maximum allowed run time as 12 hours (720 minutes).

  <div class="alert">


  > [!NOTE]
  > <P>If the maximum run time (whether set by the user or as the default value) is exceeded, Configuration Manager will stop the program if <STRONG>run with administrative rights</STRONG> is selected and <STRONG>Allow users to view and interact with the program installation</STRONG> is not selected.</P>


  </div>

  4. Click Next and continue to To complete the Create Package and Program Wizard.

To create a device program

  1. On the Program Type page of the Create Package and Program Wizard, select Program for device, and then click Next.

  2. On the Program for Device page of the Wizard, specify the following information:

    - **Name:** Specify a name for the program with a maximum of 50 characters.

  <div class="alert">


  > [!NOTE]
  > <P>The program name must be unique within a package. After you create a program, you cannot modify its name.</P>


  </div>

- **Comment:** Optionally, specify a comment for this device program with a maximum of 127 characters.

- **Download folder:** Specify the name of the folder on the Windows CE device in which the package source files will be stored. The default value is **\\Temp\\**.

- **Command Line:** Enter the command line to use to start this program, or click **Browse** to browse to the file location.

- **Run command line in download folder** – Select this option to run the program from the previously specified download folder.

- **Run command line from this folder** – Select this option to specify a different folder from which to run the program.

  3. On the Requirements page of the Wizard, specify the following information:

    - **Estimated disk space:** Specify the amount of disk space required for the software. This will be displayed to users of mobile devices before they install the program.

- **Download program:** Specify information regarding when this program can be downloaded to mobile devices. You can specify **As soon as possible**, **Only over a fast network**, or **Only when the device is docked**.

- **Additional requirements:** Specify any additional requirements for this program. These will be displayed to users before they install the software. For example, you could notify users that they need to close all other applications before running the program.

  4. Click Next.

To complete the Create Package and Program Wizard

  1. On the Summary page of the Wizard, review the actions that will be taken, then complete the Wizard.

  2. Optionally, verify that the new package and program is displayed in the Packages node of the Software Library workspace.

How to Create a Package and Program from a Package Definition File

Use the following procedure to create a package and program from a package definition file. For more information about package definition files, see About the Package Definition File Format in this topic.

To import a package and program from a definition file

  1. In the Configuration Manager console, click Software Library.

  2. In the Software Library workspace, expand Application Management, and then click Packages.

  3. In the Home tab, in the Create group, click Create Package from Definition.

  4. On the Package Definition page of the Create Package from Definition Wizard, choose an existing package definition file, or click Browse to open a new package definition file. After you have specified a new package definition file, select it from the Package definition list, and then click Next.

  5. On the Source Files page of the Wizard, specify information about any required source files for the package and program, and then click Next.

  6. If the package requires source files, on the Source Folder page of the Wizard, specify the location from which the source files are to be obtained, and then click Next.

  7. On the Summary page of the Wizard, review the actions that will be taken and then complete the Wizard. The new package and program is displayed in the Packages node of the Software Library workspace.

About the Package Definition File Format

Package definition files are scripts that you can use to help automate package and program creation with Configuration Manager. They provide all of the information that Configuration Manager needs in order to create a package and program, except for the location of package source files. Each package definition file is an ASCII or UTF-8 text file following the .ini file format and containing the following described sections:

  • [PDF]

  • [Package Definition]

  • [Program]

[PDF]

This section identifies the file as a package definition file. It contains the following information:

  • Version: This specifies the version of the package definition file format that is used by the file. This corresponds to the version of System Management Server (SMS) or Configuration Manager for which it was written. This entry is required.

[Package Definition]

This section of the package definition file specifies the properties of the package and program. It provides the following information:

  • Name: The name of the package, up to 50 characters. This entry is required.

  • Version: The version of the package, up to 32 characters. This entry is optional.

  • Icon: Optionally, the file containing the icon to use for this package. If specified, this icon will replace the default package icon in the Configuration Manager console.

  • Publisher: The publisher of the package, up to 32 characters. This entry is required.

  • Language: The language version of the package, up to 32 characters. This entry is required.

  • Comment: An optional comment about the package, up to 127 characters.

  • ContainsNoFiles: This entry indicates whether or not a source is associated with the package.

  • Programs: The programs defined for this package. Each program name corresponds to a [Program] section in this package definition file. This entry is required.

    Example:

    Programs=Typical, Custom, Uninstall

  • MIFFileName: The name of the Management Information Format (MIF) file that contains the package status, up to 50 characters.

  • MIFName: The name of the package (for MIF matching), up to 50 characters.

  • MIFVersion: The version number of the package (for MIF matching), up to 32 characters.

  • MIFPublisher: The software publisher of the package (for MIF matching), up to 32 characters.

[Program]

For each program specified in the Programs entry in the [Package Definition] section, the package definition file must include a [Program] section that defines that program. Each Program section provides the following information:

  • Name: The name of the program, up to 50 characters. This entry must be unique within a package. This name is used when defining advertisements. On client computers, the name of the program is shown in Run Advertised Programs in Control Panel. This entry is required.

  • Icon: Optionally specifies the file containing the icon to use for this program. If specified, this icon will replace the default program icon in the Configuration Manager console and will be displayed on client computers when the program is advertised.

  • Comment: An optional comment about the program, up to 127 characters.

  • CommandLine: Specifies the command line for the program, up to 127 characters. The command is relative to the package source folder. This entry is required.

  • StartIn: Specifies the working folder for the program, up to 127 characters. This entry can be an absolute path on the client computer or a path relative to the package source folder. This entry is required.

  • Run: Specifies the program mode in which the program will run. You can specify Minimized, Maximized, or Hidden. If this entry is not included, the program will run in normal mode.

  • AfterRunning: Specifies any special action that occurs after the program is successfully completed. Options available are SMSRestart, ProgramRestart, or SMSLogoff. If this entry is not included, the program will not run a special action.

  • EstimatedDiskSpace: Specifies the amount of disk space that the software program requires to be able run on the computer. This can be specified as Unknown (the default setting) or as a whole number greater than or equal to zero. If a value is specified, the units for the value must also be specified.

    Example:

    EstimatedDiskSpace=38MB

  • EstimatedRunTime: Specifies the estimated duration (in minutes) that the program is expected to run on the client computer. This can be specified as Unknown (the default setting) or as a whole number greater than zero.

    Example:

    EstimatedRunTime=25

  • SupportedClients: Specifies the processors and operating systems on which this program will run. The specified platforms must be separated by commas. If this entry is not included, supported platform checking will be disabled for this program.

  • SupportedClientMinVersionX, SupportedClientMaxVersionX: Specifies the beginning-to-ending range for version numbers for the operating systems specified in the SupportedClients entry.

    Example:

    SupportedClients=Win NT (I386),Win NT (IA64),Win NT (x64)
Win NT (I386) MinVersion1=5.00.2195.4
Win NT (I386) MaxVersion1=5.00.2195.4
Win NT (I386) MinVersion2=5.10.2600.2
Win NT (I386) MaxVersion2=5.10.2600.2
Win NT (I386) MinVersion3=5.20.0000.0
Win NT (I386) MaxVersion3=5.20.9999.9999
Win NT (I386) MinVersion4=5.20.3790.0
Win NT (I386) MaxVersion4=5.20.3790.2
Win NT (I386) MinVersion5=6.00.0000.0
Win NT (I386) MaxVersion5=6.00.9999.9999
Win NT (IA64) MinVersion1=5.20.0000.0
Win NT (IA64) MaxVersion1=5.20.9999.9999
Win NT (x64) MinVersion1=5.20.0000.0
Win NT (x64) MaxVersion1=5.20.9999.9999
Win NT (x64) MinVersion2=5.20.3790.0
Win NT (x64) MaxVersion2=5.20.9999.9999
Win NT (x64) MinVersion3=5.20.3790.0
Win NT (x64) MaxVersion3=5.20.3790.2
Win NT (x64) MinVersion4=6.00.0000.0
Win NT (x64) MaxVersion4=6.00.9999.9999

  • AdditionalProgramRequirements: Optionally provide any other information or requirements for client computers, up to 127 characters.

  • CanRunWhen: Specifies the user status that the program requires to be able run on the client computer. Available values are UserLoggedOn, NoUserLoggedOn, or AnyUserStatus. The default value is UserLoggedOn.

  • UserInputRequired: Specifies whether the program requires interaction with the user. Available values are True or False. The default value is True. This entry is set to False if CanRunWhen is not set to UserLoggedOn.

  • AdminRightsRequired: Specifies whether the program requires administrative credentials on the computer to be able to run. Available values are True or False. The default value is False. This entry is set to True if CanRunWhen is not set to UserLoggedOn.

  • UseInstallAccount: Specifies whether the program uses the Client Software Installation Account when it runs on client computers. By default, this value is False. This value is also False if CanRunWhen is set to UserLoggedOn.

  • DriveLetterConnection: Specifies whether the program requires a drive letter connection to the package files that are located on the distribution point. You can specify True or False. The default value is False, which allows the program to use a Universal Naming Convention (UNC) connection. When this value is set to True, the next available drive letter will be used (starting with Z: and proceeding backward).

  • SpecifyDrive: Optionally, specifies a drive letter that the program requires to connect to the package files on the distribution point. This specification forces the use of the specified drive letter for client connections to distribution points.

  • ReconnectDriveAtLogon: Specifies whether the computer reconnects to the distribution point when the user logs on. Available values are True or False. The default value is False.

  • DependentProgram: Specifies a program in this package that must run before the current program. This entry uses the format DependentProgram=<ProgramName>, where <ProgramName> is the Name entry for that program in the package definition file. If there are no dependent programs, leave this entry empty.

    Example:

    DependentProgram=Admin
    DependentProgram=

  • Assignment: Specifies how the program is assigned to users. This value can be: FirstUser, only the first user who logs on runs the program; or EveryUser, every user who logs on to the client runs the program. When CanRunWhen is not set to UserLoggedOn, this entry is set to FirstUser.

  • Disabled: Specifies whether this program can be advertised to clients. Available values are True or False. The default value is False.

How to Import a Package and Program

To import a package and program

  1. In the Configuration Manager console, click Software Library.

  2. In the Software Library workspace, expand Application Management, and then click Packages.

  3. In the Home tab, in the Create group, Click Import.

  4. On the General page of the Import Package Wizard, specify or browse to the compressed (.zip) file that contains the package and program to import, and then click Next.

  5. On the File Content page of the Wizard, review the items that will be imported, and then click Next. You can click View Failure to examine the details of items that cannot be imported. If the package you are trying to import already exists, you can choose to either ignore the duplicate package or overwrite the original package.

  6. On the Summary page of the Wizard, review the actions that will be taken and then complete the Wizard. The new package and program is displayed in the Packages node of the Software Library workspace.