Setup Program

Article
02/20/2014

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.

Setup Components

Use the Microsoft® Project Setup program (Setup.exe) to do the following:

Create an administrative installation point for users to install Microsoft Project over the network.

Install Microsoft Project on users' computers.

Make changes to the installation in maintenance mode after Microsoft Project is installed.

Like Microsoft Project 2000 Setup, Microsoft Project 2002 Setup calls the Microsoft Windows® Installer to install Microsoft Project features; however, Microsoft Project 2002 Setup manages more of the installation process.

For example, on computers running Microsoft Windows NT® 4.0 and Microsoft Windows 98, Setup automatically checks for the required versions of shared and system files on the user's computer, and updates the files from the System Files Update before installing Microsoft Project. Setup can also coordinate installations of multiple chained packages through the Setup settings file (INI file).

Run Microsoft Project Setup by double-clicking Setup.exe. If Microsoft Project is not currently installed on the computer, you can also run Microsoft Project Setup by inserting the Microsoft Project 2002 CD in the CD-ROM drive. When Setup starts, it performs the following functions:

If the Windows Installer is not installed on the computer, Setup installs it from the Microsoft Project CD.

If Microsoft Project is installed, Setup allows the user to add or remove Microsoft Project features.

If Microsoft Project is not installed, Setup runs the Windows Installer (Msiexec.exe) to install Microsoft Project.

Setup Program

Microsoft Project Setup manages and coordinates the installation process from beginning to end. Setup spans required restarts and does not terminate until the last chained package is installed. Tasks performed by Setup include the following:

Detecting and installing required system files, including restarting and resuming if necessary

Installing Microsoft Project

Installing changed packages specified in the Setup settings file

Detecting an HTTP source and installing Microsoft Project from a Web server

Setup makes successive calls to the Windows Installer to perform the actual installation. All command-line options documented in this Resource Kit are defined for Setup, which passes appropriate options to Msiexec.exe.

Setup Settings File

Setup reads the Setup settings file and writes tasks to the registry based on the information contained in the settings file. You can customize the default Setup settings file (Setup.ini), or create your own custom INI files, to control many aspects of the installation process. Setup.ini is located in the Files\Setup folder on the administrative installation point. When you use the Setup INI Customization Wizard to specify your modifications, the wizard automatically writes the information in the appropriate sections of the INI file.

For Microsoft Project, the Setup settings file contains more information than previous versions, and includes several new sections:

[Product] section Contains the product code, product name, and version number. Setup uses this information to determine whether Microsoft Project is installed.

[MSI], [MST], and [Options] sections Contain information about Microsoft Project (MSI file) and any transform (MST file) to apply, as well as property settings for Microsoft Project installation. For example, you can specify a value for the COMPANYNAME property in the [Options] section.

[Display] section Contains settings for the user interface displayed during Setup. These settings override default values and apply to the entire installation process, including the System Files Update.

[Logging] section Contains the logging mode to use for each portion of the installation process, as well as the location and naming scheme for log files.

[Installer] section Contains Windows Installer information, including minimum version and the path to Instmsi.exe or Instmsiw.exe (the program that installs or upgrades Windows Installer).

[SystemPack] section Contains information about the System Files Update package, as well as some property settings to apply. For example, you can enter DISPLAY=Basic to display only simple progress indicators during the System Files Update installation, even if you set Microsoft Project installation to run with a full user interface.

[SystemPackOptions] section Contains custom settings and properties to pass to the System Files Update installation. For example, you can enter TRANSFORMS=Custom.mst to apply a transform to the System Files Update package.

[SystemPack_DetectionFileList] section Lists all the shared and system files and version numbers that Setup checks during the detection process.

[ChainedInstall_n] sections Contain information about chained packages and any transforms to apply. You can chain as many additional packages as you want and apply a transform to each one. These sections of Setup.ini are useful when you want to include multiple Microsoft Project Multilanguage User Interface Packs (MUI Packs) in a Microsoft Project installation.

Windows Installer

Windows Installer (which includes Msiexec.exe) installs Microsoft Project by using a dynamic-link library file (Msi.dll) to read the Windows Installer package (MSI file), apply a Windows Installer transform (MST file), incorporate command-line options supplied by Setup, and install programs and files on users' computers.

When a user selects a feature to install during Microsoft Project Setup, the Windows Installer identifies a corresponding set of components to copy to the computer. Each component consists of a unique set of files, programs, dynamic-link libraries, and registry entries that work together as a unit.

Windows Installer uses two types of files to install Microsoft Project: packages (MSI files) and transforms (MST files). A Windows Installer package is a relational database that contains all the information necessary to install a product. The MSI file associates components with features. It also contains information about the installation process itself, such as installation sequence, destination folder paths, system dependencies, installation options, and properties that control the installation process.

Like a Windows Installer package, a Windows Installer transform is a relational database that contains information about components, features, and Setup properties. A transform is based on a particular package and contains the modifications to apply to that package during installation. When you use the Custom Installation Wizard to create a transform, the wizard compares the original MSI file with the MSI file that has all your customizations incorporated. The differences are recorded in a transform; the original package is never altered.

Microsoft Project requires Windows Installer 1.1. The new version contains a number of improvements over Windows Installer 1.0, including better support for upgrading to a new version of a previously installed package.

If Windows Installer 1.0 is present on the computer, Setup automatically updates the program. If Windows Installer is not present on the computer, Setup calls Instmsi.exe (in Windows 98) or Instmsiw.exe (in Windows NT 4.0) to install it. Both the Microsoft Windows 2000 and Microsoft Windows Millennium Edition (Windows Me) operating systems include Windows Installer 1.1. If you are installing Microsoft Project on one of these operating systems, no Windows Installer update is required.

System Files Update

Microsoft Project requires minimum versions of a set of dynamic-link library (DLL) files, and other shared and system files. Before installing Microsoft Project under Windows NT 4.0 or Windows 98, Setup verifies that these key system files are up-to-date and, if they are not, updates them automatically from the System Files Update before proceeding with the rest of the installation.

The release versions of Windows 2000 and Windows Me include an equivalent or better level of the key system files required for Microsoft Project. Under Windows 2000 or Windows Me, you cannot install the System Files Update or run Internet Explorer Setup from the System Files Update. The /spforce command-line option has no effect on these operating systems.

If you are upgrading from Microsoft Project 2000 Service Release 1 under Windows 98 or Windows NT 4.0, and you have Microsoft Internet Explorer 5.01 or later, your system files are up-to-date. In these cases, you can install Microsoft Project without installing the System Files Update.

The System Files Update is a separate package (MSI file). If required, it is installed automatically with Microsoft Project, but you customize it in a separate transform applied to the Osp.msi package. Key system files and components in the System Files Update include the following:

Internet Explorer 5.01

HTML Help

Microsoft Data Access Components 2.5

Microsoft Visual Basic® for Applications Runtime

Microsoft Visual C Runtime

Microsoft Foundation Class 4.2

Tip The Setup settings file includes a list of the system and shared files that Setup checks before installing Microsoft Project, along with minimum required version numbers. Setup.ini is located in the Files\Setup folder on the administrative installation point; you can find the file list in the [SystemPack_DetectionFileList] section of Setup.ini.

Creating an Administrative Installation Point

The most common method of deploying a customized version of Microsoft Project 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 Microsoft Project from the Microsoft Project 2002 CD, and allows you to do the following:

Manage one set of Microsoft Project files from a central location

Create a standard Microsoft Project configuration for all users

Take advantage of flexible installation options

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

Manage controlled upgrades of Microsoft Project in the future

Running Administrative Setup for Microsoft Project

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

To create an administrative installation point for Microsoft Project

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

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

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

On the Microsoft Project CD, double-click Setup.exe and add /a to the command line.

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

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

Enter the 25-character product key and click Next.

Accept the end-user license agreement and click Install.

Setup copies the files from the Microsoft Project CD to the administrative installation point, extracts the compressed cabinet (CAB) files, and creates a hierarchy of folders in the root folder of the share. The System Files Update is automatically included during an administrative installation.

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

File	Location
Setup.exe	Root of the administrative image
Microsoft Project 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 Microsoft Project, 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 share available to users by providing them with read access.

When users run Setup to install Microsoft Project, any Microsoft Project features that are installed to run from the network uses this administrative installation point as the source of Microsoft Project files, and Microsoft Project runs the features over the network from this server. Similarly, for features that are set to be installed on first use, Microsoft Project 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 Microsoft Project from the administrative installation point, Setup uses the organization name that you specified as the default. In the Microsoft Project Custom Installation Wizard, you can create a Windows Installer transform 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 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, but in this case you must leave the organization name blank when you create the administrative installation point.

Replicating the Administrative Image

In many organizations, it makes sense to create multiple administrative installation points from which users can install Microsoft Project—and to which the Windows Installer can connect, to install or repair Microsoft Project 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, then 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.

Installing Microsoft Project on Client Computers

Users install Microsoft Project by running Setup from the Microsoft Project 2002 CD or from an administrative installation point that you create. Client Setup guides users through the process of installing Microsoft Project on their computers, using the information described below.

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 Microsoft Project is installed with the correct customizations, 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 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 distribute the batch file or shortcut to users in an e-mail message.

Unless you choose to install Microsoft Project quietly, the Setup user interface guides users through the following steps to install Microsoft Project on their computers:

Update system files

Enter user information

Select installation mode and location

Select installation options for Microsoft Project features

Select previous versions of Microsoft Project to keep

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 quiet mode. For information about installing Microsoft Project quietly, see the Customizing Setup resource kit article.

Update System Files

On Microsoft Windows 98 and 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 components related to Internet Explorer and Windows (such as HTML Help) that are required by Microsoft Project.

You can install the System Files Update quietly, 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 Microsoft Project installation.

Enter User Information

User information appears on users' computers in the About box (accessed from the Help menu) in Microsoft Project. If a user is installing Microsoft Project from the administrative installation point, Setup uses the organization name you specified without prompting the user.

Accept End-User License Agreement

When users install Microsoft Project from the CD, Setup displays an end-user license agreement page. When users install Microsoft Project 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 during Setup.

Select Installation Mode and Location

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

Installation mode

Users can select one of the following installation options:

Install Now Automatically installs the most frequently used Microsoft Project features in the default installation location and skips the remaining pages of Setup.

Upgrade Now Automatically upgrades to Microsoft Project 2002 and skips the remaining pages of Setup. This option removes all previous versions of Microsoft Project and installs Microsoft Project 2002 features based on the user's current configuration.

**Custom ** Allows the user to configure all aspects of Microsoft Project installation on the remaining pages of Setup.

**Complete ** Installs all Microsoft Project features locally on the user's computer. This option requires the most disk space but ensures that users do not need access to the Microsoft Project 2002 CD or an administrative installation point on the network later.

Run from Network Installs all Microsoft Project features to run over the network; only components that must be installed locally are copied to the user's computer. This option requires access to the network to run Microsoft Project.

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 Microsoft Project with the default settings, including the most commonly used components.
TypicalUpgradDescription	Upgrades your Microsoft Project 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 Microsoft Project.
CustomInstallDescription	Customize your Microsoft Project installation, selecting which Microsoft Project features to install on your computer.
CompleteInstallDescription	Installs Microsoft Project on your computer, including all optional components and tools.

Installation location

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

You can specify a default value for the installation location on the Specify Default Path and Organization page of the Office Custom Installation Wizard. You can also specify the location by setting the InstallLocation 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 Microsoft Project Features

When users choose the Custom installation mode, Setup displays a list of Microsoft Project features on the Selecting Features page, and users can set an installation state for each feature.

Alternatively, users can select Choose detailed installation options for each feature to further customize their Microsoft Project configuration. In this case, Setup displays the Microsoft Project 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 application or 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.

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

Select Previous Versions of Microsoft Project to Keep

If the user is upgrading from a previous version of Microsoft Project, Setup displays the version of Microsoft Project currently installed—which Setup removes when it installs Microsoft Project 2002. However, if the user installs Microsoft Project 2002 in a folder that is different from the folder in which the previous version of Microsoft Project is installed, the user can choose to keep the previous version of Microsoft Project.

Because Microsoft Project 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 Microsoft Project 2002.

On the Keep Previous Versions page of the Microsoft Project Custom Installation Wizard, you can specify default settings for this Setup page, or even hide this page from users altogether. The wizard also includes an option to remove obsolete files, shortcuts, and registry settings left over from previous versions.

Setup Program

On This Page

Setup Components

Setup Program

Setup Settings File

Windows Installer

System Files Update

See Also

Creating an Administrative Installation Point

Running Administrative Setup for Microsoft Project

To create an administrative installation point for Microsoft Project

Replicating the Administrative Image

See Also

Installing Microsoft Project on Client Computers

Running Setup from an Administrative Installation Point

Update System Files

Enter User Information

Accept End-User License Agreement

Select Installation Mode and Location

Installation mode

Installation location

Select Installation Options for Microsoft Project Features

Select Previous Versions of Microsoft Project to Keep

See Also

Additional resources