Using command programs

You can automate the installation process by creating a command (.cmd) file to run setup.exe with predefined parameters. In this situation, users do not need to specify options at the command prompt.

The .cmd file can include any of the valid parameters for setup.exe that are listed in the "Using command line parameters to change the install behavior" topic.

You should consider using .cmd files if you intend to apply different transforms to different users depending on some organizational criteria. Because you must specify transforms at command line by setting the TRANSFORMS public property, your users would need to enter the right parameters and you must trust that they entered the right choices. One alternative is to set the command line options in setup.ini, but a disadvantage to that is that all clients running from the same source image would get the same set of transforms applied. By creating separate .cmd files, you can define different settings and have each user run the appropriate .cmd file.