| Attribute |
|
| Value |
|
| Description |
|
|
|
|
|
|
| |||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| x86 platform. This command runs only if the |
|
|
|
|
|
|
|
| computer on which the installation is run |
|
|
|
|
|
|
|
| matches this platform requirement. |
|
|
|
|
|
|
|
|
|
|
|
|
|
| x64 |
|
| Specifies that this program requires a |
|
|
|
|
|
|
|
| processor that supports the x64 extensions |
|
|
|
|
|
|
|
| to the x86 architecture. This command runs |
|
|
|
|
|
|
|
| only if the computer on which the installation |
|
|
|
|
|
|
|
| is run matches this platform requirement. |
|
|
|
|
|
|
|
|
|
|
Remarks
The Command element in the Config.xml file and the Add installations and run programs option in the OCT
The command line can be specified to run an arbitrary command or to run a lightweight executable that you want to run when this product is installed.
The Command element in Config.xml and the Add installations and run programs option in the OCT do not provide the software deployment capabilities that an enterprise software deployment and management tool provides, such as the ability to track deployment progress and troubleshoot problems. Therefore, we recommend that you use the Command element in Config.xml and Add installations and run programs in the OCT to run only lightweight executables or arbitrary commands that will not change the computer or that do not require user input. For example, you can run a utility to copy logs or a command to launch a Welcome page at the end of installation.
Important:
Chaining is not as reliable as installing each product separately. For example, if you chain two installations together and one of the products fails or encounters an unexpected error, the primary installation and the chained installation might not be completed successfully. Therefore, we recommend that you do not use the chaining approach. The recommended method for installing multiple products together in enterprise environments is to use a deployment management program, such as Microsoft System Center 2012 Configuration Manager or Microsoft Systems Management Server (SMS) 2003, or a third party tool, instead of chaining.
The use of Args and QuietArg is as follows:
∙The Args attribute is always appended to the command. This can include switches such as "/install" or "Company=MyCorporation."
∙The QuietArg attribute is also appended if setup is running silently (with Display set as Display="none"). In such cases, you can specify the QuietArg attribute by using the "/quiet" switch, for example, you can use: QuietArg="/quiet".
The following statements apply to the Wait attribute:
68
