This technical note describes common modifications you can make to the default package definition files that ship with Reflection Windows-based products.
Note: This technical note is intended for use by system administrators who are experienced in working with Microsoft Systems Management Server (SMS). If you are not familiar with SMS, please consult your system administrator before using it to deploy Reflection. Or, deployment information.
The most common modifications made to package definition files include adding a transform file to the Msiexec command line, adding command line switches /q or /qb to the Msiexec command line, and adjusting the installation environment options. The steps for making these modifications are included in the section "Using the Program Properties Dialog Box" below.
Before importing the Reflection Package Definition file into Microsoft SMS, create the Reflection administrative installation point and optionally customize your installation as described in Technical Note 1444. You can use the Reflection Customization Manager to customize your installation by creating a transform (*.mst) file. Installation customizations may include:
Reflection Customization Manager will create the transform and the associated files at the Administrative installation location. You will modify the default program definition to reference the *.mst file you created.
For more information about using Reflection Customization Manager, see the Preparing to Deploy Reflection tutorial at http://www.attachmate.com/docs/reflection/14.0/deploy.pdf or the Reflection Customization Manager (or Deployment Manager, depending on your version) help.
A package definition file (*.sms) is a template that contains the SMS components necessary to distribute software. Use the Microsoft SMS Package Definition Wizard to import the Reflection *.sms file and create the package.
Use the Program Properties dialog box to modify any of the programs in the Reflection *.sms file.
Adding a Transform File. To include a transform file, follow the standard syntax:
Msiexec /I <Reflect.msi> Transforms="<transformname.mst>"
where <Reflect.msi> is the name of the *.msi file for your Reflection product, and <transformname.mst> is the name of the transform file you created if you customized Reflection.
Using a Language Transform. If you are deploying a localized copy of Reflection and want the setup dialog boxes to be in the localized language, you must include the appropriate language transform.
You can specify multiple transforms by separating the transforms with a semi-colon. For example:
Msiexec /I ud130ilw.msi Transforms=":fra;MyTransform.mst" /q
Adding Command Line Switches. You can include Msiexec command line switches such as /q after the name of the transform. For Automated installations, use /q for no user interface, or /qb for basic user interface that displays a progress bar. For more information about Msiexec command line switches, see the Microsoft Knowledge Base Article 227091 at http://support.microsoft.com/default.aspx?scid=kb;en-us;227091.
Example. The following example shows the Msiexec command line used to deploy Reflection for UNIX and OpenVMS version 14.0, with a transform named MyTransform.mst, and without user interaction:
Msiexec /I ud140ilw.msi Transforms="MyTransform.mst" /q
Once modified, the package can be advertised to a collection.