ODMS supports MST files through the use of the System Configuration Program, supplied as part of the ODMS Admin CD.

Transcription

1 Using MST files to create a custom ODMS deployment MST files are used to transform a windows MSI installer. They can be very useful for creating a custom deployment of software and for ensuring a consistent, efficient installation over a large network. This guide will also provide guidelines on deploying with an MST file over Group Policy and with a script. ODMS supports MST files through the use of the System Configuration Program, supplied as part of the ODMS Admin CD. This guide will demonstrate two methods of deployment using custom MST files: Deploying ODMS through Group Policy Deploying ODMS with a script (.bat file) Making an MST file: Open the System Configuration Program Select the Software tab.

2 Click the 'Add' button to import the ODMS installer into the System Configuration Program. Browse to your ODMSClient.msi file (found in your ODMS Download or ODMS CD), and click Open. The software package will now be shown in the list. Click the MST button to start the MST creation wizard.

3 Click Next Leave the option Create new MST file as it is and click Next.

4 Select where to save your file and the name. For convenience during deployment it is recommended to save the file in the same place as your install media. Enter the license manager address and port number as per your Workgroup mode installation.

5 Choose which package(s) to install. Leave the installation path as the default value unless you specifically need to change it. Click Next.

6 Choose Management with a repository on a network and click Next. Configure the repository path or repository service address as per your Workgroup mode installation. Click Next

7 Click Next to create the MST file. Your MST file will now be ready to use alongside the ODMSClient MSI.

8 Deploying ODMS with Group Policy: Log into your server and open Group Policy Manager Select your domain or group and right click. Choose Create new GPO in this domain, and Link it here...

9 Choose whether you want to deploy to computers (User Policy or Computer Policy) and select software installation. Right click and select New Package.

10 Browse to your copy of ODMS and choose your ODMSClient.msi Note: Your ODMSClient Msi file should be saved in a network location accessible from all PCs/Users in order for the software to be deployed. When prompted choose Advanced

11 A new window will appear, go to the Modifications tab and click add and browse to your Custom MST file. Note: This should also be saved in a shared location, for best results store the MST file in the same location as the MSI. Click OK to save your policy. When the affected users/computers are logged on the software will be deployed automatically.

12 Deploying ODMS with a script (.bat file): Follow the steps on making an MST file (Pages 1-6) and save the MST in a shared folder with your ODMS software. Open notepad or a similar application. Enter the following string: msiexec.exe.i Path to your ODMSClient.msi file SYSTEM=WORKGROUP TRANSFORMS= Path to your custom MST file /q Save the file with a.bat extension (e.g. Script.bat). This script can now be executed individually or added to a user's logon script for a silent deployment. What is this script doing? Here is the script broken down into each section: msiexec.exe /i - This is telling Windows to run Windows Installer in Installation Mode. Path to your ODMSClient.msi - e.g. \\Server\ODMS_R6\ODMSClient.msi The quotations should be included if there are spaces in the filepath. SYSTEM=WORKGROUP This is a switch that tells the ODMSClient.msi file to run in Workgroup mode. The opposite of this would be SYSTEM=STANDALONE. TRANSFORMS= - Tells the installer to expect a modification (MST file). Path to your custom MST - e.g. \\Server\ODMS_R6\CustomInstall.mst /q Make the installation silent. Alternatively use /qb to show a basic progress bar or remove this tag to see the installation wizard.