Microsoft Visio 2002 Resource Kit

Archived content. No warranty is made as to technical accuracy. Content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

Chapter 4 - Installing and Customizing Visio 2002 SR-1

Deploying Microsoft Visio 2002 SR-1 from an administrative installation point gives you the most flexibility and control over the installation process. After you install the files on a network share, you can determine how much users interact with Setup and which Visio features are available to them. You can specify default settings for most options and even chain additional Windows Installer packages to the Visio installation. Users can run Setup from the network or the Visio CD, or you can distribute Visio by using a hard-disk image or management services tool such as Microsoft Systems Management Server.

On This Page

Creating an Administrative Installation Point
Running Administrative Setup for Microsoft Visio
Replicating the Administrative Image
Customizing the Visio Installation
Customizing How Setup Runs
Customizing Visio Features and Shortcuts
Including Additional Packages in the Visio Installation
Customizing Removal Behavior
Distributing Visio to Users' Computers
Deploying Service Releases and Updates

Creating an Administrative Installation Point

The most common method of deploying a customized version of Microsoft Visio 2002 SR-1 to a large number of users is to create an administrative installation point on a network server and have users run Setup from there. This method provides several advantages over installing Visio from the Visio CD, and allows you to do the following:

• Manage one set of Visio files from a central location.

• Create a standard Visio configuration for all users.

• Take advantage of flexible installation options.

  For example, set Visio features to be installed on first use, or deploy the Visio package through Microsoft Windows 2000 software installation, or use Systems Management Server to install Visio.

• Manage controlled upgrades of Visio in the future.

Running Administrative Setup for Microsoft Visio

To distribute Visio from a network server, you must first install Visio on an administrative installation point by running Setup with the /a command-line option. Then you can customize your Visio configuration before running Setup on users' computers.

To create an administrative installation point for Visio 

1. Create a network share on a network server for the administrative installation point.

   The network share must have at least 300 megabytes (MB) of available hard-disk space.

2. On a computer that has write access to the network share, connect to the server share.

   The computer must be running a supported operating system: Microsoft Windows 2000 or later, Microsoft Windows NT 4.0 Service Pack 6a (recommended), Microsoft Windows Millennium Edition (Windows Me), or Microsoft Windows 98.

3. On the Start menu, click Run, and then click Browse.

4. On the Visio CD, double-click setup.exe, and add /a to the command line.

5. Enter the organization name that you want to define for all users who install Visio from this administrative installation point.

6. Enter the server and network share you created as the installation location.

7. Enter the 25-character product key and click Next.

   You must enter a valid product key when you create the administrative installation point; users who install Visio from this administrative image do not need to enter the product key when they install Visio or start Visio for the first time.

8. Accept the end-user license agreement, and then click Install.

   By accepting the agreement here, you are accepting on behalf of all users who install Visio from this administrative installation point.

Setup copies the files from the Visio CD to the administrative installation point and creates a hierarchy of folders in the root folder of the network share. The System Files Update is automatically included during an administrative installation.

Note   When you install Visio under Windows 2000 and you set features to run from the network (Run from Network or Run All from Network), you must create your administrative installation point in a subfolder on the network share; for example, \\server\share\admin_install_point\setup.exe. If Setup.exe is stored at the root of the network share, Visio features do not run properly.

The following table identifies the location of key files on the Visio administrative image.

File	Location
Setup.exe	Root of the administrative image
Visio 2002 SR-1 MSI file	Root of the administrative image
System Files Update MSI file	Files\Osp\<LCID>
Setup.ini	Files\Setup

Setup also modifies the Windows Installer package for Visio, identifying it as an administrative installation package and setting the ProductID and COMPANYNAME properties accordingly. After you create the administrative installation point, you make the network share available to users by providing them with read access.

When users run Setup to install Visio, any Visio features that are installed to run from the network use this administrative installation point as the source of Visio files, and Visio runs the features over the network from this server. Similarly, for features that are set to be installed on first use, Visio copies files from this server when needed. If you install features in one of these two states, you must keep this network server available to users.

When users install Visio from the administrative installation point, Setup uses the organization name that you specify as the default. In the Custom Installation Wizard, you can create a Windows Installer transform (MST file) that modifies the organization name during installation. This flexibility allows you to create different organization names for different groups of users in your organization.

You can specify the organization name on the Specify Default Path and Organization page of the wizard, or you can set the COMPANYNAME property on the Modify Setup Properties page. You can also specify an organization name on the Setup command line or in the Setup settings file (Setup.ini), but in this case you must leave the organization name blank when you create the administrative installation point.

Note   The Microsoft Office XP Resource Kit includes the Custom Installation Wizard as part of the core tool set. The Custom Installation Wizard is installed by default when you run the Office XP Resource Kit Setup program. For more information on the wizard, see "Custom Installation Wizard" in the Office XP Resource Kit Toolbox.

Replicating the Administrative Image

In many organizations, it makes sense to create multiple administrative installation points from which users can install Visio—and to which Windows Installer can connect to install or repair Visio features. As long as you use relative paths for any customizations that include paths, you can copy the complete folder hierarchy and files from one administrative installation point to multiple servers. If you copy the folders, each new administrative image that you create has the same default organization name specified in Setup.

You list the paths to the servers that contain replicated administrative installation points on the Identify Additional Servers page of the Custom Installation Wizard.

System Files Update language versions

You can copy the language versions you need to the Files\Osp folder on the administrative installation point. By default, Setup installs the language version that matches the language of the operating system; otherwise, Setup installs the English version.

Internet Explorer 5.5 or later

Visio 2002 SR-1 includes Internet Explorer 5.01, which is located in the Files\Osp\<LCID>\IE5 folder on the administrative installation point. To install Internet Explorer 5.5 on computers running Windows NT 4.0 or Windows 98, replace the IE5 folder with a folder that contains the configuration you want. The alternate version is installed during the System Files Update portion of the Visio installation.

Note   Because the System Files Update detection and installation process does not run under Windows 2000 or Windows Me, you must deploy Internet Explorer 5.5 separately, before you deploy Visio, on these operating systems. For more information, see the Internet Explorer Web site.

Customizing the Visio Installation

 

After you create an administrative installation point for Microsoft Visio 2002, you can make extensive customizations before installing Visio on users' computers. You can also customize many aspects of the installation process itself, as shown in the following diagram:

 

Many of the customizations you make to a Visio installation can be accomplished by one of several methods:

• Specifying options on the command line.

• Modifying the Setup.ini file with the Setup INI Customization Wizard.

• Creating a transform (MST file) with the Custom Installation Wizard.

The following table shows packages (MSI files) related to Visio that you can customize, and it provides recommended methods for different types of customizations.

Customization	MSI file	Command line	INI file	MST file
Setup process (display, logging, installation location, organization name, and so on)	Visio.msi	x	x	x
Internet Explorer installation and settings	Osp.msi	x	x	x
Visio features, added files, and shortcuts	Visio.msi			x
Other user settings	Visio.msi			x
Removal options	Visio.msi			x
Chained packages	Chained.msi		x

Note   When customizing an installation of Visio, always use the Setup INI Customization Wizard or the Custom Installation Wizard. Do not attempt to customize the MSI file directly. The Office XP Resource Kit core tool set includes the Custom Installation Wizard and the Setup INI Customization Wizard. These tools are installed by default when you run the Office XP Resource Kit Setup program. For more information, see the Office XP Resource Kit Toolbox.

Working with Setup properties

Setup properties control many aspects of the installation process, including the following:

• Display settings, logging options, and other properties used by Setup to manage the installation process.

• Properties that customize button labels and descriptive text in the Setup user interface.

• Properties that control how Visio features are installed.

• Properties that determine how Microsoft Internet Explorer is installed with Visio.

The default values for Setup properties are defined in the Windows Installer package (MSI file). You can specify new values on the command line, in Setup.ini, or on the Modify Setup Properties page of the Custom Installation Wizard. During the installation, Setup passes all Setup property values to Windows Installer.

Most properties are passed only during the call to install Visio, except for the following:

• Global display settings (/qoption) are passed to every installation included with Visio.

  For example, when you specify /qb on the command line, Setup displays simple progress indicators and error messages throughout the entire installation. To install the System Files Update unattended, you must set other properties in the Setup.ini file.

• NOIE is passed during the call to install the System Files Update.

  When NOIE is set to True, Setup does not install or give the user the option to install Internet Explorer 5.01.

• When specified on the command line, SOURCELIST is passed to the System Files Update and any chained packages. Note   You can find detailed information about Setup command-line options and properties in Setupref.doc, which is installed by default when you run the Office XP Resource Kit Setup program. This document also describes the format of the Setup settings file. For more information, see Supplemental Documentation in the Office XP Resource Kit Toolbox.

For more information about Windows Installer, including online Help and other documentation, see the Microsoft Platform SDK on MSDN.

Specifying options on the command line

When you run Setup, you can use command-line options to change some of the parameters that Setup uses to install Visio. By using command-line options, you can do the following:

• Identify the package (MSI file) and transform (MST file).

• Specify a custom Setup settings file (INI file).

• Direct Setup to run in unattended mode.

• Set Windows Installer logging options.

• Change default values of Setup properties.

For example, you can enter the following options on the command line:

setup.exe /qb+ /l* %temp%\Visio2002.txt COMPANYNAME="Championzone"

This command line customizes Setup in the following ways:

• Setup does not prompt the user for information, but displays progress indicators and a completion message when it installs Visio (/qb+).

• Windows Installer logs all information and any error messages (/l*) for Setup.exe to the file \<Temp>\Visio2002.txt on the user's computer.

  Logging information for the System Files Update is recorded in \<Temp>\Visio2002_Task(0001).txt; logging information for the Visio package is recorded in \<Temp>\Visio2002_Task(0002).txt.

• Setup sets the default organization name to <Blank>.

• Because no custom INI or MST file is specified, Setup installs the same Visio features that it would if the user clicked Install Now in the Setup user interface.

When to use command-line options

The Setup command line is most useful when you have few customizations to make, or when you want to create several different installations quickly. You can use one custom INI file or apply the same MST file to install a basic Visio configuration to everyone, but define different command lines for targeted groups of users.

For example, you can have your Engineering and Accounting departments install the same set of Visio features and settings but specify unique organization names. In the administrative installation point, you create two shortcuts that have the following command lines:

setup.exe /q /settings Custom.ini COMPANYNAME="Engineering Department"
setup.exe /q /settings Custom.ini COMPANYNAME="Accounting Department"

Command-line options are also useful if you use Microsoft Systems Management Server or another systems management tool to create multiple deployment packages, each of which requires a different command line.

Tip   Any settings that you can specify on the command line can also be added to Setup.ini—including the command line itself. For extensive or complex customizations, use Setup.ini to make the installation process easier to track and troubleshoot.

How to distribute command-line options

When users double-click setup.exe on the administrative installation point, Setup runs with no command-line options. To apply your custom command-line options, users must click Run on the Windows Start menu and enter the path to Setup.exe, along with your command-line options.

To simplify this process, you can create in MS-DOS a batch file that runs Setup.exe with your command-line options. Or you can create a Windows shortcut and add your custom options to the command-line box. Users double-click the batch file or shortcut to run the Setup command line that you have defined. You can store the batch file or shortcut in the root folder of the administrative installation point.

If you run Setup from a network log-on script or through a systems management tool (such as Systems Management Server), you can add your custom options to the Setup command line in the script or deployment package.

Customizing the Setup settings file

Before applying the values specified on the command line, Setup reads the properties specified in the Setup settings file (Setup.ini), where you can set all the properties that you can on the command line. For example, you can:

• Identify the MSI and MST files to use in the [MSI] and [MST] sections.

• Direct Setup to run in unattended mode in the [Display] section.

• Set logging options for Windows Installer and Visio Setup in the [Logging] section.

• Change the default values of Setup properties in the [Options] section.

The Setup.ini file for Visio also contains several new sections that allow you to specify settings that you cannot add to the command line. For example:

• Customize the System Files Update separately from Visio in the [SystemPack] and [SystemPackOptions] sections.

• Chain multiple Windows Installer packages to your core Visio installation in the [ChainedInstall_n] sections.

In most sections of Setup.ini, including the [Options] and [SystemPackOptions] sections, you use the syntax PROPERTY=value to specify custom property values. In the [ChainedInstall_n] sections, you can set the DISPLAY and MST values with this syntax; however, you must use the CMDLINE property to add other options to the command line that Setup passes to Windows Installer for a chained package.

The Office XP Resource Kit includes a new tool—the Setup INI Customization Wizard (Iniwiz.exe)—that provides a convenient user interface for creating or modifying custom Setup settings files. The wizard automatically enters the settings that you select into the correct section of the settings file, and it creates a command line that includes the /settings option and specifies your custom INI file.

Note   The Microsoft Office XP Resource Kit core tool set includes the Setup INI Customization Wizard, which is installed by default when you run the Office XP Resource Kit Setup program. For more information, see "Setup INI Customization Wizard" in the Office XP Resource Kit Toolbox.

When to use a custom INI file

Because the Setup settings file organizes Setup options in an easy-to-read format, it is more convenient to use than long or complex command lines. If you use Setup.ini to set most Setup properties, you can reserve the command line for specific and targeted modifications, or for changes that you need to make late in the deployment process.

If you want to chain Windows Installer packages to your core Visio installation, you must enter the MSI files by adding the name and path in the Setup INI Customization Wizard or in the [ChainedInstall_n] section of Setup.ini.

Other scenarios in which the Setup settings file is the best customization method to use include the following:

• You want users to run Setup.exe directly from the administrative installation point, instead of creating a batch file or shortcut to install a customized version of Visio.

• You want to override global display settings (that is, the display settings specified for Visio) and set unique display settings for the System Files Update or other chained packages.

• You want to set additional options for the System Files Update or a chained package, such as specifying a transform to apply.

How to use the Setup INI Customization Wizard

The Setup INI Customization Wizard provides a convenient user interface for creating custom versions of the Setup settings file. The wizard also helps to prevent you from inadvertently specifying conflicting settings and automatically generates a Setup command line that includes the /settings switch and the name and path to your custom INI file.

Before you can use the Setup INI Customization Wizard, you must create a Visio administrative installation point. Your custom INI file must be based on an existing INI file, such as the Setup.ini file for Visio.

To create a custom Setup.ini file 

1. Enter the path to your Visio administrative installation point and click Next.

   The wizard searches the specified network share for a Setup.ini file.

2. Select an INI file from the administrative installation point on which to base your custom INI file, or click Browse to go to a different location, and then click Next.

3. Under Logging, select a logging mode and enter a name for the log file or template.

   To use the logging mode specified in the INI file, click Default; to use all logging options, click Verbose. Note that verbose logging creates very large log files.

4. Under Display, select a default display setting, and then click Next.

   The wizard searches the administrative installation point for additional packages (MSI files) that you can chain to the Visio installation.

5. Select the check boxes next to the packages that you want to include in your custom INI file, add packages or programs (EXE files) stored in another location, and then click Next.

6. Use the arrow keys to determine the order in which you want Setup.exe to install the chained packages.

   The System Files Update package is always installed first (if required), followed by the Visio package. You can change the order in which subsequent chained packages are installed.

7. Select each package, specify the options you want for that package, and then click Next.

   For each package, you can specify an MST file and a unique display setting, as well as additional property values.

8. To add additional property-value pairs to your custom INI file, select a package, click Advanced Properties, enter the properties and values you want, and then click Next.

   The wizard displays a summary of the changes to save in the custom INI file.

9. Click Save As and enter a name and path for your INI file, and then click Finish to exit the wizard.

   The wizard supplies you with a sample Setup command line that specifies your custom INI file with the /settings option.

Note   Do not overwrite the original Setup.ini file. If you want Setup to use your custom INI file, copy Setup.exe and rename it to match the name of your custom INI file. In this case, Setup uses your custom INI file by default, and you do not need to use the /settings option.

How to distribute a custom INI file

When you edit the default Setup settings file (Setup.ini), users can run Setup without using command-line options to install Visio with your customizations.

To create multiple custom installations that use different Setup options, you can create several custom INI files that have different names and store them in the root folder of the administrative installation point. Users specify the name of a settings file by using the /settings Setup command-line option. You can simplify this process by creating an MS-DOS batch file or Windows shortcut that contains the appropriate /settings command-line option.

Note   If your custom INI file is stored in any location other than the folder that contains Setup.exe, you must include the relative or absolute path with the /settings option. For example:Setup.exe /settings \\server\share\files\setup\vis10eng.ini

If you run Setup from a network log-on script or through a systems management tool (such as Systems Management Server), you must edit the Setup command line in the script or deployment package to refer to the appropriate settings file by using the /settings option.

You can create multiple custom INI files for different groups of users. For example, you might want to deploy Visio Standard and Office XP to your Accounting department but give users in your Engineering department Visio Professional. In this case, you can create two custom INI files: one that chains Visio Standard packages and another that chains the Visio Professional package. Users in each department run Setup by using one of the following command lines:

setup.exe /settings vis10act.inisetup.exe /settings vis10eng.iniNote   When you create a custom INI file, you can also specify options on the Setup command line. If you specify a command-line option that conflicts with a value in the INI file, Setup uses the command-line option.

Storing values in a transform

When you install Visio from an administrative installation point, you can customize the Visio configuration that is installed on users' computer by applying a Windows Installer transform (MST file). Many of the customizations that you make in Setup.ini or on the command line can also be made in a transform, but some tasks are better handled in a transform. For example, a transform is typically used to set default installation states for Visio features or to specify default application settings.

You create a Windows Installer transform by using the Office XP Custom Installation Wizard. The transform contains the changes that you want to make to the Windows Installer package (MSI file). When you apply the transform during the installation, your modifications become the default settings for anyone who runs Setup from your administrative installation point. If you run Setup in unattended mode (with no user interaction), your selections define precisely how Visio is installed on users' computers.

Note   The Office XP Resource Kit core tool set includes the Custom Installation Wizard, which is installed by default when you run the Office XP Resource Kit Setup program. The wizard includes a detailed Help file. For more information, see "Custom Installation Wizard" in the Office XP Resource Kit Toolbox.

When to use a transform

A Windows Installer transform is most useful when you want to make extensive customizations, particularly customizations that you cannot readily make by using the Setup command line or Setup settings file. By creating multiple transforms, you can also install different Visio configurations to different groups of users from the same administrative installation point.

When you create a transform, the Custom Installation Wizard allows you to do the following:

• Define the path where Visio is installed on users' computers.

• Define the default installation state for all Visio features.

  For example, not all users may need to have the engineering solutions installed locally. You could set these solutions to Install on Demand to make them available to users as they need them. You can also hide and lock features so that users cannot make changes after Visio is installed.

• Add your own files and registry entries to Setup so that they are installed with Visio.

• Modify Visio feature shortcuts, specifying where they are installed and customizing their properties.

• Define a list of servers for Visio to use if the primary administrative installation point is unavailable.

• Specify other products to install or programs to run on users' computers after Setup is completed.

You can create transforms for other chained Windows Installer packages, including the System Files Update. By using the Microsoft Internet Explorer Administration Kit (which you can call from the Custom Installation Wizard), you can also customize how Internet Explorer is installed on users' computers during the System Files Update installation.

How to apply a transform during Visio installation

For users to install Visio with your customizations, you must specify the name and path to the transform by setting the TRANSFORMS property on the command line or by adding an entry to the appropriate section of the Setup settings file.

For example, to direct Setup to use the transform Custom.mst (stored in the same folder as Setup.exe), you use the following Setup command line:

setup.exe TRANSFORMS=custom.mst

You can also specify a transform in the Setup INI Customization Wizard. In the Transform (MST file) to apply during installation box, select the Visio package and enter <path> Custom.mst. This step adds the following entry to the [MST] section of Setup.ini:

MST1=Custom.mst

On the same page of the wizard, you can select other packages that you added to the installation—including the System Files Update and chained packages—and specify a transform. The wizard records this information in the appropriate sections of Setup.ini. (Note that the property used to specify a transform for the System Files Update differs from other packages included in Setup.ini.) For example:

[SystemPackOptions]
TRANSFORMS=SystemPack.mst
[ChainedInstall_1]
MST=French.mst

Note   If you incorrectly enter this property on the command line as TRANSFORM (not plural) setup.exe will display an error message. However, if you add it to the Setup.ini file [Options] or [SystemPackOptions] sections as TRANSFORM instead of TRANSFORMS, the property is ignored. You can avoid this error by using the Setup INI Customization Wizard to specify a transform for the System Files Update.

If you create unique transforms for different groups of users, you must specify—on the command line or in Setup.ini—which transform to use. For example, users in your Accounting department might need some of the add-ons included with Microsoft Visio, and users in the Engineering department might need others, such as the Electrical Engineering solution. In this scenario, you can create different transforms that specify different feature installation states for Visio features, and then create two shortcuts on the administrative installation point by using the following command lines:

setup.exe TRANSFORMS=vis10eng.mst
setup.exe TRANSFORMS=vis10act.mst

Resolving conflicting Setup options

Visio offers many ways to customize its installation, and using a combination of methods can result in conflicting settings. If you specify different values for the same Setup options on the Setup command line, in the Setup settings file, and in a transform, Setup uses the following rules to determine which value to use:

• If you set an option in the Custom Installation Wizard that corresponds to a Setup property, the wizard sets the corresponding property automatically in the MST file.

  For example, if you select the Upgrade to Internet Explorer 5 option on the Customize Internet Explorer 5 Installation Options page, the wizard sets the NOIE property to False. 

• If you modify a Setup property on the Modify Setup Properties page of the Custom Installation Wizard, this setting overrides any corresponding options that you set on previous pages of the wizard. Your modified Setup property is written to the MST file.

• If you set options (including Setup properties) in the Setup settings file that conflict with options in the transform, the values in the INI file take precedence over the transform.

• If you set options on the command line, those settings take precedence over any conflicting values in either the INI file or the transform.

Customizing How Setup Runs

 

You can always run Setup interactively to install Microsoft Visio 2002—or allow users to run Setup interactively. However, by using command-line options or setting values for Setup properties in the Setup settings file (Setup.ini) or in a transform (MST file), you can customize the way Setup installs Visio throughout your organization.

You can set most properties that control the behavior of Setup in one of three locations, listed in order of precedence:

• On the command line

• In the Setup settings file (Setup.ini)

• On the Modify Setup Properties page of the Custom Installation Wizard, which stores your settings in a transform (MST file)

Note that settings specified on the Modify Setup Properties page override any corresponding settings specified on previous pages of the wizard.

Note   The Office XP Resource Kit core tool set includes the Custom Installation Wizard and Setup INI Customization Wizard. These wizards are installed by default when you run the Office XP Resource Kit Setup program. For more information, see Custom Installation Wizard or Setup INI Customization Wizard in the Office XP Resource Kit Toolbox.

Display settings

When you distribute Visio throughout an organization, you can determine how much of the Setup user interface is displayed to users. You can allow users to interact fully with Setup and make choices that differ from the defaults you specify, or you can run Setup unattended so that your configuration of Visio is installed with no questions asked. You can even set different display settings for different portions of the installation process.

The following display settings are available:

• None 

  No user interface is displayed; Visio is installed unattended.

• Basic 

  Only simple progress indicators and error messages are displayed. To display only progress indicators, append a minus sign to the command-line option (/qb-).

• Reduced 

  Full progress indicators and error messages are displayed, but Setup collects no information from the user.

• Full 

  All dialog boxes and messages are displayed to the user, and the user can enter information during the Setup process.

When you run Visio Setup unattended or with only the basic user interface, you can also determine whether users see a completion message when the installation is finished. A completion message is displayed only when Setup does not have to restart the computer to complete the installation.

You set all these display options on the command line by using the /q switch or in the [Display] section of Setup.ini, as shown in the following table. In the Setup INI Customization Wizard, you select a value for the DISPLAY property in the Default display setting box.

Display setting	Command-line option	Setup.ini value
None	/q or /qn	DISPLAY=None
Basic	/qb or /qb-	DISPLAY=Basic
Reduced	/qr	DISPLAY=Reduced
Full	/qf	DISPLAY=Full
Completion message on	+ (e.g., /qn+ or /qb+)	COMPLETIONNOTICE=Yes

Display settings like the /q option are passed globally to every installation. For example, if you set this option on the command line or in the [Display] section of Setup.ini, all Visio–related installations, including the System Files Update, are installed with the same level of user interface, unless you set a different display setting for just those packages.

Note   You can find detailed information about Setup options and properties in Setupref.doc, which is installed by default when you run the Office XP Resource Kit Setup program. This document also describes the format of the Setup settings file. For more information, see "Supplemental Documentation" in the Office XP Resource Kit Toolbox.

Install Visio unattended

By default, Setup installs Visio with a full user interface and displays a completion message at the end of the installation. In many large organizations, however, it is more efficient to install Visio without any user interaction. In this case, the recommended setting is /qb-, which installs Visio as follows:

• Progress indicators are displayed during the installation.

• Error messages and other modal dialog boxes are not displayed.

• Setup restarts the computer automatically, if a restart is required (for example, when Internet Explorer is installed).

• Setup displays a completion message when the installation is finished.

When you run Visio Setup with a basic or reduced display, users can still click the Cancel button to stop the installation process. However, if you set the NOCANCEL property to True, the Cancel button is displayed but is unavailable. Users know that the installation is occurring and they know when it is complete, but they cannot interrupt the process.

You can install Visio with no user interface whatsoever by using the /qn option or setting the DISPLAY property to None. If you are using a deployment tool such as Microsoft Systems Management Server to run the installation when users are not logged on, you must use this display setting.

Set unique display settings for other packages

In some circumstances, you might want to specify different display options for different packages installed with Visio. You must use Setup.ini to override global display settings set on the command line or in the [Display] section of Setup.ini.

For example, if you install Visio with a full user interface, you can install the System Files Update quietly to ensure that system files and Internet Explorer are updated the same way for every user. In this case, you enter the following in the [SystemPack] section of Setup.ini:

[SystemPack]
DISPLAY=Basic

You can modify display settings for all chained packages at once by using the Setup INI Customization Wizard. The wizard adds the correct entries to the correct sections of the INI file and helps prevent you from inadvertently specifying conflicting settings.

To modify display settings by using the Setup.ini Customization Wizard 

1. Start the Setup INI Customization Wizard and enter information about your administrative installation point, Setup settings file, and packages to include in the installation.

2. Select the package for which you want to change display settings and select a new value in the Display setting box.

Note   If you specify a display setting on the command line, that setting overrides any display settings specified in any section of Setup.ini.

Customize the Setup user interface

When you run Visio Setup with a full user interface, you can customize some of the text and buttons that users see by setting properties on the command line, in Setup.ini, or on the Modify Setup Properties page of the Custom Installation Wizard.

For example, if a user selects the Customize option, Setup prompts the user for the installation location and then displays a list of Visio features or a hierarchy of Visio features so that the user can select an installation state for each one. You can change descriptive text for the Customize option. For example, if you have omitted the Database solution from the installation, but you want to tell users how to install it for themselves, specify the following:

CUSTOMINSTALLDESCRIPTION="By default the Database solution is not 
installed. Click Customize to install the Database solution on your 
computer."

You can also customize the descriptive text for the Typical, Complete, and Run from Network options. Similar properties customize the Install Now and Upgrade Now button labels and descriptive text. All of these properties are defined in the following table.

Property	Default value
TYPICALINSTALLTEXT	&Install Now
TYPICALUPGRADETEXT	&Upgrade Now
TYPICALINSTALLDESCRIPTION	Installs Visio with the default settings, including the most commonly used components.
TYPICALUPGRADEDESCRIPTION	Upgrades your Visio installation. Setup will remove your previous versions, and install based on your current configuration.
RUNFROMSOURCEINSTALLDESCRIPTION	Installs only the files that must be copied to your computer. Access to the installation source will be required to run Visio.
CUSTOMINSTALLDESCRIPTION	Customize your Visio installation, selecting which Visio features and features to install on your computer.
COMPLETEINSTALLDESCRIPTION	Installs all of Visio on your computer, including all optional components.

In Microsoft Windows 2000 only, you can also customize what users see in Add/Remove Programs when they run Visio Setup in maintenance mode. For example, to prevent users from changing an installed Visio configuration, you can set the Setup property ARPMODIFY to True in a transform. When users run Visio Setup in maintenance mode, the Change button in Add/Remove Programs is unavailable.

Logging options

Both Visio Setup and Windows Installer generate log files during the installation process. You cannot set options for the Setup log file; however, Windows Installer allows you to set a number of logging options that apply to each package that it installs during Visio Setup. Note that any logging options you set apply to all log files created by Windows Installer during the Visio installation.

You set Windows Installer logging options and specify a log file name on the command line by using the /l option. For example:

/lv+ "Visio Setup(*).txt"

Note   If your custom log file name includes spaces, you must enclose it in quotation marks on the command line.

You can set the same options by specifying values in the [Logging] section of the Setup settings file. Valid logging options include the following.

Option	Information written to the log file
I	Information-only messages
W	Warning messages
E	Error messages
F	List of files in use
A	Start-of-action notification
R	Action data record, containing action-specific information
U	User-request messages
C	Initial user-interface parameters
M	Out-of-memory messages
p	Property table list, written in the form property = value
v	Verbose; includes debug messages
*	Turns on all options except v
+	Appends to the log file if it already exists

The default—and recommended—logging options are vpiwaeo. Verbose logging can slow the installation significantly and produce large log files. Verbose logging is generally useful only to diagnose installation problems during the testing phase or after a failed installation.

In Setup.ini, you specify the same logging options by setting the TYPE property, and you determine a name for the log files by setting the TEMPLATE property. The following example shows the syntax used in Setup.ini:

[Logging]
TYPE= <options>
PATH=<path>
TEMPLATE=<file name>.txt

You must include the .txt file extension when you specify a Setup log file name. Appending an asterisk (*) to the file name results in a unique log file for each installation performed by Setup.exe. The same log file name is used for each Windows Installer log file, with the task number from Setup.ini appended to the file name. For example:

[Logging]
TYPE= v+
PATH=%Temp%
TEMPLATE=VisioSetup(*).txt

These values create the following verbose log files during the installation process, append any new log files to the existing log files, and store them in the %Temp% folder on each users' computer. (%Temp% is the default location for log files.)

Log file	Description
VisioSetup(0001).txt	Setup.exe log file
VisioSetup(0001)_Task(0001).txt	System Files Update log file
VisioSetup(0001)_Task(0002).txt	Visio log file
VisioSetup(0001)_Task(0003).txt	Log file for first chained package

The Setup INI Customization Wizard allows you to specify logging options for the entire installation. (You cannot set unique logging options for chained packages.)

To modify logging options by using the Setup INI Customization Wizard 

1. Start the Setup INI Customization Wizard and enter information about your administrative installation point and Setup settings file.

2. In the Logging mode box, select Default or Verbose.

3. In the Log file name or template box, enter the name of the template file.

System Files Update options

Unless you are installing Visio on Microsoft Windows 2000 or Microsoft Windows Millennium Edition (Windows Me), Visio Setup automatically checks to see whether key system and shared files are up-to-date, based on the file names and minimum versions listed in the [SystemPack_DetectionFileList] section of Setup.ini.

If the computer passes this test, Setup proceeds directly to the Visio installation. If it fails this test, Setup calls Windows Installer to install the System Files Update and update the files—including installing Internet Explorer 5.01.

If you are installing Visio on Microsoft Windows NT 4.0 or Microsoft Windows 98, you can control this default Setup behavior by using the following command-line options:

• /nosp 

  Setup skips the detection process and does not install the System Files Update.

• /spforce 

  Setup installs the System Files Update even if the computer passes the detection check.

• /sponly 

  Setup installs the System Files Update but does not chain the Visio package.

You can also set the NOIE property to True on the command line, in the [SystemPackOptions] section of the Setup settings file (Setup.ini), or on the Modify Setup Properties page of the Custom Installation Wizard. Setting NOIE to True prevents Setup from upgrading the computer to Internet Explorer 5.01, except for required components such as Windows Web Browsing Components and HTML Help.

Note   Because Windows 2000 and Windows Me already have the required level of system files, the System Files Update detection and installation process does not run on these operating systems, nor can you use /spforce or /sponly to trigger the System Files Update or upgrade Internet Explorer.

Installation location

By default, Setup installs Visio in the Program Files\Microsoft Visio\Visio10 folder on each users' computer. You can change this location by specifying a different path for the INSTALLDIR property.

You can specify the location by setting the INSTALLDIR property on the Modify Setup Properties page of the wizard, on the Setup command line, or in the Setup settings file.

Note   Unlike previous versions, Visio 2002 SR-1 is always installed in a version-specific folder. If you choose to retain a previous version of Visio on the computer, you can specify the same custom location without overwriting any files.

Setup error messages and failure reporting

Visio Setup allows you to customize the error messages that users see when they run Setup with a full or reduced user interface. For example, you can add text to the error message box that refers users to an internal support group. Specify a string value for the SUPPORTERRORSTRING property on the command line, in Setup.ini, or in a transform.

The Visio feature Error Reporting (Dw.exe) also allows you to report Setup failures directly to Microsoft. By default, this feature is turned off when you create an administrative installation point. However, you can turn it on by setting the SETUPDW property to True. Note that, unlike Application Error Reporting for application failures after installation, you cannot redirect Setup failure reporting to an internal Web site.

Customizing Visio Features and Shortcuts

 

When you install Microsoft Visio 2002 SR-1from an administrative installation point, you can determine which features are installed on users' computers, including how and when features are installed. You can also customize the way that Setup creates shortcuts for Visio and add your own custom files to the Visio installation.

Selecting Visio features

When running Visio Setup interactively, users can choose which Visio features are installed by selecting options from the feature tree that Setup displays. Visio features can be installed in any of the following states:

• Copied to the local hard disk.

• Run from the network server.

• Installed on first use, which means that Setup does not install the feature until the first time it is used.

• Not installed, but accessible to users through Add/Remove Programs or the command line.

• Not installed, not displayed during Setup, and not accessible to users after Visio is installed.

By using the Office XP Custom Installation Wizard, you can make these choices for users ahead of time. When users run Setup interactively, the installation states that you specify in the transform (MST file) appear as the default selections. When you run Setup unattended, your choices determine how the features are installed.

Note   Visio doesn't support mixed local and network feature installation states.

Set the installation state for features

The Set Feature Installation States page of the Custom Installation Wizard displays the same feature tree that users see when they select the Customize option during Setup. The feature tree is a hierarchy where parent features contain child features. For example, the Solutions feature includes the child feature Block Diagrams.

When you click a feature in the feature tree, you can select one of the following installation states:

• Run from My Computer 

  Setup copies files and writes registry entries and shortcuts associated with the feature to the user's hard disk, and the feature runs locally.

• Run all from My Computer 

  Same as Run from My Computer, except that all child features belonging to the feature are also set to this state.

• Run from Network 

  Setup leaves components for the feature on the administrative installation point, and the feature is run from there.

• Run all from Network 

  Same as Run from Network, except that all child features belonging to the feature are also set to this state.

• Installed on First Use 

  Setup leaves components for the feature and all its child features on the administrative installation point until the user first attempts to use the feature, at which time the components are automatically copied to the local hard disk.

  Note that a few child features do not support Installed on First Use; you can set these features to be installed on the local computer.

• Not Available 

  The components for the feature, and all of the child features belonging to the feature, are not installed on the computer.

• Not Available, Hidden, and Locked 

  The components for the feature are not installed and the feature does not appear in the feature tree during Setup—nor can users install it by changing the state of the parent feature or by calling Windows Installer directly from the command line.

Not all installation states are available for every feature. For example, if a feature contains a component that cannot be run over the network, Run from Network is not included in the list of available installation states.

When you change the installation state of a parent feature, Windows Installer may automatically change the installation state of a child feature to match. If you set the Database feature to Run from My Computer, for example, but set the parent feature Solutions to Installed on First Use, Setup installs the entire Solutions feature to Installed on First Use.

Tip   If you run the Custom Installation Wizard (Custwiz.exe) with the /x command-line option, the wizard displays the feature tree fully expanded on the Set Feature Installation States page.

Hide or lock features during Setup

In addition to setting the installation state, you can right-click any feature on the Set Feature Installation States page and click Hide to hide the feature from the user. Setup does not display hidden features in the feature tree when users run Setup interactively; instead, the feature is installed behind the scenes according to the installation state that you have specified. When you hide a feature, all of the child features belonging to the feature are also hidden.

The best use of the Hide setting is to simplify the feature tree for users. For example, you might hide the Add-Ons branch of the feature tree so that users do not have to decide which add-ons they need. Only the add-ons that you select are installed.

Note   When you edit the transform in the Custom Installation Wizard, you can reverse the Hide setting by right-clicking the feature and clicking Unhide.

Even if you set a feature to Not Available and hide it in the feature tree, users can still change the setting and install the feature by installing the parent feature or by running Visio in maintenance mode. For example, if you set the Database feature to Not Available and hide it, users can still install it by setting the parent Solutions feature to Run All from My Computer.

To prevent users from installing hidden features, choose the Not Available, Hidden, and Locked installation state. In this case, the feature or application is not installed and is not available in maintenance mode. Users cannot install it by changing the state of the parent feature or by calling Windows Installer directly from the command line. There is no way to change the Not Available, Hidden, and Locked installation state after Visio is installed.

Disable installation states that rely on a network connection

Installing features on demand or running features over the network is not always efficient. Both of these installation states require a fast connection and reliable access to the administrative installation point on the network—which laptop users in the field might not always have.

The Custom Installation Wizard for Office XP includes two new options on the Set Feature Installation States page that disable these installation states and help ensure that users do not reset features to these states during Setup or in maintenance mode:

• Disable Run from Network 

  When you select a feature in the feature tree and then select this check box, users are prevented from setting the feature to run from the network—the installation state does not appear in the list of options during initial Setup or in maintenance mode.

• Disable Installed on First Use 

  When you select a feature in the feature tree and then select this check box, users are prevented from setting the feature to be installed on first use—the installation state does not appear in the list of options during initial Setup or in maintenance mode.

Child features do not inherit these settings from parent features. You must select each feature in the tree and set Disable Run from Network or Disable Installed on First Use for only that feature.

Note   The Disable Run from Network and Disable Installed on First Use properties remain in effect for as long as Visio is installed on the user's computer.

Adding files to the installation

In addition to selecting which Visio files are installed, Setup allows you to add your own files to the Visio installation. You can deploy corporate templates, images, custom applications, or other files along with Visio. On the Add/Remove Files to the Installation page of the Office XP Custom Installation Wizard, click Add to add a new file to the installation.

After you select one or more files to add, enter the destination path for the file or files in the File Destination Path dialog box. You can enter an absolute path on the user's computer, or you can select a path from the list. If you select a path, you can add a subfolder to it by appending a backslash (\) followed by the subfolder name. When you click OK, the wizard adds the file to the transform. Setup installs the file on the user's computer, in the folder you specified, when the user installs Visio.

Note   Files that you add to the installation on this page are not removed if the user subsequently modifies the file or removes, repairs, or reinstalls Visio.

After you add the file, you can add a shortcut for the file on the Add, Modify, or Remove Shortcuts page of the wizard. On that page, click Add—the file you added appears in the Target box. Because the file is copied into the transform, you must update the transform if the file changes later on.

To update the installation with modified files 

1. On the Create or Open the MST File page, enter the name of the Windows Installer transform (MST file).

2. On the Select the MST File to Save page, enter the name of the MST file again.

3. Click Next until you reach the Add/Remove Files to the Installation page.

4. Select the file that has changed, and click Remove.

5. Click Add, and then enter the information for your modified file.

The Custom Installation Wizard also allows you to specify files to remove from users' computers when Visio is installed. For example, you can have Setup delete custom templates designed for Visio 5.0 or Visio 2000 when you upgrade to Visio 2002 SR-1. Click the Remove Files tab to list files to remove.

For more information about adding or removing files by using a transform, see the help file included with Custom Installation Wizard, available from the Office XP Resource Kit Toolbox.

Customizing Visio shortcuts

By using the Office XP Custom Installation Wizard, you can customize the shortcuts that Setup creates for Microsoft Visio. You can control what shortcuts are installed, and you can also specify the folder in which the shortcut is stored and what command-line options to use with the shortcut.

On the Add, Modify, or Remove Shortcuts page, the Custom Installation Wizard displays shortcuts for all the features that you selected on the Set Feature Installation States page.

Modify an existing shortcut

On the Add, Modify, or Remove Shortcuts page, you modify any existing shortcut by selecting the shortcut and clicking Modify. In the Add/Modify Shortcut Entry dialog box, you can make the following modifications:

• Target

  Change the application associated with the shortcut. The names in the list correspond to features that you selected on the Set Feature Installation States page of the wizard, plus any custom files that you added to the installation on the Add Files to the Installation page. You can add command-line options by appending a space and a list of options to the target name.

• Location

  Change the folder in which the shortcut is created by selecting a location from the list. You can specify a subfolder by appending a backslash (\) followed by the subfolder name.

  For example, to install the Visio shortcut in the Microsoft Visio subfolder in the Programs folder, click the Start menu, select <StartMenu\Programs>, and then append the subfolder name as follows:

<startmenu\programs>\Microsoft Visio

• Name

  Change the name of the shortcut by entering any string.

• Start in

  Change the starting folder for the application by entering a path. The path must be a valid path on the user's computer. If it is not a valid path, the user sees an error message when trying to use the shortcut.

• Shortcut key

  Associate a shortcut key with this shortcut by entering the shortcut key string in this box. Click the Help button in the wizard for a description of how to specify a shortcut key.

• Run

  Select how you want the application to run when the user double-clicks this shortcut. For example, if you want the application to run in a maximized window by default, select Maximized.

• Change Icon

  Select a new icon for the shortcut.

Add or remove shortcuts

You can click Add to add a new shortcut for any file being installed by Setup. This step allows you to create duplicate shortcuts for the most frequently used Visio features on the user's computer. It also allows you to create shortcuts for custom files or applications that you add to the installation.

To remove a shortcut from the list, select the shortcut, and then click Remove.

Create Windows Installer shortcuts

Windows Installer shortcuts support automatic repair of Visio features and allow you to advertise Visio features. Advertised features are installed the first time a user clicks the shortcut or opens a file associated with the application. If the computer does not support Windows Installer shortcuts, any feature set to Installed on First Use is installed on the local hard disk, and Setup creates a standard Windows shortcut.

By default, Setup creates Windows Installer shortcuts on any computer that supports them. The following operating systems support Windows Installer shortcuts:

• Microsoft Windows XP Professional

• Microsoft Windows 2000 or later

• Microsoft Windows Millennium Edition (Windows Me)

• Microsoft Windows 98

• Microsoft Windows NT 4.0 Service Pack 6a, if you also install either Microsoft Internet Explorer 4.01 Service Pack 1 or Internet Explorer 5.01 with the Active Desktop option.

In some circumstances, you might not want Setup to create Windows Installer shortcuts. For example, if you are deploying to roaming users who sometimes log on to computers that do not support Windows Installer shortcuts, you can circumvent the default behavior by clearing the Create Windows Installer shortcuts if supported check box on the Add, Modify, or Remove Shortcuts page.

For more information about updating Windows NT 4.0 to support Windows Installer shortcuts, see Using Windows Installer Shortcuts with Visio in Chapter 6 of the Microsoft Visio 2002 Resource Kit.

Including Additional Packages in the Visio Installation

 

The Microsoft Visio Setup program supports the chaining of additional packages (MSI files) or programs (EXE files) to the core Visio installation. Chaining allows you to deploy Visio and other applications in one seamless process.

A typical installation of Visio follows this pattern: The System Files Update is always installed first, followed by the core Visio package. Then Setup calls Windows Installer to install any number of chained packages in the order that you specify in the Setup settings file (Setup.ini). You customize chained packages by setting properties in Setup.ini or by creating a transform.

Specifying chained installations in Setup.ini

Setup reads the Setup.ini file at the start of the installation process and writes a set of tasks to the Windows registry to install each package listed in the [ChainedInstall_1] through [ChainedInstall_n] sections. By default, Setup passes to Windows Installer the command-line options and properties defined for Visio; however, you can set unique properties for a chained package in Setup.ini.

For example, you can include Visio in your Office XP installation by adding the appropriate Visio.msi file to Setup.ini:

[ChainedInstall_1]
PATH=\\server\share\admin_install_point\1033\Visio.msi
DISPLAY=None
MST=Visio_eng.mst
CMDLINE=SOURCELIST=\\server2\share admin_install_point\1033

These lines add Visio to an Office XP installation. Visio is installed unattended (regardless of the display setting specified for the Office XP installation), the customizations in the transform Visio_eng.mst are applied, and an alternate source is identified for when the primary administrative installation point is unavailable.

Customize chained packages

In most sections of Setup.ini, including the [Options] and [SystemPackOptions] sections, you use the syntax PROPERTY=value to specify custom property values. In the [ChainedInstall_n] sections, you can set the DISPLAY and MST values with this syntax, along with several additional settings that customize the installation process. However, you must use the CMDLINE property to add other options to the command line that Setup passes to Windows Installer for the package.

You can set the following properties for chained packages in Setup.ini:

• TASKNAME=< task_name > 

  Assigns a friendly name to the installation. Setup uses this name in the Setup log file.

• TASKTYPE=< task_type > 

  Identifies whether the chained installation is an MSI file or EXE file.

  Note   If you edit Setup.ini directly, you must specify TaskType=exe to chain an executable file; the value exe is case-sensitive and must be all lowercase. The Setup INI Customization Wizard enters the correct value automatically when you add an EXE file to the Visio installation.

• PATH=< path_to_msi_or_exe > 

  Specifies the relative or full path to the MSI file or EXE file.

• DISPLAY=< user interface display level > 

  Specifies a display setting for the chained installation. Use Basic to display only progress indicators; use None for an unattended installation.

• MST=< transform.mst > 

  Specifies the path and file name of a transform (MST file) to apply to the chained package.

• CMDLINE=< command_line_options > 

  Specifies other property-value pairs or command-line options that Setup passes to Windows Installer during the call to install the chained package.

• IGNORERETURNVALUE=[0|1] 

  To continue installing successive chained packages even if this installation fails, set this property to 1.

• REBOOT=[0|1] 

  To restart the computer after the installation completes, set this property to 1.

Use the Setup INI Customization Wizard to add installations

Although you can modify Setup.ini manually in Notepad, the Setup INI Customization Wizard (Iniwiz.exe) provides a convenient interface for adding and customizing chained packages.

To add chained packages to Setup.ini 

1. Install the package that you want to chain on the Visio administrative installation point or another network share.

2. Start the Setup INI Customization Wizard, and enter the path to your Visio administrative installation point.

   The wizard searches the specified network share for a Setup.ini file and all Windows Installer packages on the network share.

3. On the Select MSI and EXE files to include in your INI file page, select the check boxes next to the packages that you want to include in your custom INI file, or click Browse to add packages from another location, and then click Next.

4. Use the arrows to determine the order in which you want Setup.exe to install the chained packages.

5. On the Specify options for each package in your INI file page, select the chained package that you want to customize, and specify the options you want for that package.

   For each package you can specify an MST file and unique display settings, as well as additional property values.

6. To add additional property-value pairs to your custom INI file, select a package, click Advanced Properties, enter the properties and values you want, and then click Next.

The wizard enters all your customizations in the correct sections and with the correct syntax in the Setup.ini file. For example, if you set the SOURCELIST property to \\server\share\admin_install_point2, the wizard correctly enters the following line in the [ChainedInstall_n] section of Setup.ini:

CMDLINE=SOURCELIST=\\server\share\admin_install_point2

Note   The Office XP Resource Kit includes the Setup INI Customization Wizard, which is installed by default when you run the Office XP Resource Kit Setup program. For more information, see "Setup INI Customization Wizard" in the Office XP Resource Kit Toolbox.

Requirements and limitations

The Setup program for Visio is designed to support chaining of other Windows Installer packages and simple executable programs (EXE files). However, chaining is not the best method to use in all circumstances, as described in the following sections.

Adding programs through the Custom Installation Wizard

The Custom Installation Wizard allows you to add installations and run programs during the Visio installation. For example, if you have a custom Visio solution that has a setup program, you could chain that setup onto Visio. However, you cannot use the Add Installations and Run Programs page of the Custom Installation Wizard to chain additional Windows Installer packages. If Windows Installer tries to start installation of a second package before it has completed installation of the first package, the entire installation process stops.

Note The Office XP Resource Kit includes the Customization Installation Wizard, which is installed by default when you run the Office XP Resource Kit Setup program. For more information, see Custom Installation Wizard in the Office XP Resource Kit Toolbox.

Using Windows 2000 software installation services

Microsoft Windows 2000 software installation, a feature of Microsoft IntelliMirror, works directly with the MSI file and bypasses Visio Setup and the Setup.ini file when assigning or publishing packages. For this reason, you cannot use Setup.exe to chain Visio installations when you assign or publish packages. Instead, Windows 2000 deploys Visio 2002 SR-1 and other Visio-related packages separately and in random order.

Restarting the computer after a chained installation

Visio Setup does not support forced reboots for chained packages. In other words, you cannot chain a package that must restart the computer to complete its installation because restarting interrupts the Visio Setup.exe thread and stops the installation process. To avoid this problem, Visio Setup sets the REBOOT property to REALLYSUPPRESS by default for all but the last chained package.

You can, however, direct Setup.exe to restart the computer and then resume to complete a chained installation by setting the REBOOT property. For example, you can set the REBOOT property to 1 in the [ChainedInstall_n] section of Setup.ini. (In the Setup INI Customization Wizard, select the Restart computer after this package. Setup will resume after restart, and continue installation check box.) This setting adds a task to the registry that directs Setup to restart the computer and then resume the Visio installation.

Elevating installation of a chained package

If you chain a package that requires elevated privileges to install, you must take the same steps to elevate the installation that you do for Visio. Setup.exe does not automatically install a chained package with administrator privileges when the Visio installation is elevated. However, several of the methods that you use to elevate the Visio installation also elevate any chained installations:

• If you use the /jm option to advertise Visio, every installation listed in Setup.ini is also advertised and therefore elevated.

• If you set the Windows system policy Always install with elevated privileges, any user can install any Windows Installer package with elevated privileges.

• If you log on as an administrator when you begin the Visio installation and do not log off or restart before it completes, chained installations run with elevated privileges.

For more information about elevating the Visio installation for users who are not administrators, see Installations That Require Elevated Privileges in Chapter 3 of the Microsoft Visio 2002 Resource Kit.

Customizing Removal Behavior

 

When you upgrade to Microsoft Visio 2002, you can choose to remove or keep previously installed versions of Visio.

Removing previous versions during Setup

When users install Visio, Setup detects files, settings, and shortcuts from previously installed versions of Visio and removes them. When you run Setup in unattended mode (/q), default Setup behavior removes all previous versions of Visio. If you run Setup with a full user interface, users can choose to remove or keep previous versions.

Setup can detect and remove the Visio versions 4.5 and later.

Note   Setup does not remove documents or other user files from the user's hard disk.

Customizing the removal process

You can specify how the Setup program for Visio cleans up users' computers:

• In the Custom Installation Wizard, you must add a property on the Modify Setup Properties page called OPCKEEPAPPS and set its value to 1. Doing so will prevent Visio from removing previous versions of Visio. Additionally, you can set OPCREMOVEVISIO on the Modify Setup Properties page to force the removal of previous versions of Visio regardless of what the default setup behavior is set to be. Note   The Office XP Resource Kit includes the Custom Installation Wizard, which is installed by default when you run the Office XP Resource Kit Setup program. For more information, see Custom Installation Wizard in the Office XP Resource Kit Toolbox.

Customize removal behavior in a transform

You can use the Custom Installation Wizard to customize removal behavior during Visio Setup. On the Modify Setup Properties page of the wizard, specify that Visio be removed from users' computers by adding OPREMOVEVISIO. In this case, Setup does not display the Remove Previous Versions page to users during the installation—the instructions in the transform are carried out regardless of the display setting.

Distributing Visio to Users' Computers

 

After you create an administrative installation point and customize your Microsoft Visio 2002 SR-1configuration, users can install Visio from the network. You can use any of the following methods to distribute Visio to users:

• Have users run Setup from the administrative installation point using the command-line options, Setup settings file, or transform that you specify.

• Assign or publish Visio to users or computers (Microsoft Windows 2000).

• Advertise Visio on users' computers.

• Create a hard-disk image and replicate it on users' computers.

• Use a systems management tool, such as Microsoft Systems Management Server, to install Visio.

Running Setup from an administrative installation point

When users double-click setup.exe on the administrative installation point, Setup runs with no command-line options. To apply your customizations, users must click Run on the Windows Start menu and enter the path to Setup.exe, along with the appropriate command-line options. For example, the command line must include the /settings option to specify a custom Setup settings file or the TRANSFORMS property to specify a transform (MST file).

To ensure that Visio is installed with the correct customizations, you can create a Windows shortcut and add options to the command-line box. Users click the shortcut to run the Setup command line that you have defined. You can distribute the shortcut to users in an e-mail message.

Unless you choose to install Visio unattended, the Setup user interface guides users through the following steps to install Visio on their computers:

1. Update system files.

2. Enter user information.

3. Specify to keep previous versions of Visio.

4. Select installation mode and location.

5. Select installation options for Visio features.

Most of the customizations that you specify on the command line, in the Setup settings file, or in a transform appear as defaults in the Setup interface; however, users can modify your choices when they run Setup interactively. To prevent users from changing the configuration during the installation, run Setup in unattended mode. For information about installing Visio unattended, see "Customizing How Setup Runs" earlier in this chapter.

Update system files

On Microsoft Windows 98 and Microsoft Windows NT 4.0, Setup first checks to see whether the computer has the required versions of key system and shared files. If the computer fails this test, Setup starts the System Files Update installation and displays a list of components that need to be updated.

The next page of Setup gives users the option of upgrading to Microsoft Internet Explorer 5. If users choose not to upgrade, Setup calls Internet Explorer Setup to install a subset of Internet Explorer– and Windows-related components (such as HTML Help) that are required by Visio.

You can install the System Files Update unattended, even if you run Setup with a full user interface. In this case, system files and Internet Explorer are updated based on the settings that you specify on the command line, in the Setup settings file, or in a transform applied to the System Files Update package. After updating system files and installing Internet Explorer, Setup restarts the computer before starting the Visio installation.

Note   If a computer already has Internet Explorer 5.0 installed, Setup upgrades to version 5.01 behind the scenes, without offering the user the option of upgrading. If the NOIE property is set to True, Setup installs only the subset of Internet Explorer– and Windows-related components required by Visio.

Enter user information

User information appears on users' computers in the About box (Help menu) in Visio. When a user installs Visio from an administrative installation point, Setup uses the organization name you specify without prompting the user.

Note   Because you must enter the product key from the Visio CD when you create an administrative installation point, users are not prompted for a product key during the installation.

Accept end-user license agreement

When users install Visio from the CD, Setup displays an end-user license agreement page. When users install Visio from the administrative installation point, however, the license agreement that you accepted when you created the administrative installation point applies, and users do not see this page of Setup.

Select installation mode and location

After they enter the required user information, on the next page in Setup users select the type of installation to perform and the location to install Visio.

Installation mode

Users can select one of the following installation options:

• Install Now 

  Automatically installs the most frequently used Visio features in the default installation location, and skips the remaining pages of Setup.

• Custom 

  Allows the user to configure all aspects of the Visio installation on the remaining pages of Setup.

  Note   Visio Setup does not include the option to run from the Visio CD.

By using the Custom Installation Wizard, you can create a Windows Installer transform (MST file) that specifies the default features installed by Setup when the user clicks Install Now. You can also change the button labels and descriptive text on this page by setting the properties described in the following table.

Property	Default value
TYPICALINSTALLTEXT	&Install Now
TYPICALUPGRADETEXT	&Upgrade Now
TYPICALINSTALLDESCRIPTION	Installs Visio with the default settings, including the most commonly used components.
TYPICALUPGRADEDESCRIPTION	Upgrades your Visio installation. Setup will remove your previous versions and install based on your current configuration.
RUNFROMSOURCEINSTALLDESCRIPTION	Installs only the files that must copied to your computer. Access to the installation source will be required to run Visio.
CUSTOMINSTALLDESCRIPTION	Customize your Visio installation, selecting which Visio features to install on your computer.
COMPLETEINSTALLDESCRIPTION	Installs all of Visio on your computer, including all optional components and tools.

For example, if few users in your organization work with databases, you might omit the Database solution from a typical installation by setting its installation state to Not Available in the transform. To alert the minority of users who might need that solution, however, you can change the description of the Custom option by setting the following property:

CUSTOMINSTALLDESCRIPTION="To install the Database solution, choose 
this option and change the installation state."

Installation location

On this page of Setup, users can also enter the path to the installation location they want. The default location is Program Files\Microsoft Visio\Visio10.

You can specify a default value for the installation location on the Specify Default Path and Organization page of the Office XP Custom Installation Wizard. You can also specify the location by setting the INSTALLDIR property on the command line, in the Setup settings file, or on the Modify Setup Properties page of the Custom Installation Wizard.

Select installation options for Visio features

Setup displays the Visio feature tree and allows users to set an installation state for each feature. The installation states you specify in a transform are set by default, but users can modify them. Features that you have hidden or locked or installation states that you have disabled are not displayed.

The following feature installation states are normally available to users during Setup:

• Run from My Computer 

  Setup copies files and writes registry entries and shortcuts associated with the feature to the user's hard disk, and the feature runs locally.

• Run all from My Computer 

  Same as Run from My Computer, except that all child features belonging to the feature are also set to this state.

• Run from Network 

  Setup leaves components for the feature on the administrative installation point, and the feature is run from there.

• Run all from Network 

  Same as Run from Network, except that all child features belonging to the feature are also set to this state.

• Installed on First Use 

  Setup leaves components for the feature and all its child features on the administrative installation point until the user attempts to use the feature for the first time, at which time the components are automatically copied to the local hard disk.

• Not Available 

  The components for the feature, and all of the child features belonging to this feature, are not installed on the computer.

Note When installing Visio from an Administrative installation location, you should not mix Run from Network and Install Local feature states. Set all features either to Install Local (or Install on Demand) or Run from Network.

For more information about customizing what users see in the feature tree, see "Customizing Visio Features and Shortcuts" earlier in this chapter. You can also find detailed information about setting installation states in a transform by clicking Help on the Set Feature Installation States page of the Custom Installation Wizard.

Select to keep previous versions of Visio

If the user is upgrading from a previous version of Visio, Setup displays a list of all the Visio versions currently installed—versions that Setup removes when it installs Visio 2002 SR-1. Users can choose to keep all or remove all previous versions on the computer.

Because Visio 2002 SR-1 is always installed in a version-specific folder, users can choose to keep previous versions without overwriting any files. However, Setup does redefine system settings, such as file types and shortcuts, to point to the Visio 2002 SR-1 application.

Assigning or publishing Visio

If all the computers in your organization run under Windows 2000, you can use a set of Windows 2000–based technologies known collectively as Microsoft IntelliMirror to install and manage Visio by policy. IntelliMirror includes a software installation and maintenance feature that allows an administrator to centrally manage software installation, repairs, updates, and removal.

Note   Before you can use Windows 2000 software installation, you must set up an Active Directory and Group Policy structure. You manage Visio 2002 SR-1 applications within a Group Policy object (GPO), which is associated with a particular Active Directory container: a site, domain, or organizational unit.

There are three ways to install and manage Visio applications by using Group Policy and Windows 2000 software installation:

• Assign Visio to computers

  Visio is installed on the computer the next time the computer starts. Users can repair Visio features on the computer, but only an administrator can remove the application.

• Assign Visio to users

  Visio is available to all users in the designated group the next time they log on. Visio is installed the first time a user clicks the associated shortcut on the Start menu or opens a file associated with Visio.

• Publish Visio to users

  Visio is available to all users in the designated group the next time they log on. Users install Visio through Add/Remove Programs in Control Panel or by opening a Visio drawing. (Under Windows 2000, you cannot publish a feature to a computer.)

With any of these methods, Visio is installed from your administrative installation point; however, Windows 2000 works directly with the MSI files and bypasses Setup.exe and the Setup settings file. To customize the installation you must apply a transform (MST file) when you assign or publish the Visio package (MSI file). Note that you can apply only one transform to a given installation of the Visio package.

Note   Transforms are applied when Visio is assigned or published. You cannot reapply a transform after Visio is installed. If you need to modify a managed Visio installation, you must remove and then reinstall Visio with a new transform.

For more information about using software installation to assign or publish Visio, see Using Windows 2000 Software Installation in Chapter 5 of the Microsoft Visio 2002 Resource Kit.

Advertising Visio

Under Microsoft Windows NT 4.0 and Microsoft Windows 2000, you can advertise Visio by logging on as an administrator and then running Setup with the /jm option. If you also include a Windows Installer transform (MST file) to customize the installation, you use the /t command-line option to specify the MST file. For example:

setup.exe /jm visio.msi /t visio.mst

Note   When you use the /t command-line option to specify a transform, you must insert a space between the option and the transform name to ensure that the transform is correctly applied.

In many organizations, advertising is a quick and efficient means of making Visio available to users. Advertising is similar to assigning Visio under Windows 2000, in that all Visio features and features are installed on demand. However, you can advertise only to computers, and advertising does not provide the same management capabilities as Windows 2000 software installation.

When you advertise Visio in this way, a Windows Installer shortcut for Visio appear on the Start menu, and a minimal set of core Visio files and components is installed on the computer. When a user clicks the shortcut or opens a file associated with a Visio feature, Windows Installer installs the feature or the application from the administrative installation point. After Visio is advertised, users can also run Setup directly from an administrative installation point to install Visio.

Windows NT 4.0 does not support Windows Installer shortcuts without the Windows Desktop Update, which is an updated version of the Windows shell. The Windows Desktop Update is included with Microsoft Internet Explorer 4.01 Service Pack 1 or later, but it is not installed by default. Without the updated shell and Windows Installer shortcuts, users must run Visio Setup from the administrative installation point for the core Visio files and components to be installed on the computer.

The System Files Update cannot be advertised. Advertising Visio on Windows NT 4.0 fully installs the System Files Update on the local computer when the System Files Update is required and then restarts the computer before advertising other packages.

For more information about installing Visio and updating the Windows shell on Windows NT 4.0, see Using Windows Installer Shortcuts with Visio in Chapter 6 of the Microsoft Visio 2002 Resource Kit.

Installing Visio on Windows NT 4.0 or Windows 2000 requires elevated privileges. For more information, see Installations That Require Elevated Privileges in Chapter 3 of the Microsoft Visio 2002 Resource Kit.

Distributing a custom CD

If you have users who cannot install or run Microsoft Visio over a network, you can distribute a customized version of Visio to them by creating copies of the Visio CD. This option requires that you have the capability to create and distribute CDs.

For example, traveling users who have limited access to the network might install Visio from a CD. Because less frequently used features in Visio are set to Installed on First Use by default, these users might find that they need an additional feature when they are out of the office. You can ensure that the source is always available by providing customized copies of the Visio CD.

Note   You must obtain the proper user licenses before copying, modifying, or distributing a customized version of the Visio CD. For more information about volume licensing programs, contact your software reseller or see the Licensing page of the Microsoft Licensing Web site.

Copy the Visio CD

Customizing a Visio CD image is similar to customizing an administrative installation point. For example, you can use the Custom Installation Wizard and Setup INI Customization Wizard as long as you point the wizards to the MSI file on the disk.

To create a customized copy of the Visio CD

1. Insert the Visio CD into your CD-ROM drive.

2. In Windows Explorer, select all the folders on the CD.

   Be sure to display all hidden files so that you see the entire contents of the Visio CD.

3. Copy the CD contents to a network share; the complete CD image for Microsoft Visio 2002 SR-1 Professional requires approximately 460 MB of space.

   If all your users are running Windows 2000 or Windows Millennium Edition (Windows Me), you can also omit the OSP folder. The folders and core Visio MSI file require approximately 230 MB of free space.

4. Customize the CD image by creating one or more transforms and modifying Setup.ini.

   For example, to avoid making users enter the correct product key from the Visio CD case, set the PIDKEY property in the transform, and specify the transform in the [MST] section of Setup.ini. You cannot accept the end-user license agreement, but if you specify an unattended display setting, users do not see that page during Setup.

5. Copy the image on your hard disk onto a CD, and distribute copies to users.

The CDs that you create can be used in the same way as the original Visio CD, except that Setup runs with your modifications.

Tip   If the original Visio source is unavailable and you must use a different type of source, you can reinstall Visio by running Setup with the /fv option. This option allows Setup to use a new source, but you cannot return to your original source without repeating the reinstallation process.

For more information about customizing the Setup process or your Visio configuration, see "Customizing the Visio Installation" earlier in this chapter.

Creating a hard-disk image

Some organizations deploy a complete user system at one time, including Microsoft Windows software, device drivers, Visio features, and custom settings. In this scenario, you install the entire system onto a test computer, and then you create an image of the hard disk to copy to users' computers.

Installing Visio with a complete user system is almost as fast as installing Visio by itself. It is a particularly efficient way to configure new computers or to restore a computer to its original state. When you distribute the hard-disk image to users, everything on the computer is replaced by your custom configuration, so users must back up any documents or other files they want to keep.

Customize Visio on the administrative installation point

To create the hard-disk image, you begin by running Visio Setup with the /a option to create an administrative installation point. You can use the Custom Installation Wizard to create a transform and the Setup INI Customization Wizard to modify Setup.ini, just as you do when you customize Visio in any other network installation scenario. In addition, you must take several steps to exclude user-specific information from the hard-disk image.

To customize Visio for a hard-disk image 

1. To create a Visio administrative installation point, run Setup with the /a option to start the Custom Installation Wizard.

2. On the Set Feature Installation States page, set installation states for each feature.

3. On the Modify Setup Properties page, set the following properties:

   NOUSERNAME=True 

   ENTERPRISE_IMAGE=True 

4. Make any additional customizations and save the transform.

To customize Setup.ini using the Custom Installation Wizard 

1. Start the Setup INI Customization Wizard, browse to the root of the administrative installation folder where the VISIO.MSI is located, and then click Next.

2. Click Next again to accept the Seutp.ini file in the files\setup folder,

3. Click Next repeatedly until you reach the page titled Specify options for each package in your INI file.

4. Under Installation sequence, select Microsoft Visio 2002 in the Description column, and then select Microsoft Visio 2002.

5. Click the Transform (MST file) to apply during installation check box, and then browse to the transform you created. Note   Because of the path name dependencies of the Setup INI Customization Wizard, it is advisable to place the transform files in the root folder of the administrative installation point. If you must specify more than one transform file, use a semicolon to separate the full file names.

6. Because Visio requires support for long file names, make sure that Microsoft Visio 2002 is selected in the Description column, and then click Advanced Properties.

7. In the Edit Advanced Properties dialog box, if SHORTFILENAMES appears in the Installer Properties list, select it, click Remove, then click OK,

8. Click Finish to save the updated Setup.ini file.

Specifying Setup properties

You must set the following Setup properties to make sure that your Visio configuration is installed properly on users' computers:

• NOUSERNAME=True 

  Prevents Setup from defining a user name during installation. This setting allows users to enter their own user names the first time they run a Visio feature.

• ENTERPRISE_IMAGE=True 

  Prevents Setup from creating a digital license identification based on the hardware components of the test computer. This setting allows Setup to generate unique digital license identification on each client computer the first time Visio is started, instead of when Visio is initially installed.

Install Visio on a clean test computer

The next step is to install Visio from the administrative installation point onto a clean client computer—one that already has the Windows configuration you want and one that has never had Visio or any previous version of Visio installed. This installation becomes the model for your hard-disk image.

After you have installed and configured all the system software on the test computer, run Visio Setup to install Visio from the administrative installation point. If you have not already done so in the transform or Setup.ini file, set the NOUSERNAME and ENTERPRISE_IMAGE properties on the Setup command line.

To install Visio on the test computer 

1. On the Start menu, click Run.

2. Enter the name and path to Visio Setup.

   You can copy and paste the command line generated by the Setup INI Customization Wizard.

3. If you have not already done so, set the NOUSERNAME and ENTERPRISE_IMAGE properties on the command line; for example:

\server\share\admin_install_point\setup.exe NOUSERNAME=True ENTERPRISE_IMAGE=True

4. Unless you want all users who receive the hard-disk image to use your administrative installation point as a source for installing, repairing, or removing Visio features, reset the source list to point to the Visio CD or another network share.

Caution   To prevent user-specific information from appearing on the hard-disk image, do not start any Visio features on the test computer. After you install Visio on the test computer, you can make additional modifications to the configuration. However, starting a Visio feature writes user-specific information to the Windows registry, which is then duplicated to all users.

Distribute the hard-disk image

Before you distribute your hard-disk image, install it on a client computer and make sure that Visio features are installed and configured correctly. Then you can use any one of a number of tools to create copies of the hard-disk image.

The Windows 2000 operating system includes several new or improved technologies for automating installation of Windows 2000 Professional on client computers through hard-disk imaging. Two of these technologies allow you to include Visio 2002 SR-1 in the hard-disk image that installs Windows 2000 Professional:

• SysPrep 1.1

  Prepares the hard disk on the test computer for duplicating to other computers and then runs a third-party, disk-imaging process. SysPrep can copy the hard-disk image to client computers that have different hardware application layers (HALs) and different Plug and Play device drivers. SysPrep is fast—the hard-disk image can be packaged and compressed; only the files required for the specific configuration are included.

• Remote Installation Services (RIS)

  Installs both Windows 2000 and Visio 2002 SR-1 remotely on client computers. You can set up new computers and new users without on-site technical support and recover more quickly from computer failures. RIS requires adequate network capacity and the Active Directory service.

Use Remote Installation Services (Windows 2000)

Remote OS Installation, which is based on RIS, is an optional service in Windows 2000 Server. It provides a mechanism for computers to connect to a network server during the initial startup process, while the server controls a local installation of Windows 2000 Professional.

If all the computers in your organization are running under Windows 2000, you can use remote installation services to copy a preconfigured hard-disk image—with standardized versions of both Windows 2000 Professional and Visio 2002 SR-1—to client computers. RIS also requires that you have Active Directory and a Group Policy structure set up.

This method can significantly reduce deployment time. A remote installation of Windows and Visio together takes only slightly longer than a remote installation of Windows by itself. When clients download the disk image, Visio is fully installed on the local computer—and not merely advertised.

Note If you want users to receive a managed Visio installation, you must use the Software Installation snap-in to assign Visio to the test computer before creating your disk image.

When used together, Remote OS Installation and other Windows 2000 management services offer the following benefits:

• More efficient and cost-effective setup of new computers.

• Dynamic configuration and repair of both Windows 2000 and Visio.

• Easier recovery from computer failures.

If the computer fails, you can quickly restore Windows 2000 Professional (by using Remote OS) and restore the user's applications, data, and settings (by using Microsoft IntelliMirror features).

To distribute Visio by using RIS 

1. Install and configure Windows 2000 Professional for your organization on a test computer.

2. Install and customize Visio on an administrative installation point.

3. Install your customized version of Visio from the administrative installation point to the test computer.

4. Run the Remote Installation Preparation Wizard (RIPrep.exe) from the RIS server that will receive the hard-disk image.

Note   Remote OS Installation works only in a homogenous Windows 2000 environment—Windows 2000 Server and Windows 2000 Professional clients. You cannot use it to install to clients running under Windows NT 4.0 or Windows 98.

For a detailed outline of the steps necessary to install, configure, and use Remote Installation Services (RIS), see Step-by-Step Guide to Remote OS Installation on the Microsoft Windows 2000 Web site.

To find out how to create an installation image by using the Remote Installation Preparation Wizard, search for Creating an installation image in the Windows 2000 Server Help page on the Microsoft Windows 2000 Web site.

Using Microsoft Systems Management Server

Microsoft Systems Management Server (SMS) 2.0 provides a robust distribution model for deploying Visio to client computers. If you are installing Visio under any of the following circumstances, consider using SMS:

• You want more control over the timing of your Visio installation.

  For example, you need to complete the installation during off hours, or you need to coordinate upgrades across multiple sites.

• You need advanced reporting and troubleshooting tools.

• You are deploying to users over slow network or dial-up connections.

• You are deploying to a mixture of Windows clients, including Windows 2000, Windows Me, Windows NT 4.0, and Windows 98.

Systems Management Server also gives you the flexibility to deploy non-Windows Installer packages and to target collections of users or computers based on advanced resource attributes (such as software or hardware inventory properties).

For more information about using Systems Management Server, see the Microsoft Systems Management Server Web site.

For a comparison of software deployment features in Windows 2000 IntelliMirror, Remote OS Installation, and Systems Management Server 2.0, see the white paper Software Deployment Using Windows 2000 and Systems Management Server 2.0 on the Windows 2000 Web site.

Deploying Service Releases and Updates

 

Microsoft Visio 2002 SR-1service releases are interim upgrades that are designed to improve the performance and reliability of Visio. Although service releases are often developed in response to emerging issues, such as virus attacks, they may also contain bug fixes or updated features.

In considering whether to deploy a given service release, first determine how the changes will benefit your organization. If a particular upgrade does not apply to how you use Visio, you may elect not to deploy that release. Deploying a service release is not always required to maintain the functionality of your original installation, although many Microsoft quick-fix engineering (QFE) updates do require that the latest service release be installed.

Information about the changes and features offered by a specific service release is posted on the Downloads on Microsoft Office Online. Follow the instructions on the site to display the downloads available for your version of Visio. Each download page contains information about the release.

If a particular service release has language dependencies, separate versions of the update will be made available for each language in which Visio 2002 SR-1 is released.

Note   If you originally installed your product from a network location, check with your system administrator before you apply an update from the Web. Depending on how your product was installed, if you apply a patch yourself, you may have problems trying to access the Visio image on the network location or when you try to apply future updates.

Deploying administrative updates

When you deploy an administrative update, you must perform a re-cache and reinstallation of the updated version of Microsoft Visio. This process overwrites any old files with the newer versions.

Whenever possible, updates are designed to make sure that your features retain their existing installation states and that support files, such as transforms, continue to work as they did before installation. Usually, you can use existing transforms (MST files) on an updated administrative image to reproduce the same customizations for new client installations.

By applying a service release to either an administrative installation point or a stand-alone version of Visio, you create an upgraded version of the original product. The original product and the upgraded version cannot coexist as separate installations on the same computer.

Planning for a service release

For most organizations, the best way to deploy a Microsoft Visio service release is to create an updated image of the product on an administrative installation point. Local users can then connect to this network share and update the version of Visio installed on their computers.

If you are staging your upgrades over a period of time, you may need to maintain two administrative installation points during the process:

• The original network share to serve as a source for clients who have not yet upgraded.

  Until they upgrade, some clients may need access to the original network share for install on demand, automatic feature repair, and other services.

• An updated network share from which clients can upgrade to the new service release.

Upgrading an administrative installation point

You must install an administrative update manually from the command line. After you download the executable update file from the Downloads on Microsoft Office Online, you expand the executable file into an MSP file. Then, on the command line, you run Windows Installer along with options to specify the path to the updated MSI file and the name of the updated MSP file.

• The MSI file is the Windows Installer package file from your original administrative image.

• The MSP file is the Microsoft Visio administrative update file that contains the changed files and other information necessary for the upgrade.

  The update instructs Windows Installer to add or update files in the administrative image.

The following procedures describe how to apply an update to an administrative installation point.

Note   Before you update an administrative installation point, make sure that nobody is using the network share. If a file on the network share is in use during the upgrade process, the Windows Installer will require a reboot of the computer that the administrative installation point is on to complete the installation. When the computer is rebooted, the updated file will be copied to the administrative installation point while the system is rebooting.

To apply an update to a Visio administrative installation point 

1. Download the executable update file from the Downloads on Microsoft Office Online, and extract the MSP file. To extract the MSP file, on the command line, use the following syntax:

[Visio_update.exe] /T:[path to temporary working folder that will hold the expanded MSP file] /C

**\[** ***Visio\_update.exe*** **\]** is a placeholder for the name of the update file, which will be different for each update. **/C** is an IExpress setup switch that, when used in conjunction with **/T:**, extracts files to the temporary folder but does not install them there.

**Note**   For more information about using IExpress setup switches, see the [Internet Explorer Administration Kit Service Pack 1](https://www.microsoft.com/technet/prodtechnol/ie/ieak/techinfo/deploy/60/en/) Web site.

2. Connect to the network share for your administrative installation point.

   You must have both write access to the administrative installation point on the server and the appropriate privileges to carry out the task.

3. On the Start menu, click Run, and then type the command line for Windows Installer with the appropriate options for your installation. Use the following syntax:

[start] msiexec /p [path\name of update MSP file] /a [path\name of MSI file] /qb /L*v [path\name of log file]

If an update contains multiple MSP files, you must run the command line separately for each MSP file that you apply to the administrative installation point—you cannot reference multiple MSP files on the same command line. The following table describes the command-line options:

Command-line option	Description
[start]	Required only for Windows 98 systems where Msiexec is not directly in the path.
Msiexec	Executable file name for Windows Installer.
/p	Enables Windows Installer to apply an update to an existing installation.
[path\name of update MSP file]	Path and file name of the MSP file for the update.
/a	Enables Windows Installer to perform an administrative installation of a product on a network share.
[path\name of MSI file]	Path and file name of the Windows Installer package for your original administrative image.
/qb	Sets the user interface to the basic level (simple progress and error handling).
/L*v	Turns on logging, and sets a path for the log file. The * flag causes the switch to log all information.
[path\name of log file]	Path and file name of the Windows Installer log file.

Note   For information about additional command-line switches, see the Help file that ships with the Windows Installer SDK, version 1.1 or later, or on the MSDN Web site.

Updating client computers from an administrative installation point

After you update your administrative installation point, you must perform a re-cache and reinstallation on existing client computers that use the administrative image. Any new client installations from the administrative installation point will automatically include the updated version of Microsoft Visio.

To update an existing client installation from an administrative installation point, run the following command line on the client computer:

[start] msiexec /i [path to updated .msi file on the administrative
image] REINSTALL=All REINSTALLMODE=vomus

You can run this command line by creating a log-on script, distributing it as a batch file, deploying it via Systems Management Server, or using other means according to your practice. The options for this command line are as follows:

Command-line option	Description
[start]	Required only for Windows 98 systems where Msiexec is not directly in the path.
Msiexec	Executable file name for Windows Installer.
/I	Indicates that the information in brackets that follows is the path to the administrative installation .msi file.
[path to updated .msi file on the administrative image]	Path and file name of the Microsoft Installer (.MSI) file on the administrative installation point.
REINSTALL=ALL	Specifies to reinstall all features on the administrative image.
REINSTALLMODE=vomus	Triggers the re-cache and reinstallation on the client computer, as follows: v--Re-caches the Installer database on the local machine. o--Reinstalls a file if it is missing, or if an older version is present. m--Rewrites all required machine-specific registry entries. u--Rewrites all required user-specific registry entries. s--Overwrites all existing shortcuts.

Note If you originally installed Visio on a client computer from an administrative installation point, you must follow the re-cache and reinstallation procedure described above to update that client. If you update the client directly by using a patch designed for stand-alone computers, the client and administrative images will become out of sync, which may cause future updates to fail.

Customizing Visio while deploying a service release

To modify your existing installations at the same time that you are deploying a service release, you must plan to carry out the two actions separately. For example, to make changes such as adding features or changing the installation states of existing Microsoft Visio features, first deploy the service release, and then proceed with the changes.

You cannot redeploy a transform (MST file) when you update an existing installation of Visio. A transform can only be used to configure Visio during the initial installation. If you try to apply a transform against existing installations, the transform is ignored and the existing settings are maintained.

Synchronizing independently updated client computers

If a client computer is upgraded independently of an administrative installation point, the computer may not recognize an administrative image after it has been updated. Further, its link to the original Visio source is no longer usable. To synchronize an independently updated client computer to recognize an updated administrative image, run the following command line on the client computer:

[path to updated administrative image] setup.exe /fvm [path to new MSI]

Applying an administrative update under Windows 2000

If your administrative installation point and all of your client computers are running Microsoft Windows 2000, you can use Microsoft IntelliMirror technology to manage the installation of an administrative update.

Note   Be sure to test all software updates in a controlled setting before modifying your administrative installation point or deploying the update throughout your organization.

To deploy a QFE fix or update under Windows 2000 

1. Apply the updates (MSP files) to the original Microsoft Visio administrative installation point.

   You must run the command line separately for each MSP file that you apply to the administrative installation point; you cannot reference multiple MSP files on the same command line.

2. Open the Software Installation snap-in within the Group Policy Object (GPO) that you are using to manage the existing Visio installation.

3. In the details pane, right-click the Visio package, point to All Tasks, and click Redeploy application.

The next time the Group Policy Object is applied to the designated users or computers, the updated files are copied to their computers.

Note   You can redeploy a package only if it is being managed by Group Policy—that is, only if you originally installed it by using IntelliMirror software installation and maintenance or if you brought it into a managed state under Windows 2000.

To help prevent people from installing an older patch over a newer patch, update the administrative installation point with updates and QFE fixes in the order of the build number on the files.

Upgrading a stand-alone computer

You can update a stand-alone computer (one not associated with an administrative installation point) directly from the Downloads on Microsoft Office Online.

When you download the update from the Downloads on Microsoft Office Online, the MSP files will be packaged in an IExpress package. To apply the patch, double-click the IExpress executable file to apply the patch.

As for all software installations and upgrades, to complete the upgrade, you must have the appropriate systems-level privileges on the computer.

Note   If you update a client computer independently of an administrative installation point on the same network, the client will no longer recognize the administrative image. Be sure to update client computers by using the procedures described in "Updating client computers from an administrative installation point," earlier in this section.

To install an update on a stand-alone computer

1. Close all Windows-based applications.

2. Go to the Downloads on Microsoft Office Online.

3. Follow the instructions on the Web page to display updates available to download for Visio 2002 SR-1.

4. Click the link for the update you want to download.

5. Click Download Now.

   To run the update with the default settings, in the File Download dialog box, click Open.

   or

   To run the update with command-line options, in the File Download dialog box, click Save, and then in the Save As dialog box, specify the location where you want to save the file. Then, on the Start menu, click Run, and then type the path and update name.

6. To confirm the installation, click Yes.

7. Read the license agreement, and click Yes to continue the installation.

8. If necessary, follow any additional instructions on your screen to complete the upgrade.

9. If you are prompted to do so, restart your computer after the installation is complete.