How to create a package in ConfigMgr/SCCM?

Even though this article discusses about ConfigMgr/SCCM 2007, but most of the things also apply for SMS 2003.

To create a package, select Software Distribution -> Packages -> New -> Package.

New Package Wizard

Name: Type the name of the package. The length of the package name can be up to 50 characters. This field is a required fiend and can’t be left blank.
Version: This is the version number of the package. Its length can be up to 32 characters.
Manufacturer: The software manufacturer of the package and it length can be up to 32 characters.
Language: The language version of the software and its length can be up to 32 characters
Comment: Optional text about the package and its length can be up to 127 characters.  
This package contains source files” indicates whether the package contains source files. This check box is cleared by default. Check this if the package contains source files. When this check box is selected distribution points must be specified. In some cases the package may not contain any source files and we just want to execute a command line - am example would be running notepad.exe. Notepad.exe would be there on all the windows based system in %windir% folder.  In that case, de-select this option.

Use a compressed copy of the source directory: A compressed version will be decompressed and copied to the distribution points instead of being copied directly from the original source folder when the distribution points are refreshed.
If you specify Update All Distribution Points a new version of compressed copy is created from the specified source folder.

Tip: Use this option if the source files might be removed from the specified path (for example, if the source files are on a CD).
Note: A compressed version of the source folder is always created and used when the package is sent to distribution points in child sites.

Always obtain files from the source directory:

Each time a distribution point is updated, ConfigMgr will obtain the package source files from the path specified in the Source directory box.

Tip: Use this option if the source files are likely to remain on a specified path such as share on a server.

 Persist content in the client cache: Specifies whether package content should be retained in cache on the client computer indefinitely even if it has already been run. This option can be useful with some recurring packages such as virus software and this will reduce the available cache space.
Enable Binary differential replication:
Specifies whether binary delta compression should be used on changed package source files. This behavior can result in large bandwidth saving in transferring the changes for large files, compared with the traditional method where the entire file is transferred.

Note: Binary differential replication may not work properly, if you are using CIFS caching devices.

Access the distribution folder through common ConfigMgr package share:
If this option is selected, the package will be stored in common package share (SMSPKGx$, where x is the drive letter) on the distribution point.
Share the distribution folder:
If this option is selected package will be created on distribution points with an administrator specified share and path name.
Share Name:  Specify the name of the Share. This share name must be unique across all packages. All files and subdirectories within that share will be deleted and re-created each time the package is updated or refreshed. The share name\path must be unique across all packages and only the final directory in the path will be deleted and re-created each time the package is updated or refreshed.
Disconnect users from distribution points:
This setting only applies only to ‘standard distribution points’.
Number of retries before disconnecting users:
·         Number of times that ConfigMgr tires to update the package source files before disconnecting users disconnected to distribution point.
·         The default setting is 2, but we can specify 0 to 99, inclusive.
Interval between user notification and disconnection (Minutes):
·         Number of minutes ConfigMgr will wait after notifying users before disconnecting them from distribution points. The default setting is 5 minutes, but we can specify 0 to 59 minutes, inclusive.

Sending priority:
Specify the priority of this package. This priority setting will be used, when transferring this package to other child sites. The package with high sending priority will be processed first. The packages with identical priorities are sent in the order of their creation.
The three priorities available are:
  • High
  • Medium
  • Low
Medium is the default setting.

Preferred sender:
Select the preferred sender. <No Preference> is the default.
Branch distribution point content settings:

If Automatically download content when package are assigned to branch distribution points  option is selected, then package will be automatically downloaded to all branch distribution points when packages are assigned to branch DP’s.
Make this package available on protected distribution points when requested by client inside the protected boundaries:
If this option is selected, a client request will cause the local BDP to download the package. After content is successfully provisioned on the BDP, a subsequent client request will be able to download and run this content.
Download content on demand is available only for protected BDP’s. If a BDP is configured but not protected the MP will not rigger the package download.
All BDP’s in a give location will retrieve the package when on demand request is made to any of the BDP’s in a give location.
If “administrator must manually copy this package to the branch distribution points” then the package will not downloaded automatically and administrator must manually copy it to the BDP.

If “Use these fields for status MIF matching” is selected, then only the fields specified in this page will be used.

If “Use package properties for status MIF matching” is selected, then only fields on “General” page will be used.
The Security tab defines which users will have access, and what type of access they will have, to the package.
Configure the security permissions for this package and click Next.

Review the package settings and click on Finish -> Close.


Unknown said...

this is awesome stuffs.. keep it up my friend!

Post a Comment