Skip to main content

Creation

Before you create packages, you must connect to the site server.

Then the tab Create Package must be selected.

create-package1.png

The creation of a package takes place in three steps.

  1. Select installation Source (Select Source)
  2. Adjust the properties of the future package if necessary
  3. Create the package (Create Package)
Select Installation Source

After clicking on the button Select Source a special file browser opens, which works with shares.

The installation source can be selected within this share browser.

create-package2.png

Der SCCM Application Manager unterstützt folgende Installationsquellen:

  • Windows Installer files (*.msi, *.mst)
  • Executable files (*.exe)
  • PowerShell scripts (*.ps1)
  • Command line scripts (*.cmd)
  • VB scripts (*.vbs)

After pressing OK the SCCM Application Manager tries to read the properties of the installation source and displays them in the Source Properties area.

create-application3.png

The reading of the properties from an installation source depends on certain factors:

  1. For an MSI file, all properties can be read because they are mandatory.

  2. For executable files (*.exe), it depends on whether the manufacturer has been entered these properties in the header of the file. If not, these properties must be typed in by hand.
  3. For all scripts like *.ps1, *.cmd or *.vbs files it depends on whether regular expressions have been stored for each type of script, see this chapter. If not, these properties must be typed in by hand.

When working with scripts, the selected script is also displayed.

create-application10.png

This script is read-only by default, but it can be edited after clicking the Edit Script button and saved with Save Script.

Modifying Package Properties If Necessary

Within the deployment option drop-down list, you can select different advertisement options:

create-package3.png

  • One install deployment, one uninstall deployment (Standard)
  • Two install deployments, one uninstall deployment
  • One install deployment, no uninstall deployment
  • Two install deployments, no uninstall deployment
  • No deployments, package only
Package creation for devices or users

When creating packages, you can specify whether the associated collections should be created for devices or for users. For this purpose, the corresponding option must be selected before creating the package.

create-package7.png

If the SCCM Application Manager was configured sufficiently in advance (see global Configuration and Package Configuration), subsequent adjustments are minimal. It is often enough to check if the Source Properties were fully read.

If changes are made in the area of the Source Properties, these changes have a direct effect on the Package Properties. These are the properties that will be used during the creation of a package.create-package4.png

All Package Properties with a white background can be customized. Grayed-out properties can either be changed indirectly via the Source Properties, or their values are stored globally (see global Configuration and Package Configuration) and must be changed there.

Create the Package

Before a package is created, it should be checked whether all settings have been made correctly. The button ✅ gives information about it. If clicked, all settings will be checked. Any errors are displayed within the status messages. The button ✅ does not create a package.

create-package6.png

Finally, the Create Package button creates the desired package with all the objects involved (collections, programs, deployments, deployment types, folders, distribution point groups, etc.).

WMI Data

When the application is created, an entry is set in the WMI with which the SCCM Application Manager recognizes that the application was created with the SCCM Application Manager. Only applications with this entry are displayed in the SCCM Application Manager.

The entry is created in the WMI namespace root/SMS/site_{SITECODE} in the WMI class SMS_ContentPackage.
For each application created with the Application Manager, the entry is written to the WMI property "ISVString".

The entry is structured as follows (italics = placeholder):
SCCMApplicationManager.DEVICE:Manufacturer|ApplicationName|Version|Language|{GUID}

Example:
SCCMApplicationManager.DEVICE:IGOR PAVLOV|7-ZIP|23.01|ENGLISH|{138B78E5-6154-2856-1BF0-A4B38BDD0901}

Back to top