A Deployment is the package and target combined with additional deployment parameters such as when and how the package will be deployed.
- Software Package: Information about the software you want to deploy, such as: name, version, and path to setup files.
- Target: The computers or users that should receive the package.
Creating a package
Specops Deploy packages contain information about a software installation, such as network file path to the installation files and any parameters needed to install the software.
There are four different package types:
- Windows Installer: A Windows Installer package uses an msi-file as the installation source and is applied on the client through Windows Installer.
- Windows Installer Patch: A Windows Installer Patch, or msp-file is a type of msi-package that updates an existing software installation. Windows Installer patches are applied through Windows Installer and require little or no configuration.
- App-V package: Microsoft Application Virtualization packages are based on App-V 4.6 or 5.0 package files. These applications can only be installed on clients that have the App-V client installed.
- Legacy Setup: The legacy package type indicates that the installation is run through a separate executable, typically a Setup.exe installation program. The setup file is fully responsible for all actions it performs during the software
installation and typically requires many configuration parameters to silently install the software without end user intervention. In order to remove the installed software, you must also specify uninstallation commands for legacy setups.
- Windows Store Applications: Windows Store applications are applications that are designed for the Windows 8 start screen. Before you can deploy your Windows Store App you need to package and sign it using the App Packager (MakeAppX.exe)
and SignTool (SignTool.exe) executables shipped with Visual Studio 2012 and the Windows 8 SDK.
Create a package using the Control Center
- In the navigation pane expand tasks, and click Deploy Package.
- Click Create new package.
- Select the type of package you want to create, and click OK.
- In the package category field, click New to create a new Package Category.
NOTE
You can use an existing Package Category.
- Enter a name and description for the Package Category, and click OK.
NOTE
Selecting a package category is not mandatory but it will allow you to easily sort and view the deployments.
- Browse to the location of the file, and click Open.
NOTE
The path to the source files must be in the UNC format.
- Verify that the Package Properties field has automatically been updated and enter a description for the package in the text field.
- In the navigation pane, select Installation options and modify the following settings:
Option
Additional Windows Installer Properties
- Enter parameters to the install command in the text field.
Option
Additional Windows Installer Properties
- Expand Show advanced options.
- In the Pre installation command text field, enter the full path to a command that will be executed before a package is installed.
- Enter parameters to the pre-installation command in the parameters text field.
- In the text field, enter the exit code value that represents a successful execution. You can also choose to ignore the exit code.
Option
Additional Windows Installer Properties
- Expand Show advanced options.
- In the Post installation command text field, enter the full path to a command that will be executed after a package is installed.
- Enter parameters to the pre-installation command in the parameters text field.
- In the text field, enter the exit code value that represents a successful execution. You can also choose to ignore the exit code.
- Once you have modified the installation options, select Uninstallation options from the navigation pane to configure the parameters that will be used when you choose to uninstall a package. You can modify the following settings:
Option
Pre-installation commands and parameters
- Expand Show advanced options.
- In the Pre installation command text field, enter the full path to a command that will be executed before a package is installed.
- Enter parameters to the pre-installation command in the parameters text field.
- In the text field, enter the exit code value that represents a successful execution. You can also choose to ignore the exit code.
Option
Pre-installation commands and parameters
- Expand Show advanced options.
- In the Post installation command text field, enter the full path to a command that will be executed after a package is installed.
- Enter parameters to the pre-installation command in the parameters text field.
- In the text field, enter the exit code value that represents a successful execution. You can also choose to ignore the exit code.
- If the package you are creating is a Windows Installer package, click Transforms in the navigation pane and follow the below steps. If you are not creating a Windows Installer Package, skip to step 11.
- Click Add to add a transform MST file to the package.
- Click OK.
- Click Advanced options in the navigation pane.
- If you want to allow computers to reboot if it is required by the package, enable the checkbox. If the checkbox is enabled, you can also force computers to reboot after installing or uninstalling the package.
- If the package file is not in the root directory of the files and directories required by the package, you will need to change the path. Click Change.
- Enable the Use HTTP URL as package source checkbox if you want to use a HTTP URL as the package source.
- Enable an HTTP directory for the package.
- To view a list of changes made to the package, click Modify history in the navigation pane.
- Click OK to save the new package.
Set package order
If you are deploying multiple packages to the same target, you can use the set package order command to define the precedence order for the packages. This command is available in the Deploy Control Center. You will need to expand Objects,
and click Packages.
Create a package using the GPMC snap-in
- Open the GPMC and navigate to the GPO you want to the GPO you want to edit.
- Right click on the GPO and select Edit…
- In the Group Policy Management Editor, expand:
- Group Policy Name>Computer Configuration>Software Settings>Specops Deploy
or
- Group Policy Name>User Configuration>Software Settings>Specops Deploy
- Select Click here to deploy a package.
- Click Create new package.
- Select the type of package you want to create, and click OK.
- In the package category field, click New to create a new Package Category.
NOTE
You can use an existing Package Category.
- Enter a name and description for the Package Category, and click OK.
NOTE
Selecting a package category is not mandatory, but it will allow you to easily sort and view the deployments.
- Browse to the location of the file, and click Open.
NOTE
The path to the source files must be in the UNC format.
- Verify that the Package Properties field has automatically been updated and enter a description for the package in the text field.
- In the navigation pane, select Installation options and modify the following settings:
Option
Additional Windows Installer Properties
- Enter parameters to the install command in the text field.
Option
Additional Windows Installer Properties
- Expand Show advanced options.
- In the Pre installation command text field, enter the full path to a command that will be executed before a package is installed.
- Enter parameters to the pre-installation command in the parameters text field.
- In the text field, enter the exit code value that represents a successful execution. You can also choose to ignore the exit code.
Option
Additional Windows Installer Properties
- Expand Show advanced options.
- In the Post installation command text field, enter the full path to a command that will be executed after a package is installed.
- Enter parameters to the pre-installation command in the parameters text field.
- In the text field, enter the exit code value that represents a successful execution. You can also choose to ignore the exit code.
- Once you have modified the installation options, select Uninstallation options from the navigation pane to configure the parameters that will be used when you choose to uninstall a package. You can modify the following settings:
Option
Pre-installation commands and parameters
- Expand Show advanced options.
- In the Pre installation command text field, enter the full path to a command that will be executed before a package is installed.
- Enter parameters to the pre-installation command in the parameters text field.
- In the text field, enter the exit code value that represents a successful execution. You can also choose to ignore the exit code.
Option
Pre-installation commands and parameters
- Expand Show advanced options.
- In the Post installation command text field, enter the full path to a command that will be executed after a package is installed.
- Enter parameters to the pre-installation command in the parameters text field.
- In the text field, enter the exit code value that represents a successful execution. You can also choose to ignore the exit code.
- If the package you are creating is a Windows Installer package, click Transforms in the navigation pane and follow the below steps. If you are not creating a Windows Installer Package, skip to step 14.
- Click Add to add a transform MST file to the package.
- Click OK.
- Click Advanced options in the navigation pane.
- If you want to allow computers to reboot if it is required by the package, enable the checkbox. If the checkbox is enabled, you can also force computers to reboot after installing or uninstalling the package.
- If the package file is not in the root directory of the files and directories required by the package, you will need to change the path. Click Change.
- Enable the Use HTTP URL as package source checkbox if you want to use a HTTP URL as the package source.
- Enable an HTTP directory for the package.
- To view a list of changes made to the package, click Modify history in the navigation pane.
- Click OK to save the new package.
Set package order
If you are deploying multiple packages to the same target, you can use the set package order command to define the precedence order for the packages. This command is available in the Deploy Control Center. You will need to expand Objects,
and click Packages.
Selecting a target
Once a package has been created, it can be configured for deployment using targeting criteria. A target consists of a set of criteria which the client will match against its own environment. If the criterion matches the client environment,
the target is considered valid and the deployments associated with the target should be acted on. The Client will evaluate all targets in every GPO with Specops Deploy / App settings.
Select a target using the Control Center
- In the navigation pane, expand Objects, and click Targets.
- Click New Target.
- Select the type of target you want to create, and click OK.
NOTE
Computer and user targets are different. Packages deployed to a Computer target will install software to a specific set of computers while packages deployed to a user target will install on any computers where the users logon.
- Enter a name and description for the target in the text field.
- Select Target criteria from the navigation pane.
- To add Target Criteria select the Add Target Criterion drop box. You can add the following criteria:
Table captionCriteria | Description |
---|
Membership criteria | The Membership criteria consists of the following items:
- Security groups
- Organizational units
- User names
- Computer names
- Sites
- Ip address range
|
---|
Environment criteria | The Environment criteria consists of the following items:
- Languages
- Environment variables
- Registry settings
|
---|
Hardware criteria | The Hardware criteria consists of the following items:
- Computer models
- BIOS versions
- Hard drive free space
- Processor
- Memory size
|
---|
Software criteria | The Software criteria consists of the following items:
- Operating systems
- Windows installer installations
- Files
|
---|
WMI Query | - Query the Windows Management Instrumentation
|
---|
- Once you have added the target criteria, they will be displayed in the list. From the list you can:
- Edit a criterion
- Remove a criterion
- To view a list of changes made to the package, click Modify history in the navigation pane.
- Click OK to save the new user target.
Select a target using the GPMC Snap-in
- In the Group Policy Management Editor, expand:
- Group Policy Name>Computer Configuration>Software Settings>Specops Deploy
or
- Group Policy Name>User Configuration>Software Settings>Specops Deploy
NOTE
Computer and user targets are different. Packages deployed to a Computer target will install software to a specific set of computers while packages deployed to a user target will install on any computers where the users logon.
- Select the target node, and click New Target.
- Enter a name and description for the target in the text field.
- Select Target criteria from the navigation pane.
- To add Target Criteria select the Add Target Criterion drop box. You can add the following criteria:
Table captionCriteria | Description |
---|
Membership criteria | The Membership criteria consists of the following items:
- Security groups
- Organizational units
- User names
- Computer names
- Sites
- Ip address range
|
---|
Environment criteria | The Environment criteria consists of the following items:
- Languages
- Environment variables
- Registry settings
|
---|
Hardware criteria | The Hardware criteria consists of the following items:
- Computer models
- BIOS versions
- Hard drive free space
- Processor
- Memory size
|
---|
Software criteria | The Software criteria consists of the following items:
- Operating systems
- Windows installer installations
- Files
|
---|
WMI Query | - Query the Windows Management Instrumentation
|
---|
- Once you have added the target criteria, they will be displayed in the list. From the list you can:
- Edit a criterion
- Remove a criterion
- To view a list of changes made to the package, click Modify history in the navigation pane.
- Click OK to save the new user target.
Advanced targets (target criteria Boolean expressions)
Targets can contain multiple different criteria. By default, to be considered a valid member of the target and be included in the deployment, that member has to meet all these criteria (i.e. the criteria are combined by using the Boolean AND
operator). Criteria are assigned an ID in the order that they are added (A, B, C… etc.).
NOTE
the order of criteria cannot be altered after they have been created.
This default relationship between the different criteria can be altered by using a customized Boolean expression.
Boolean customization
- Select the Customize checkbox.
- Enter or alter the Boolean expression in the text field.
Removing the customization
- Clear the Customize checkbox
- The Boolean expression will revert to the default (all criteria combined by AND)
Boolean operators
The following Boolean operators can be used:
- AND
- OR
- NOT (notation: AND NOT)
It is also possible to group criteria by enclosing them in parentheses in the Boolean expression.
NOTE
do not use Boolean algebraic notation (&&, ||, !) when entering your expression. Use the alphabetic notation above instead.
NOTE
the Boolean operator Exclusive OR (^) cannot be used.
Removing a criterion in targets with Boolean customization
Removing a criterion from a target with a customized Boolean expression will make the expression invalid, and it will be removed from the target. Since there is no valid expression governing the target, the target cannot be saved. To resolve
this, do one of the following:
- Clear the Customize checkbox (the expression will revert to its default AND state) OR
- Enter a valid Boolean expression containing all the remaining criteria.
NOTE
when removing a criterion, all following criteria will receive new ID designations.
Examples
The following expression examples are applied to a target containing the following three criteria:
- Organizational units: HR
- Computer models: Dell XPS 8700
- Security groups: Administrators
Expression examples
A and B and C: users in the HR OU who have a Dell XPS 8700 and who are a member of the Administrators Security group (this is the default expression)
(A and B) and not C: users in the HR OU who have a Dell XPS 8700, but are not a member of the Administrators Security group
(A or B) and C: users in the Administrators Security group who are either a member of the HR OU or have a Dell XPS 8700
A and not B and not C: users in the HR OU who do not have a Dell XPS 8700, and who are not a member of the Administration Security group
Configure the deployment
Once you have the package and the target you can configure additional deployment parameters such as when and how the package will be deployed.
Configure the deployment using the Control Center
- In the navigation pane, expand Objects and select Deployments.
- Click New Deployment.
- Select the package you want to deploy, and click OK.
- From the Target drop down menu select the target the package will be deployed to.
- Select the installation type. You will be given the following options:
Option | Description |
---|
Install | A full installation that completely installs the package on the computer. |
---|
Advertise only | The package is prepared for installation but the files are not installed. |
---|
Publish in Add/Remove programs | The package is published in the available programs list in Add/Remove programs. |
---|
- In the navigation pane, select Deployment options. You can configure the following items:
Option | Description |
---|
Installation time | - As soon as possible
- Not before
|
---|
Installation options | - Only install during user logon
- Only install after the user has logged on
- Both
|
---|
Source file options | - Download and install, remove source files from cache
- Download and install, leave source files in cache
- Install from network
|
---|
Uninstall the package if the deployments falls "Out of the Scope of management" | - Uninstalls the package if the GPO no longer applies
|
---|
- In the navigation pane, select End User Interaction. You can configure the following items:
Option | Description |
---|
Installation popup dialog | |
---|
Use custom end user message | |
---|
- To view a list of changes made to the package, click Modify history in the navigation pane.
- Click OK to start deployment.
View deployment feedback using the Control Center
You can use the Control Center to monitor, in real time, the status of deployments.
- In the navigation pane, expand Objects and select Deployments.
- Click Deployment feedback to view the status of deployments.
Configure the deployment using GPMC snap-in
- In the Group Policy Management Editor, expand:
- Group Policy Name>Computer Configuration>Software Settings>Specops Deploy / App
or
- Group Policy Name>User Configuration>Software Settings>Specops Deploy / App
- Click Deployments.
- Select the package you want to deploy, and click OK.
- From the Target drop down menu select target the package will be deployed to.
- Select the installation type. You will be given the following options:
Table captionOption | Description |
---|
Install | A full installation that completely installs the package on the computer. |
---|
Advertise only | The package is prepared for installation but the files are not installed. |
---|
Publish in Add/Remove programs | The package is published in the available programs list in Add/Remove programs. |
---|
- In the navigation pane, select Deployment options. You can configure the following items:
Option | Description |
---|
Installation time | - As soon as possible
- Not before
|
---|
Installation options | - Only install during user logon
- Only install after the user has logged on
- Both
|
---|
Source file options | - Download and install, remove source files from cache
- Download and install, leave source files in cache
- Install from network
|
---|
Uninstall the package if the deployments falls "Out of the Scope of management" | - Uninstalls the package if the GPO no longer applies
|
---|
- In the navigation pane, select End User Interaction. You can configure the following items:
Option | Description |
---|
Installation popup dialog | |
---|
Use custom end user message | |
---|
- To view a list of changes made to the package, click Modify history in the navigation pane.
- Click OK to start deployment.
View deployment feedback using the GPMC snap-in
You can use the GMCP snap-in to monitor, in real time, the status of deployments.
- In the Group Policy Management Editor, expand:
- Group Policy Name>Computer Configuration>Software Settings>Specops Deploy / App
or
- Group Policy Name>User Configuration>Software Settings>Specops Deploy / App
- Click Deployments.
- Click Deployment feedback to view the status of deployments.