This article describes the Setup command-line options that you can use with the Microsoft Office Visio 2007 and Microsoft Office Visio 2003 Setup program to control how Setup operates. The Setup program is contained in the Setup.exe file.

When you run Setup, you can use command-line options to change some of the parameters that Setup uses to install Visio, such as display settings and default values for Setup properties. Setup and Microsoft Windows Installer use properties to control the installation process.

Back to the top

Setup command-line options in Visio 2007

In Visio 2007, the Setup.exe command line is used for very few operations. In Visio 2007, Setup recognizes the following command-line options:

•	/admin
•	/adminfile [path]
•	/config [path]
•	/modify [ProductID]
•	/repair [ProductID]
•	/uninstall [ProductID]

Note Although Setup recognizes only some command-line options in Visio 2007, you can still make all the same modifications to the Office installation. To do this, use the Office Customization tool instead of the command line to set Setup properties and to make other customizations. Alternatively, edit the Config.xml file for the product that you are installing.

/admin

This command-line option runs the Office Customization Tool to create a Setup customization file (.msp file). An example of the /admin option is as follows.

\\server\share\Office12\setup.exe /admin

/adminfile [path]

This command-line option applies the specified Setup customization file to the installation. You can specify a path of a particular customization file (.msp file) or of the folder in which you store customization files.

Note The /adminfile command-line option can be used only during the initial installation of the product.

We recommend that you keep the customization files in the Updates folder at the root of the network installation point. When you do this, you do not have to specify the file on the command line. Setup automatically finds the customization file that matches the product that is being installed, and then applies the customization file during the installation process.

If you store more than one customization file per product in the Updates folder, Setup applies them all to the installation. If you want to create unique configurations for different groups of users, you must store the customization files in a separate folder, and then specify the customization file that you want on the command line.

An example of the /adminfile [path] option is as follows.

\\server\share\Office12\setup.exe /adminfile \\server\share\MyUpdates\Engineering.msp 

In this example, "Office12" is the root of the network installation point.

/config [path]

This command-line option specifies the Config.xml file that Setup uses during the installation. By default, the Config.xml file that is stored in the core product folder directs Setup to install that product. For example, the Config.xml file in the Pro.WW folder installs Microsoft Office Professional 2007.

You can edit Config.xml to make additional customizations to the installation. These customizations can include specifications for one or more language versions to install. Use /config on the Setup command line to point to the location of the default Config.xml file for a particular product or to point to a custom Config.xml file.

An example of the /config [path] option is as follows.

\\server\share\Office12\setup.exe /config \\server\share\Office12\Pro.WW\Config.xml

In this example, "Office12" is the root of the network installation point.

Note You must use a fully qualified path. Setup does not recognize relative paths when it uses the /config option.

/modify [ProductID]

This command-line option is used together with a modified Config.xml file to run Setup in maintenance mode and to change to an existing Office installation. For example, use this option when you want to add or remove languages. Look up the value of [ProductID] in the Setup.xml file for the product that you want to modify.

The Setup.xml file is located in the core product folder on the network installation point. In Setup.xml, [ProductID] is equal to the value of the Id attribute of the Setup element. For example the [ProductID] value may be as follows:

<Setup Id="Pro" Type="Product" ProductCode="{30120000-0011-0000-0000-1000000FF1CE}">

An example of the /modify [ProductID] option is as follows.

\\server\share\Office12\setup.exe /modify Pro /config \\server\share\Office12\AddOutlookConfig.xml 

In this example, "Office12" is the root of the network installation point.

/repair [ProductID]

This command-line option runs Setup to repair the specified product. Look up the value of [ProductID] in the Setup.xml file for the product that you want to modify.

An example of the /repair [ProductID] option is as follows.

\\server\share\Office12\setup.exe /repair Pro 

In this example, "Office12" is the root of the network installation point.

/uninstall [ProductID]

This command-line option removes the specified product from the user’s computer. Look up the value of [ProductID] in the Setup.xml file for the product that you want to modify. You can use the /uninstall option on the command line together with the /config option.

An example of the /uninstall [ProductID] option is as follows.

\\server\share\Office12\setup.exe /uninstall Pro 

In this example, "Office12" is the root of the network installation point.

Note In the 2007 Office suites, you cannot set Windows Installer properties, such as PIDKEY or DISPLAY, by using the Setup.exe command line. Setup does not pass these properties to Windows Installer. Instead, make these customizations by using the Office Customization Tool or Config.xml.

For a complete list of Setup properties that includes blocked and unsupported properties, visit the following Microsoft Web site:

Back to the top

Setup command-line options in Visio 2003

In Visio 2003, the default values for Setup properties are defined in the Windows Installer package (.msi file). You can specify new property values by using the command line or by modifying the Setup settings file (Setup.ini).

Note Usually, command-line options override duplicate customizations in the Setup settings file (Setup.ini) or in a transform (.mst file). Command-line options and properties are not supported by all .msi files.

The following is a list of command-line options that you can use with the Visio 2003 Setup program (Setup.exe):

•	/a [msifile] Use this command-line option to create an administrative installation point for the Windows Installer package (.msi file) that you specify. The Windows Installer package (.msi file) and the Setup.exe file must be in the same folder, and both files must be located in the root folder of the administrative installation point. Examples: • /a Vispro.msi • /a "Folder1\Vispro.msi" Note You can only use the /a command-line option with the Setup.exe file to perform an administrative installation of Visio if you have an Enterprise version of Microsoft Office Visio 2003 Standard or Microsoft Office Visio 2003 Professional. If you try to perform an administrative installation by using a retail version of Visio, you receive the following error message: Creation of administrative installation images is supported only in Enterprise versions of Microsoft Office Visio Edition 2003.
•	/f[options] [msifile] Use this command-line option to force a repair of Visio. The Windows Installer package (.msi file) and the Setup.exe file must be in the same folder, and both files must be located in the root folder of the administrative installation point. Alternatively, you can specify the product code for the Windows Installer package. You can copy the product code from the [Product] section of the Setup settings file (the Setup.ini file). Note You must specify the same Windows Installer package that you used to originally install Visio. The following table lists the values that you can use for the options parameter: Option Description --------------------------------------------------------------------------------------------------------- a Force reinstallation of all files, regardless of the checksum or version. c Reinstall a file if the file is missing or damaged. d Reinstall a file if the file is missing or if a different version is present. e Reinstall a file if the file is missing or if the same or earlier version of the file is present. m Rewrite all required HKEY_LOCAL_MACHINE registry entries. o Reinstall a file if the file is missing or if an earlier version is present. p Reinstall a file only if it missing. s Reinstall all shortcuts and overwrite existing shortcuts. u Rewrite all required HKEY_CURRENT_USER registry entries. v Retrieve the package from the original source and recache it on the local computer. Notes • Using the Setup.exe file with the /focums command-line option performs the same operations as if you run Setup and you select the Detect and Repair errors in my Visio installation option. • Using the Setup.exe file with the /fecums command-line option performs the same operations as if you run Setup and you select the Reinstall Visio option. When you install Visio, Windows Installer saves the .msi file to the local computer. • If you use the Setup.exe file with the /fvm command-line option to force a recache and reinstallation operation, Windows Installer retrieves the .msi file from the original source and recaches it on the local computer. You can use the /fvm command-line option to update client computers after you apply an update to an administrative installation point Important If a user applies a client update to a computer, you cannot use the /f command-line option to recache and reinstall Visio on that computer by using an administrative installation point that you updated. In this situation, the user must remove Visio, and then reinstall Visio from the administrative installation point that you updated. Examples: • /fpiwae Vispro.msi • /fvm {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx} In this example, x represents a number between 0 (zero) and 9.
•	/i [msifile] Use this command-line option to install Visio by using the Windows Installer package file (.msi file) that you specify. The Windows Installer package (.msi file) and the Setup.exe file must be in the same folder. Examples: • /i Vispro.msi • /i "Folder1\Vispro.msi"
•	/j[option] [msifile] [/t mstfile] Use this command-line option to advertise Visio on the computer and install Visio on first use. You must specify whether you want to advertise Visio to either all users on the computer or only to the current user. You can use the /j command-line option only when you run Setup from an administrative installation point or from an image of the CD on the network. If you do not specify a Windows Installer package, Setup uses the Windows Installer package that is specified in the Setup.ini file. To apply a transform, use the /t command-line option, and then specify a .mst file. The following table lists the values that you can use for the option parameter: Option Description ---------------------------------------------------- m Advertise to all users on the computer. u Advertise to the current user on the computer. Note When you use the /j command-line option to advertise Visio, you can also use the /l, /q, and /settings command-line options. Example: • /jm Vispro.msi /t MyTransform.mst
•	/l[options] [logfile] Use this command-line option to create a log of installation actions for Setup and to create a log file for each Windows Installer task. This command-line option overrides the default settings that are specified in the [Logging] section of the Setup.ini file. The following table lists the values that you can use for the options parameter: Option Description --------------------------------------------------------------------------------------- a Start of action notification c Initial user interface (UI) parameters e Error messages i Information-only messages m Out-of-memory messages o Out-of-disk-space messages p Property table list in property=value format r Action data record that contains action-specific information u User request messages v Verbose log, includes debug messages w Warning messages * Turn on all logging options except the v option + Append to existing log file The logfile parameter represents the name and path of the log file. When you use"(*)" (without the quotation marks) in the name of the log file, Setup creates a unique log file name every time that you run Setup. Example: • /lv* "%temp%\MyLog(*).txt" This command-line option creates the following two log files: • The Setup.exe log file: %temp%\MyLog(0001).text • The Windows Installer log file for core packages %temp%\MyLog(0001)_Task(0001).txt
•	/noreboot Use this command-line option to specify that you do not want to restart the computer or display a restart dialog box at the end of the installation . This command-line option sets the Windows Installer REBOOT property to ReallySuppress for each package that is included in the installation except the last package.
•	/p [mspfile] Use this command-line option to apply an administrative update (.msp file) to a client installation. You can also use the /p command-line option to apply an update to an administrative installation by including the /a command-line option and the name and path of the .msi file on the administrative installation point. To apply the update quietly, use the /qb command-line option. To generate a log file, use the /l command-line option. Examples: • msiexec /p mspfile /qb /loptions • msiexec /p mspfile /a msifile/qb /loptions
•	/q[option] Use this command-line option to set the display level that you want for the user interface. The following table lists the values that you can use for the option parameter: Option Description ----------------------------------------------------------------------------------------------------------- b Basic: Display only simple progress indicators and error messages. f Full: Display all dialog boxes and messages. This setting is the same as when you omit the /q option. n None: Display no user interface. This setting is same as when you use /q option with no parameters. r Reduced: Display all progress indicators and error messages but do not collect any user information. - Suppress all modal dialog boxes. Use only with the b option. + Add completion message to either the n or the b option. The completion message is displayed only when Setup does not have to restart the computer after the installation.
•	/settings file Use this command-line option to specify a custom Setup settings file for the Setup.exe file to use instead of the Setup.ini file. The custom settings file that you specify and the Setup.exe file must be in the same folder. Or, you must specify the path of the custom settings file in the command line. Example: • /settings MySetttings.ini
•	/x [msifile] Use this command-line option to remove Visio. The Windows Installer package (.msi file) and the Setup.exe file must be in the same folder, and both files must be located in the root folder of the administrative installation point. Note You must specify the same Windows Installer package that you used to originally install Visio. Example: • /x Vispro.msi
•	property=value Use this command-line option to specify a property value on the command line. If the value contains spaces, insert quotation marks (") around the value. To specify two or more property=value pair, separate each pair with spaces. The following table describes the property=value pairs that you can use: Property=Value Description --------------------------------------------------------------------------------------------------------------------- ALLUSERS=[string] Install Visio for all users of the computer or for only the current user. By default, Windows Installer installs for all users of the computer. Setting ALLUSERS to a null value ("") overrides this default behavior and installs per user. 1 = Install for all users of the computer. Requires administrative credentials. 2 = Install for all users of the computer. "" = Install only for the user who is running Setup. Example: ALLUSER="" CDCACHE=[string] Specify the level of caching. Auto = cache based on available disk space 1 = cache only what you install 2 = cache the whole source 0 = cache disabled Example: CDCACHE=auto COMPANYNAME=[string] Specify an organization name. Example: COMPANYNAME=My Business INSTALLLOCATION=[string] Specify the installation location. Example: INSTALLLOCATION=C:\Program Files\MyApp LOCALCACHEDRIVE=[string] Specify the drive that the installation files are cached to. Example: LOCALCACHEDRIVE=C PIDKEY=[string] Specify a 25-character product key on the Setup command line or in the Setup settings file. When you set the PIDKEY property, users do not have to enter a product key when the users install Visio. Example: PIDKEY=123467890123456789012345 TRANSFORMS=[string] Specify a transform to apply to the installation. Example: TRANSFORMS=\\Server1\MyShare\MyApp\MyTransform.mst USERNAME=[string] Specify a default user name. Example: USERNAME=User1

For more information about Visio 2003, visit the following Microsoft Web site:

Back to the top