Visio 2000 Unattended Install Instructions
| 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. |
Published: September 1, 2000
For the latest information, please see https://www.microsoft.com/office/visio
On This Page
Introduction
Contents and Location of Files Provided for Unattended Installation
Microsoft Visio 2000 Program's Interactive Setup
Unattended Installation Instructions
Additional Information
Introduction
This document provides an overview of how the Microsoft Visio 2000 unattended installation works and is a guide to those deploying the program across an organization. This document describes the components of an interactive installation, as well as providing instructions for using unattended options. Both interactive and unattended installations are on the Visio CDs distributed in the October Select shipment. This documentation is intended for IT professionals deploying Visio 2000 programs across an organization. End users wanting to install Visio 2000 should refer to the readme.wri file on the CD. It is highly recommended that the entire document be read in order to insure successful deployment.
For Visio 2000 unattended installation availability and editions and language versions supported, see Microsoft Visio 2000 Unattended Installation.
Contents and Location of Files Provided for Unattended Installation
In addition to these instructions, all files necessary to create an unattended installation are included on the Visio Select CDs. Table 1.1 describes the files or folders, location, and purpose.
Table 1.1 Unattended installation files
File or folder name |
Location on CD |
Description |
|---|---|---|
Vis2000.msi |
\Install\Unattended |
Installer package for Microsoft Visio 2000. |
Vis2000.pdf |
\Install\Unattended |
File for deployment via SMS 1.2 |
Vis2000.sms |
\Install\Unattended |
File for deployment via SMS 2.0 |
Visio program files installed by Vis2000.msi are located in the Install\Unattended\Program Files folder. For a complete list of files installed, see filelist.wri.
Microsoft Visio 2000 Program's Interactive Setup
Overview
The Visio program's interactive installation is intended for people who are installing on a small number of computers or by companies that allow individuals to install and customize their own desktops. The installation works in two parts: system configuration and Microsoft Visio program installation. You launch setup by double-clicking Setup.exe. Setup.exe checks to see if your system needs to be updated by calling the Microsoft System Updater (MSSUP.exe). Depending on the state of the system, up to eight separate micro-components will be installed during this time. After MSSUP.exe has completed, Setup.msi is called to install the Visio Installation Manager (VIM.exe). The VIM.exe provides a user interface that allows the person installing to choose which Microsoft Visio program content to install. The VIM.exe also controls modifications to the program after installation is complete.
Microsoft System Updater
Explanation of components
MSSUP.exe is responsible for making sure the system has all necessary components to run Visio. MSSUP.exe is a wrapper that calls the various components found in the Visio\Install\bin\sp folder on the CD. If necessary, each component is installed. After an individual component is installed, control is returned to MSSUP.exe and the next component is then called.
Table 1.2, Micro-components list, contains components, files called for setup, versions, and descriptions of what each component does. Individual components can be installed manually by running either the .exe or .msi file found in their respective directories.
Table 1.2 Micro-components list
Component |
Filename |
Version |
Description |
|---|---|---|---|
Standard, Professional, Technical, and Enterprise Editions |
|||
ComUpd |
401comupd.exe |
4.72.3110.0 |
Common Controls: Various common components such as the File and Open dialog boxes. Installed only if the system does not already have this version. Also provided by Microsoft Windows 2000 and Microsoft Office 2000 SR1A. |
DAO |
DAO.msi |
3.6 |
Data Access Objects: Necessary for some of the database features in the Visio program. Installed only if the system does not already have this version. Also provided by Windows 2000 and Office 2000 SR1A. |
DCOM95 |
DCOM95.exe |
4.71.1015.0 |
Distributed COM: Installed only on Windows 95, if needed. Required for VBA to install. Also provided by Office 2000 SR1A. |
HHUPD |
HHUpd.exe |
4.73.8252.0 |
HTML Help Update: Used for the HTML Help system. Installed only if the system does not already have this version. Installed regardless of whether the user asks for Help files or not. Also provided by Office 2000 SR1a. |
IE |
IE5setup.exe |
5.0.2314.1000 |
Internet Explorer 5. Installed only if the system does not have Internet Explorer 4.01 SP1 or later. Internet Explorer 4.0.1 or greater is required for the Help system to function. Also provided by Windows 2000 and Office 2000 SR1a. See also IE for Enterprise and Technical Editions. |
MDAC |
Mdac_typ.exe |
21.2.4202.3 (MDAC 2.1 SP2) |
Microsoft Data Access Components: Necessary for most of the solutions that require or use any type of database access. This is the new way that Microsoft packages its components to allow products access to database-type objects (for example, a Microsoft Access database). Installed only if the system does not already have this. Also provided by Windows 2000 and Office 2000 SR1a. NOTE: MDAC does not include DAO. |
MSI |
InstMSI.exe |
1.0 |
Windows Installer: Required to install the Visio program or any other MSI packages. Version 1.1 is required for unattended install. Windows Installer version 1.1 is also provided by Office 2000 SR1a. |
SPCORE |
SPCore.msi |
Redistributable files |
These are the Microsoft Visual Studio redistributable files that the engine requires to run. Always installed and requires a restart when running via MSSUP.exe. |
VBA |
VBA6.msi |
6.0 |
Microsoft Visual Basic for Applications. Installed only if the system does not already have this version or has an earlier version. Also provided by Office 2000 SR1a |
Enterprise and Technical Editions only |
|||
Repository |
Repository.msi |
2.0 |
Microsoft Repository. Used for UML and Facilities Management solutions. |
IE |
IE5setup.exe |
5.0.2314.1000 |
Internet Explorer 5.0 is required for MSDE (Enterprise Edition) and the Facilities Management (Technical Edition) solution. Also provided by Windows 2000 and Office 2000 SR1a. |
Enterprise Edition only |
|||
MSDE |
MSDEx86.exe |
1.0 |
Microsoft Data Engine. Used for AutoDiscovery and Layout. |
Winsock |
ws2setup.exe |
2.0 |
Used for AutoDiscovery and Layout. Installed on Windows 95 computers only. |
ADSI |
ADSI25_w95.exe |
2.5 |
Active Directory Services Interface. Required for Active Directory features. ADSI25_w95.exe will install on Microsoft Windows 95. ADSI25_w98.exe will install on Microsoft Windows 98. ADSI25_i386.exe will install on Microsoft NT 4.0 and Microsoft Windows 2000. |
Restarting
Depending on what components were installed by MSSUP.exe, up to two restarts may occur. If ComUpd.exe, DCOM95.exe, or IE5setup.exe has been installed, there will be a restart before installing VBA 6. If VBA6.msi, Mdac_typ.exe, or SPCore.msi has been installed, another restart will be triggered. SPCore.msi always installs, so if MSSUP.exe has been run, a restart will always happen.
Visio Installation Manager (VIM.exe)
The VIM.exe presents the user interface and allows users to choose the solutions they want to install. VIM then calls the individual MSI files that correspond with the solutions chosen.
Description of Visio program MSI packages
All Visio program MSIs for the interactive installation are located in the Visio\Install\bin folder. Most MSIs in this directory have a name similar to the solution they install, with the exception of a few files.
VisioCore.msi installs add-ons common to all four editions. 1Engine.msi installs the engine files. Other MSI files may appear to be empty, but function as parents for the Visio program features.
Running Setup with /m
If you know that the system is already properly configured, you do not have to run MSSUP.exe to install the Visio program. From a Windows command line, start the Setup.exe located in the Install folder with a /m to avoid running MSSUP.exe. This option will still install and start VIM.exe but will not install system components or cause a restart. This option requires user interaction.
Unattended Installation Instructions
Overview
The unattended installation of the Microsoft Visio program is intended for IT professionals who want to deploy across an organization without end-user interaction. If end-user input is required, the Visio 2000 interactive installation is strongly recommended.
System Requirements
The unattended installation on this CD is designed to run on a system that already has Microsoft Windows 2000 and Office 2000 SR-1a installed. If both are installed, the only component for MSSUP.exe that needs to be installed is SPCore.msi. The system will then be sufficient to properly run Microsoft Visio 2000 Standard Edition and Microsoft Visio 2000 Professional Edition. See the section titled Microsoft System Updater for further details on requirements for Microsoft Visio 2000 Technical Edition and Microsoft Visio 2000 Enterprise Edition.
MSI Command-line Options and Syntax
The executable program that interprets MSI packages and installs products is Msiexec.exe. Command-line options can be passed to the Msiexec.exe application. Table 1.3, MSI command-line options supported by the Microsoft Visio 2000 program's unattended installation, describes the supported options. The Visio program does not support all command-line options offered by MSI. Additional information on the Windows Installer is at https://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsinstal/html/veconmicrosoftwindowsinstallertechnology.asp .
Note: Options are not case sensitive. Case is shown here to distinguish between letters of similar appearance.
Table 1.3 MSI switches supported by Microsoft Visio 2000 program's unattended installation
Option |
Parameters |
Meaning |
|---|---|---|
/I |
Package|ProductCode |
Installs or configures a product. See Table 1.4 for ProductCodes |
/f |
[p|o|e|d|c|a|u|m|s|v] Package|ProductCode |
Repairs a product. This option ignores any property values entered on the command line. The default argument list for this option is 'pecms'. This option shares the same argument list as the REINSTALLMODE property. |
p - Reinstall only if file is missing. |
||
o - Reinstall if file is missing or if an older version is installed. |
||
e - Reinstall if file is missing or an equal or older version is installed. |
||
d - Reinstall if file is missing or a different version is installed. |
||
c - Reinstall if file is missing or the stored checksum doesn't match the calculated value. Only repairs files that have msidbFileAttributesChecksum in the Attributes column of the File table. |
||
a - Force all files to be reinstalled. |
||
u - Rewrite all required user-specific registry entries. |
||
m - Rewrite all required machine-specific registry entries. |
||
s - Overwrite all existing shortcuts. |
||
v - Run from source and re-cache the local package. |
||
/a |
Package |
Administrative installation option. Installs a product on the network. See NOTE below on installing to non-Windows 2000 machines. |
/x |
Package|ProductCode |
Uninstalls a product. |
/L |
[I|w|e|a|r|u|c|m|o|p|v|+|!]Logfile |
Specifies path to log file and the flags indicate which information to log. |
i - Status messages. |
||
w - Non-fatal warnings. |
||
e - All error messages. |
||
a - Start up of actions. |
||
r - Action-specific records. |
||
u - User requests. |
||
c - Initial UI parameters. |
||
m - Out-of-memory or fatal exit information. |
||
o - Out-of-disk-space messages. |
||
p Terminal properties. |
||
v - Verbose output. |
||
! - Flush each line to the log. |
||
"*" - Wildcard, log all information except for the v option. To include the v option, specify "/l*v". |
||
/m |
File name |
Generates an SMS status .mif file. Must be used with the install (-i), remove (-x), administrative installation (-a), or reinstall (-f) options. The ISMIF32.DLL is installed as part of SMS and must be on the path. |
The fields of the status .mif file are filled with the following information: |
||
Manufacturer Author |
||
Product - Revision Number |
||
Version - Subject |
||
Locale - Template |
||
Serial Number - not set |
||
Installation - set by ISMIF32.DLL to "DateTime". |
||
InstallStatus - "Success" or "Failed". |
||
Description - Error messages in the following order: (1) Error messages generated by installer: (2) Resource from msi.dll if installation could not commence or user exit: (3) System error message file: (4) Formatted message: "Installer error %i", where %i is error returned from msi.dll. |
||
/q |
N|b|r|f |
Sets user interface level. |
q , qn - No UI. |
||
qb - Basic UI. |
||
qr - Reduced UI with a modal dialog box displayed at the end of the installation. |
||
qf - Full UI with a modal dialog box displayed at the end of the installation. |
||
qn+ - No UI except for a modal dialog box displayed at the end of the installation. |
||
qb+ - Basic UI with a modal dialog box displayed at the end of the installation. The modal box is not displayed if the user cancels the installation. |
||
qb- - Basic UI with no modal dialog boxes. Note that /qb+- is not a supported UI level. |
||
/? or /h |
Displays copyright information for the Windows Installer. |
|
/y |
Module |
Calls the system API DllRegisterServer to self-register modules passed in on the command line. For example, msiexec /y my_file.dll. |
This option is used only for registry information that can't be added using the registry tables of the .msi file. |
||
/z |
Module |
Calls the system API DllUnRegisterServer to unregister modules passed in on the command line. For example, msiexec /z my_file.dll. |
This option is used only for registry information that can't be removed using the registry tables of the .msi file. |
To install the Visio program silently from the CD, where the CD is drive D, the syntax is:
msiexec /i D:\Install\Unattended\Vis2000.msi /qn
Note: On non-Windows 2000 machines, the target directory must also be set in both the command line and the installation dialog. The syntax is:
msiexec.exe /a D:\Install\Unattended\Vis2000.msi TARGETDIR="Install Location"
The /a switch is not silent. Make sure the install path entered into the dialogs matches the path set as the TARGETDIR on the command line.
Table 1.4, ProductCodes, lists ProductCodes for Microsoft Visio 2000 products that support unattended installation.
Table 1.4 ProductCodes
Edition |
Language |
ProductCode |
|---|---|---|
Microsoft Visio 2000 Standard Edition |
US English |
{0CB79209-9660-465B-B6B2-1A29891DD6E4} |
Microsoft Visio 2000 Standard Edition |
British English |
{00FF7AAA-A140-45D7-9E49-1DFC7B3A8161} |
Microsoft Visio 2000 Professional Edition |
US English |
{0B438E9A-D40F-47B6-95A3-9AD8ED796EA2} |
Microsoft Visio 2000 Professional Edition |
British English |
{0E7E203C-155B-4ECE-B972-953EC89AEE6D} |
Public Properties
In addition to options listed in Table 1.3, public properties may be modified using the command line. Public properties can be identified by names containing no lower case letters. All property names on the command line are interpreted as uppercase but the value retains case sensitivity. If you enter MyProperty at a command line, the installer overrides the value of MYPROPERTY and not the value of MyProperty in the Property table. To install the Visio product with PROPERTY set to VALUE, use the following syntax on the command line. You can put the property anywhere except between an option and its argument.
Correct syntax assuming install from the CD on drive D:
msiexec /i D:\Install\Unattended\Vis2000.msi PROPERTY=VALUE
Incorrect syntax:
msiexec /i PROPERTY=VALUE D:\Install\Unattended\Vis2000.msi
Public properties can also be changed by applying a transform. Table 1.5 lists commonly modified properties and a brief description. For a list of related properties and detailed descriptions, see the Microsoft Windows Installer documentation or visit https://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsinstal/html/veconmicrosoftwindowsinstallertechnology.asp .
Table 1.5 Public properties for the Visio 2000 program
Property |
Default value |
Purpose |
|---|---|---|
INSTALLLEVEL |
700 |
Initial "level" at which features will be installed. |
PRIMARY FOLDER |
INSTALLDIR |
Allows the author to designate a "primary" folder for the installation. |
INSTALLDIR |
Microsoft Visio |
The folder for installation. |
ARPURLUPDATEINFO |
URL for application update information. |
|
ALLUSERS |
2 |
Determines where configuration information will be stored. |
ARPHELPTELEPHONE |
+1 (425) 454-2030 |
Telephone number for technical support. |
ARPREADME |
Readme.txt |
Provides the Add/Remove Control Panel ReadMe for the application that is written under the Uninstall Registry Key |
REBOOTPROMPT |
S |
Suppresses the display of prompts for restarts to the user. Will not suppress a restart. |
ARPCONTACT |
Microsoft Corporation |
Provides contact for the Add/Remove Control Panel. |
Using MSSUP.exe with Unattended Install
If you want MSSUP.exe to configure your system automatically, it can be used in conjunction with the new single MSI file.
To attach MSSUP.exe to the unattended install MSI:
Copy the contents of the CD to your hard drive.
Move the contents of the Unattended Install folder into the \Install\bin\sp\vim folder.
Delete the Setup.msi file from that folder.
Rename Vis2000.msi to Setup.msi.
To use MSSUP.exe with the unattended MSI:
Make sure the computer has the Microsoft Windows Installer version 1.1 installed.
Run the Setup.exe executable located in the \Install folder. This will start MSSUP.exe.
After MSSUP.exe has completed (including up to two restarts), it will start the new Setup.msi file, which has unattended functionality.
Note: The MSSUP.exe portion of the install will not be silent.
Office Custom Installation Wizard
The Custom Installation Wizard creates transforms for Office products. The Visio products' .msi files were not designed to work with the wizard, and caution must be used with this method.
Upgrade scenarios
The unattended installation will ignore Visio product versions 5.0 and lower if present on the system. Unless you want two Visio product versions on the system, uninstall any previous versions. Version refers to the number associated with the release (e.g. 5.0, 2000).
The unattended installation will remove any Visio 2000 editions found on the system. This includes different editions from the one being installed. For instance, if the Technical Edition is already on the computer and an unattended installation of Professional Edition is performed, Technical Edition will be removed from the computer. Drawing files will not be removed. Edition refers to the type of product (e.g. Standard, Professional, Technical, Enterprise).
Known issues
Developing Visio Solutions will not install via the unattended installation.
The Microsoft Visio 2000 unattended installation will not install over future versions of Visio products.
More than one edition may be installed to the same computer using the unattended option. Both products will install to the same directory by default; however, both will be listed in add/remove programs.
- The US English Professional Edition, International English Standard Edition, and International English Professional Edition incorrectly install the Visio Products.mdb file. The Shape Explorer feature uses this file and searches utilizing this file may provide inaccurate results. To correct the problem, copy the correct file to the user's system. The correct Visio Products.mdb file can be found on the CD in the Install\bin\Program Files\Visio\Solutions directory.
Additional Information
For more information: https://www.microsoft.com/office/visio