Windows installer supports properties that can be provided via command line. Deployment via group policy objects in the domain doesn’t support properties be supplied via command line. Instead,
.mst file must be used.
This document describes how to create transformation and use it with GPO.
The following video shows how to create an Organizational Unit along with a GPO to deploy OBRM with
.mst to computers on a domain.
Orca application is a database table editor for creating and editing Windows Installer packages and merge modules. This tool is only available within the Windows SDK Components for Windows Installer Developers and is provided as
After installing the Windows SDK Components for Windows Installer Developers, go to
C:\Program Files\Microsoft SDKs\Windows\v7.0\Bin, and double-click
Orca.msi to install the Orca.
After Orca was installed, right-click the
.msipackage, and select Edit with Orca.
Go to Transform > New transform.
In the Tables list, select Property table. Right-click anywhere on the Values view and select Add Row.
A window will appear where a new property SOSUSER can be added, with the value of the field being the actual username.
Repeat the following for all parameters:
SOSSCAN=0|1|2 (0 - Don’t Scan, 1 - Scan Just Personal, 2 - Scan All)
SCHEDULEDAILY=Time in 24-hour format
Xhours. Use whole numbers from 1 to 23
SCHEDULEUSER=Windows admin username with domain. You should specify it even if
SCHEDULEINTERACTIVEis false to make a schedule task run correctly
SCHEDULEPASS=Windows admin password
SCHEDULEINTERACTIVE=Task should be run when user is logged out.
SCHEDULEPASSmust be supplied
SOSPASS=Backup account password
Go to Transform > Generate Transform.
Select name and path to save your transform.
Add transformation to GPO software installation package.
Go to Group policy object editor, and add new software installation package:
Use advanced deployment method.
On the Modifications tab, add path to the
.mstfile created for this
Central deployment without
There’s also a way around
.mst for deployment if you’re unwilling or can’t use for any reason.
There are various central deployment applications, like LANDesk for example.
To pass parameters to
.msi, you may use common batch file with a command line inside.
Using environment variables
When deploying centrally, you may want to use some environment variables specific to each matching the application is being installed. For example, you may want to include the Documents folder into backup set for every user.
For this purpose, you may use
%USERPROFILE% environment variable.
Since we use the
.bat file, we have all of them at hand.
So we could simply write something like
setup.msi SOSBACKUPSET=%USERPROFILE%\Desktop|%USERPROFILE%\Documents, and this will be parsed at once by Windows, and
.msi will get
To see all environment variables, run
SET from the command line.
/qn parameters to the
.msi parameters list to install silently.
.batfile, make sure you run it as administrator.