Overview
System requirements
Microsoft Project Setup
Install from the CD
Create an administrative installation point
Product Activation
Workgroup Message Handler
Install Workgroup Message Handler
ADDENDUM TO END USER LICENSE AGREEMENT FOR MICROSOFT SOFTWARE
Customizing Microsoft Project Setup
Setup components
Specify command-line options
When to use command-line options
How to distribute command-line options
Setup display settings
Install Microsoft Project quietly
Customize the Setup settings file
When to use a custom Setup settings file
How to distribute a custom Setup settings file
How to use the Setup INI Customization Wizard
System Files Updates options
Setup error messages and failure reporting
Resolve Setup conflicts
Microsoft Project Resource Kit
Customizing Setup Appendix
Setup command-line options
Setup.INI File Format
Properties for Setup and MSIs
Properties for Setup user interface
Properties for configuration of applications
Properties for Internet Explorer 5.01 Setup
This document provides information about installing Microsoft Project Standard 2002 and Microsoft Project Professional 2002, including basic setup, installation of the Workgroup Message Handler, custom setup, setup command-line switches, and setup properties.
Most users only need to review the following sections: System requirements, Microsoft Project setup, and Workgroup Message Handler. The rest of this document contains information about customizing Microsoft Project Setup.
Note If you want to take advantage of the enterprise features built into Microsoft Project Professional, it must be connected to Microsoft Project Server.
Microsoft Project has the following system requirements:
Additional items or services required to use certain features:
There are several methods you can use to install or deploy Microsoft Project:
Note An administrative installation point must be created before you can install or run Microsoft Project from a network share. See Create an administrative installation point for more information about creating an administrative installation point.
To install Microsoft Project Standard or Microsoft Project Professional directly from the CD, place the CD in your CD-ROM drive and follow the steps indicated during the Setup process.
Note If the Setup program does not begin automatically, select the Start menu, click Run, and then click Browse. On the Microsoft Project 2002 CD in the CD-ROM drive, select Setup.exe, click Open, then click OK.
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, then have users run Setup from that location. Creating an administrative installation point provides several advantages over installing Microsoft Project from the CD, and allows you to do the following:
To create an administrative installation point, do the following:
Note You can only create an administrative installation point if your copy of Microsoft Project includes the prjstde or prjproe MSI file in the root directory of the Microsoft Project CD.
| 1 | Create a share on a network server for the administrative installation point.
The network share must have at least 550 megabytes (MB) of available disk space. |
|
| 2 | Make sure you have write access to the server share, then connect to it. | |
| 3 | On the Start menu, click Run, and then click Browse. | |
| 4 | On the Microsoft Project CD in the CD-ROM drive, select Setup.exe and click Open. | |
| 5 | In the Open box, following Setup.exe, type /a, and then click OK.
For example: d:\setup.exe /a |
|
| 6 | When prompted, enter the organization name that you want to define for all users who install Microsoft Project from this location, then enter the server and share you created as the administrative installation point. |
After you create the administrative installation point, make sure it is available to users by providing them with read access.
Tip It may make sense to create multiple administrative installation points from which your users can install Microsoft Project. 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.
Once you have created an administrative installation point, users may either install or run Microsoft Project from this location.
Note After installation, access to the administrative installation point is still required to run Microsoft Project Standard or Microsoft Project Professional from the network.
Product activation technology is built into Microsoft Project. Product activation is not registration, but rather technology aimed at reducing software piracy in order to ensure you are receiving the product quality that you expect. You may be prompted to activate Microsoft Project after you have completed installation in one of the following methods:
Some quick facts about product activation:
For more information about Microsoft product activation, including frequently asked questions, see the Microsoft Software Piracy web site.
The Workgroup Message Handler is an e-mail communication tool that allows a project manager to communicate with resources assigned to tasks from Microsoft Project. The project manager must install the Workgroup Message Handler, and distribute it to resources assigned to tasks who can then communicate with the project manager about their assignments using e-mail.
Note See Microsoft Project Help for more information about team collaboration. In the Type a question for help box, type team collaboration.
Workgroup Message Handler is compatible with MAPI-compliant client e-mail applications, including:
The Workgroup Message Handler is located in the \Files\Support\WGSetup folder on your Microsoft Project CD or administrative installation point. Here are two ways to distribute the Workgroup Message Handler:
Microsoft Project Standard 2002
Microsoft Project Professional 2002
This addendum ("Addendum") provides additional rights to the End User License Agreement for Microsoft Software ("EULA") for the one software product identified above that you have validly licensed ("SOFTWARE PRODUCT"). This Addendum pertains solely to portions of the SOFTWARE PRODUCT identified below as the Microsoft Project Workgroup Message Handler.
1. ADDITIONAL RIGHTS. In addition to the rights granted to you in the EULA, you may reproduce and distribute an unlimited number of copies of the Microsoft Project Workgroup Message Handler, which is comprised of the following files:
| Acmsetup.exe | Msvcrt.dll | Openmail.exe | Stdole2.tlb |
| Acmsetup.hlp | Off97_bb.dll | Opml32.dll | Wgsetup.exe |
| Extract.exe | Oleaut32.dll | Prj2k_ca.dll | Wgsetup.inf |
| Mfc42.dll | Olepro32.dll | Regwiz.exe | Wgsetup.lst |
| Msflxgrd.ocx | Olmenu.dll | Setup.ini | Wgsetup.stf |
| Mssetup.dll | Olmenu.ecf | Setup.tdf |
provided that each copy of the Microsoft Project Workgroup Message Handler you distribute shall be a true, complete and unmodified copy, including all copyright and trademark notices.
2. OTHER TERMS AND CONDITIONS. Except as expressly stated herein, your rights to the Microsoft Project Workgroup Message Handler are governed by all remaining provisions of the EULA.
This section includes information about how to customize the installation of Microsoft Project, including setup components, installation location, using and distributing command-line options, and the Setup INI Customization Wizard. For additional customization information, see the Microsoft Project Resource Kit section in this document.
There are four primary setup components when installing Microsoft Project:
Setup.exe (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:
Setup will make successive calls to Windows Installer (Msiexec.exe) to perform the installation of each package listed in the Setup settings file. See Setup command-line options for a description of the available command-line descriptions available when you run Setup from the command line.
The Microsoft Project Setup.ini file stores settings for Setup. During installation of Microsoft Project, Setup will read information from Setup.ini and write this information to the registry. You can customize Setup.ini or create a custom INI file to control many aspects of the installation process. You can modify Setup.ini directly by opening Setup.ini in Notepad (or a similar text editor), or you can use the Setup INI Customization Wizard to make your changes (the wizard automatically writes the updated information in the appropriate sections of the INI file). See Setup.INI File Format for more information about the sections contained within the Setup.ini file.
See Setup command-line options for a description of the available command-line descriptions available when you run Setup from the command line.
Windows Installer installs Microsoft Project by using a dynamic-link library file to read the Windows Installer package (MSI file), apply a Windows Installer transform (MST file), and incorporate command-line options supplied by Setup.
Windows Installer uses two types of files to install Microsoft Project: packages (MSI files) and transforms (MST files). An MSI file is a relational database that contains all of the information necessary to install Microsoft Project. It associates components with features and contains information about the installation process itself, such as installation sequence, destination folder paths, system dependencies, installation options and properties. An MST file is also a relational database that contains information about components, features, and Setup properties. It is based on a particular MSI file and contains modifications specific to that package.
Microsoft Project requires minimum versions of a set of dynamic-link library (DLL) files and other shared and system files, including Microsoft Internet Explorer. Before installation, Setup verifies whether these files are up-to-date and, if not, updates them automatically from the System Files Update before proceeding with the rest of the installation. System Files Update is a chained package during Microsoft Project installation.
Note Setup.ini includes a list of the system and shared files that Setup checks before installing Microsoft Project, along with the minimum required version numbers. See the [SystemPack_DetectionFileList] section of Setup.ini for more information.
When you run setup, you can use command-line options to change some of the parameters that Setup uses to install Microsoft Project, including:
For example, you can enter the following options on the command line:
setup.exe /qb+ /l* %temp%\Project10.txt COMPANYNAME="Your Company Name"This command line customizes Setup in the following ways:
For more information about all of the available Setup command-line options and properties see Setup command-line options or Properties for Setup and MSIs in the appendix section of this document.
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 Microsoft Project configuration to everyone, but define different command lines for targeted groups of users.
For example, you can have your Project Management and Accounting departments install the same set of Microsoft Project 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="Project Management"setup.exe /q /settings Custom.ini COMPANYNAME="Accounting"Command-line options are also useful if you use Microsoft Systems Management Server or another systems management tool to create multiple development 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.
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 an MS-DOS 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 logon 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.
When you distribute Microsoft Project 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 silently so that your configuration of Microsoft Project is installed with no questions asked. You can even set different display settings for different portions of the installation process.
Note See [Display] for a description of the display properties.
By default, Setup installs Microsoft Project with a full user interface and displays a completion notice at the end of the installation. In many large organizations, however, it is more efficient to install Microsoft Project without any user interaction. In this case, the recommended setting is /qb-, which installs Microsoft Project as follows:
When you run Microsoft Project 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, then 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 Microsoft Project 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.
You can customize the Setup settings file (Setup.ini) either in a normal text editor or by using the Setup INI Customization Wizard. Before applying the values specified on the command line, Setup reads the properties specified in the Setup settings file, where you can set all the properties that can be entered on the command line. For example, you can:
The Setup.ini file for Microsoft Project also contains several new sections that allow you to specify settings that you cannot add to the command line. For example:
In most sections of Setup.ini, including the [Options] and [SystemPackOptions] sections, you can use the syntax PROPERTY=value to specify custom property values. The Microsoft Project Resource Kit includes the Setup INI Customization Wizard, which 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 See How to use the Setup INI Customization Wizard for more information about the Setup INI Customization Wizard.
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 the Setup settings file to set most Setup properties, you can reserve the command line for specific and targeted modifications, or changes that you need to make late in the deployment process. Customization of the Setup settings file is especially useful when Setup.exe is run from an administrative installation point, rather than from a batch file or shortcut to install a customized version of Microsoft Project.
The Setup INI Customization Wizard provides a convenient user interface for creating custom versions of the Setup settings file. The wizard also helps 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.
Note The Setup INI Customization Wizard can be downloaded from the Microsoft Project Resource Kit.
Before you can use the Setup INI Customization Wizard, you must create a Microsoft Project administrative installation point. Your custom INI file must be based on an existing INI file, such as the Setup settings file for Microsoft Project.
To create a custom Setup settings file, do the following:
| 1 | In the Setup INI Customization Wizard, enter the path to your Microsoft Project 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. Click Default to use the logging mode specified in the INI file; click Verbose to use all logging options. Note that verbose logging creates very large log files. |
|
| 4 | Under Display, select a default display setting and click Next. The wizard searches the administrative installation point for additional packages (MSI files) that you can chain to the Microsoft Project 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 Microsoft Project package. You can change the order in which subsequent packages are installed. |
|
| 7 | Select each package, specify the options you want for that package, and click Next. For each package, you can specify an MST file and a unique display setting, and 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. The wizard supplies you with a sample Setup command line that specifies your custom INI file with the /settings option. |
|
| 10 | Click Finish to exit the wizard. |
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.
When you edit the default Setup settings file, users can run Setup without using command-line options to install Microsoft Project 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\proj10.ini
If you run Setup from a network logon script or through a systems management tool (such as Systems Management Server), then 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.
Note 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.
Unless you are installing Microsoft Project on Windows 2000, Windows Me, or Windows XP, Microsoft Project 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 Microsoft Project installation. If it fails this test, Setup calls Windows Installer to install the System Files Update and update the files.
If you are installing Microsoft Project on Microsoft Windows NT 4.0 or Microsoft Windows 98, you can control this default Setup behavior by using the following command-line options:
You can also set the NOIE property to True on the command line, in the [SystemPackOptions] section of the Setup settings file, 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, except for required components.
Note Because Windows 2000, Windows Me, and Windows XP 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.
Microsoft Project Setup allows you to customize the error messages 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.
Microsoft Project Setup can be customized in several ways. This can result in Setup conflicts. 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:
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.
The Microsoft Project Resource Kit contains information about:
Visit the Microsoft Project Resource Kit for more information about these topics.
When you run Setup, you can use command-line options to change some of the parameters that Setup uses to install Microsoft Project, such as display settings and default values for Setup properties. Command-line options override duplicate customizations in the Setup settings file or in a transform.
Note The Windows Installer package (MSI file) must be in the same folder as Setup.exe. In the case of Microsoft Project, it should be in the root folder of the administrative installation point.
Refers the user to information about command-line options available in the Office Resource Kit. Information about command-line options is also available in the Microsoft Project Resource Kit.
Creates an administrative installation point for the specified package. The package should be in the same folder as Setup.exe, or the path must be included on the command line. For example:/a Prjproe.msi/a "subfolder\Prjproe.msi"
Runs Setup automatically when the Microsoft Project CD is inserted in the CD-ROM drive; used only in the Autorun.inf file.
Forces repair of an application associated with the specified package. The package must be in the same folder as Setup.exe, or the path must be included on the command line. For example:/fp Prjproe.msi
Note You must specify the same package (MSI file) that was used to install the original application.
Valid parameters for options include the following:
| Parameter | Definition |
|---|---|
| a | Force reinstallation of all files regardless of checksum or version. |
| c | Reinstall file if missing or corrupt. |
| d | Reinstall file if missing or a different version is present. |
| e | Reinstall file if missing or an equal or older version is present. |
| m | Rewrite all required HKEY_LOCAL_MACHINE registry entries. |
| o | Reinstall file if missing or an older version is present. |
| p | Reinstall file only if missing. |
| s | Reinstall all shortcuts and overwrite existing shortcuts. |
| u | Rewrite all required HKEY_CURRENT_USER registry entries. |
| v | Recopy the package (MSI file) from the original source and recache it on the local computer. |
Note The Detect and Repair command (Help menu) in Microsoft Project performs the same function as /focums. Running Setup and selecting Reinstall performs the same function as /fecums.
Installs applications using the specified package. The package must be in the same folder as Setup.exe, or the path must be included on the command line. For example:/i Prjproe.msi/i "subfolder\Prjproe.msi"
Note The default behavior of Setup.exe performs the same function as /i.
Advertises the application on the computer and installs on first use; you must specify an option to advertise the application to either the computer or the user. You can use /j only when running Setup from an administrative installation point. If no package is specified, Setup uses the package specified in Setup.ini. To apply a transform to the advertised package, use the option /t and specify an MST file. For example:/jm Prjproe.msi /t Prjtrns.mst
Notes
Note
Valid parameters for options include the following:
| Parameter | Definition |
|---|---|
| m | Advertise to all users on the computer. |
| u | Advertise to the current user. |
Creates a log of installation actions. The /l command-line option overrides default settings specified in the Type key in the [Logging] section of Setup.ini.
Default logging options for Microsoft Project are vpiwaeo.
The /l option creates a log file for Setup and a log file for each Windows Installer task. Logfile is the name and path of the log file to create. When you include the (*) in the log file name, Setup creates a unique file name for each instance of Setup by replacing the (*) with the first available 4-digit string, for example 0001, 0002, etc. For example:
/lv* "%temp%\Microsoft Project Setup(*).txt
This command line would create the following verbose log files:
Valid parameters for options include the following:
| Parameter | Definition |
|---|---|
| a | Start of action notification |
| c | Initial UI parameters |
| e | Error messages |
| i | Information-only messages |
| m | Out-of-memory messages |
| o | Out-of-disk space messages |
| p | Property table list in form property=value |
| r | Action data record; contains action-specific information |
| u | User request messages |
| v | Verbose; includes debug messages |
| w | Warning messages |
| * | Turn on all logging options except v |
| + | Append to existing log file |
Does not restart the computer or display a restart dialog box at the end of the installation. The /noreboot option passes the REBOOT=ReallySuppress property to each package included in the Microsoft Project installation except the last one.
Overrides the System Files Update detection process and does not install the System Files Update package (Osp.msi).
Note It is possible for an install process to abort or fail when Osp.msi is not installed when needed; therefore, caution should be used when including this option.
Sets the Setup user interface display level.
Valid parameters for options include the following:
| Parameter | Definition |
|---|---|
| b | Display only simple progress indicators and error messages (Basic). |
| f | Display all dialog boxes and messages; equivalent to omitting the /q option (Full). |
| n | Display no user interface; equivalent to specifying /q with no options (None). |
| r | Display all progress indicators and error messages, but collect no user information (Reduced). |
| - | Suppress all modal dialog boxes; used with b, f, n, or r. |
| + | Add completion message to the n or b option. |
Note The completion message is displayed only when Setup does not have to restart the computer after the installation.
Specifies a custom Setup settings file for Setup.exe to use in place of Setup.ini. The settings file must be in the same folder as Setup.exe, or the path must be included on the command line. For example:/settings MyApp.ini
Installs the System Files Update (Osp.msi) even if the detection process determines that it is not required. This option does not work on Windows 2000, Windows Millennium Edition (ME), or Windows XP.
Installs only the System Files Update (Osp.msi); does not install Microsoft Project. Use this option to install the System Files Update on computers running under Windows 98 or Windows NT 4.0 before beginning the Microsoft Project deployment process.
Directs Setup.exe to allow Windows Installer (Msiexec.exe) to complete before terminating the installation process. The /wait option is no longer required; the functionality is now built into Setup.exe as part of the default behavior.
Installs Microsoft Project or Microsoft Project Multilingual User Interface Packs (MUI Packs) from an URL source (HTTP, HTTPS, or FTP). If Setup.exe is started from Microsoft Internet Explorer, Setup detects the URL switch automatically, and the /webinstall option is not required. For example:/webinstall "http://SiteName/Folder/Root of Microsoft Project MSI file"
Note You cannot apply a transform from a URL source. However, if you specify a transform on a file server, Setup caches the transform locally and applies it to the installation.
Removes the application associated with the specified package. The package must be in the same folder as Setup.exe, or the path must be included on the command line.
Example:/x Prjproe.msi
Note You must specify the same package (MSI file) that was used to install the application originally.
Specifies a property value on the command line. If the value contains spaces, enclose it in quotation marks ("). To specify two or more property-value pairs, separate them with spaces. For example:COMPANYNAME="Your Company's Name" USERNAME="Manager"
Note Only public properties are set on the Setup command line. Public properties are all uppercase, but you do not have to type the property names in uppercase on the command line. Private properties consist of mixed-case letters and are not recognized by Setup on the command line; private properties must be set in the Modify Setup Properties page of the Custom Installation Wizard.
The Setup settings file (Setup.ini) file is divided into sections containing keywords and values. The default name is Setup.ini, but you can specify a different settings file to use by including the /settings Setup command-line option followed by a file you want to substitute for the default settings file.
If a Setup option in Setup.ini is also specified in the transform (MST file), the option specified in Setup.ini overrides the one in the transform. However, if the same option is used in the Setup command line, the command-line option overrides those defined elsewhere.
A wizard supplied with the Microsoft Project Resource Kit can modify the Setup.ini file. Use the Setup INI Customization Wizard to easily add or modify content in the Setup.ini file. It is recommended you use the Setup INI Customization Wizard to make changes to your Setup.ini file and if required, make any further modifications by using a text editor.
Specifies the file name of the Windows Installer package (MSI file) to use during the install. This option is not necessary if there is only one MSI file in the folder. This setting is the same as the /i command-line option in Setup. If the /i command-line option is used, it overrides the file specified in this section.
This section can only have one key, MSI, which defines the MSI file name. For example:
[MSI]
MSI=Prjproe.msiYou do not need to specify a path to the Windows Installer package (MSI file) if it is in the same directory as Setup.exe. However, if the MSI file is on a network server and you include a path to it in the MSI key, Windows Installer assumes the path is to an administrative installation point.
Lists product information, including the Windows Installer product code, product name, and version. This is used by Setup to determine whether the product is installed. For example:
[Product]
ProductCode=<{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}>
ProductName=Microsoft Project Professional 2002
Version=10.0Specifies the file name and path of the transform (MST file) to apply for the install. This is the same as using the TRANSFORMS=file Setup command-line option. If the command-line option is used, it overrides the file specified in this section. There is usually only one key used in this section, MST1, which defines the transform file name and the path to use with Setup. The path is not needed if the transform is in the same folders as the Windows Installer package (MSI file). For example:
[MST]
MST1=\\marketing\enterprise\software\my transform.mstDefines Setup properties. The format of the keys in this section is the same as the format used for Setup command-line properties. The keys in this section take the form of property=value. For example:
[Options]
REBOOT=Suppress
COMPANYNAME=Your Company
DONOTMIGRATEUSERSETTINGS=1Note Only public properties are set on the Setup command line. Public properties are all uppercase, but you do not have to type the property names in uppercase on the command line. Private properties consist of mixed-case letters and are not recognized by Setup on the command line; private properties must be set in the Modify Setup Properties page of the Custom Installation Wizard.
The [Display] section allows for setting the degree of user interface presented to a user during installation. This section uses the following keys:
[Display]
Display=None[Display]
Display=Basic
CompletionNotice=YesUsed to create two log files for recording installation actions performed by Setup.exe and Windows Installer. This section can use three keys to define the file name, path, and options for the log files: Path, Template, and Type. For example:
[Logging]
Path=%TEMP%
Template=Microsoft Project Professional 2002 Setup(*).txt
Type=piwaePath=%TEMP%\Project LogsNote %TEMP% is the default value.
Template=Project_%UserName%(*).txtIn this example, the template is used to create two files for a user named John in the folder specified by Path:Project_John(0001).txt
Project_John(0001)_Task(0001).txtType=ipmcuewar+The valid option values are:
| Parameter | Definition |
|---|---|
| a | Start of action notification |
| c | Initial UI parameters |
| e | Error messages, including those possibly causing the installer to terminate |
| i | Information-only messages |
| m | Out-of-memory messages |
| p | Property table list |
| r | User request messages |
| u | Rewrite all required HKEY_CURRENT_USER registry entries |
| v | verbose, including debug messages |
| w | Warning messages), * (turns on all options except v), and + (appends to the log file if it already exists) |
Used to specify the necessary levels of Windows Installer required to use this INI file. Includes the minimum version and the path to the installer install executables. For example:
[Installer]
Version=1.1
Path= .\Update\MSI\Conditional data used to instruct when a message should be presented by Windows Installer to the installer when they are running on a Windows platform that will not support the product without a service pack update of a minimum level. For example:
[ServicePack]
NTVersion=4
SPLevel=1536Used to set the default and alternate fonts for use by Setup.exe and Windows Installer. For example:
[InstallFontold]
Font=Tahoma (TrueType)
FontAlt=Tahoma (TrueType)
FontAlt2=Tahoma
Version=Version 2.30
Path=Files\Windows\Fonts\Tahoma.TTF
Force=NoUsed to set the default and alternate bold face fonts for use by Setup.exe and Windows Installer. For example:
[InstallFontBold]
Font=Tahoma Bold (TrueType)
FontAlt=Tahoma Bold (TrueType)
FontAlt2=Tahoma
Version=Version 2.30
Path=Files\Windows\Fonts\TahomaBD.TTF
Force=NoUsed to set when Windows Installer is installed to a user's computer that would not normally require installing Windows Installer or updating it. The valid option values are: 0 (suppresses an install of Windows Installer) and 2 (the default option that forces an install or upgrade of Windows Installer). For example:
[InstallMSI]
InstMSI=2Settings specific to the System Files Update (OSP.msi). It includes the relative path to the system pack or MSI file and any transforms to apply. For example:
[SystemPack]
Path=\files\osp\1033\osp.msi
Base=\files\osp\
Lcid=<LCID>
MSI=[<path>\}<MSI filename>
Display=[None | Basic | Reduced | Full]Public property settings to pass the system pack setup process. For example:
[SystemPackOptions]
NOIE=True
TRANSFORMS=customosp.mstChecks the files in the provided list and compares them against those present on the existing system. For example:
[SystemPack_DetectionFileList]
<file> <directory> <version>Microsoft Project Setup and Windows Installer use properties to control the Microsoft Project installation process. You can set properties on the command line, in the Setup settings file (Setup.ini), or on the Modify Setup Properties page of the Custom Installation Wizard.
The following properties are used by Setup to customize how Microsoft Project is installed.
ALLUSERS=[string]
Install Microsoft Project for all users of the computer or only for the current user (Microsoft Windows NT 4.0 or later). By default, Windows Installer installs Microsoft Project for all users of the computer. Setting ALLUSERS to a null value ("") overrides this default behavior and installs Microsoft Project per user. For example:ALLUSERS="2"
Values include the following:
| Option | Description |
|---|---|
| 1 | Install Microsoft Project for all users of the computer; requires administrative privileges. |
| 2 | Install Microsoft Project for all users of the computer; default value for Microsoft Project. |
| "" | Install Microsoft Project only for the user running Setup. |
Note Because only an administrator can install Microsoft Project, Setup terminates if the user does not have administrative privileges. For Microsoft Project, setting ALLUSERS to 1 has the same effect as setting it to 2.
ARPCOMMENTS=[string]
Displays additional text in Add/Remove Programs (Control Panel) when a user selects Microsoft Project (Windows 2000 and Windows XP). Limited to 255 characters, not all of which may be displayed. For example:ARPCOMMENTS="Project management application."
ARPCONTACTS=[string]
Displays a list of support contacts in Add/Remove Programs (Control Panel) when a user selects Microsoft Project (Windows 2000 and Windows XP). Limited to 255 characters. For example:ARPCONTACTS="For assistance with Microsoft Project, contact Help Desk."
ARPHELPLINK=[string]
Displays a link to a Web site in Add/Remove Programs (Control Panel) when a user selects Microsoft Project (Windows 2000 and Windows XP). Limited to 255 characters. For example: ARPHELPLINK="http://MyWebServer/LocalHelp"
ARPHELPTELEPHONE=[string]
Displays a Help desk telephone number in Add/Remove Programs (Control Panel) when a user selects Microsoft Project (Windows 2000 and Windows XP). Limited to 255 characters. For example: ARPHELPTELEPHONE="Ext. 1000"
ARPNOMODIFY=[Boolean]
Prevents users from modifying the Microsoft Project configuration through Add/Remove Programs (Control Panel); makes the Change button unavailable (Windows 2000 and Windows XP). For example:ARPNOMODIFY=1
Note When the ARPNOMODIFY property is set, users can still run Microsoft Project setup in maintenance mode from the command line.
ARPNOREMOVE=[Boolean]
Prevents users from removing Microsoft Project through Add/Remove Programs (Control Panel); makes the Remove button unavailable (Windows 2000 and Windows XP). For example:ARPNOREMOVE=1
Note When the ARPNOREMOVE property is set, users can still run Microsoft Project setup in maintenance mode from the command line.
ARPNOREPAIR=[Boolean]
Prevents users from repairing Microsoft Project through Add/Remove Programs (Control Panel); makes the Repair button in the Support Info dialog box unavailable (Windows 2000 and Windows XP). For example:ARPNOREPAIR=1
CIWEXTRASHORTCUTSDIRS=[string]
Searches additional locations for custom shortcuts to remove when Microsoft Project is removed (in addition to the folders that Setup searches by default). Enter an absolute folder path or a subfolder relative to a predefined folder. Separate multiple entries with a semicolon (;). For example: CIWEXTRASHORTCUTSDIRS="<StartMenu\Programs>\CorpApps;C:\Office\Tools"
COMPANYNAME=[string]
Specifies an organization name, which appears in the About box (Help menu) and on the banner page of Microsoft Project applications. For example:COMPANYNAME="My Business"
Note If you enter an organization name on the Specify Default Path and Organization page of the Custom Installation Wizard, that setting takes precedence over the COMPANYNAME property set on the Modify Setup Properties page of the wizard, in the [Options] section of Setup.ini, or on the command line.
DISABLEREMOVEPREVIOUS=[Boolean]
Does not display the Remove previous Versions page during Setup. For example:DISABLEREMOVEPREVIOUS=1
DISABLEROLLBACK=[Boolean]
Disables the rollback feature of Windows Installer. For example:DISABLEROLLBACK=1
DISABLESMIGRATION=[Boolean]
Retains custom shortcuts created for previous versions of Microsoft Project. For example:DISABLESMIGRATION=1
DONOTMIGRATEUSERSETTINGS=[Boolean]
Does not copy the user's application settings when upgrading from a previous version of Microsoft Project. If you apply a transform that includes an OPS file, the DONOTMIGRATEUSERSETTINGS property is set by default; otherwise, the property is not set by default. For example:DONOTMIGRATEUSERSETTINGS=1
Note Setting the DONOTMIGRATEUSERSETTINGS property is equivalent to clearing the Migrate user settings check box on the Customize Default Application Settings page of the Custom Installation Wizard.
DONOTUSECIWORGNAME=[Boolean]
Ignores the organization name specified on the Specify Default Path and Organization page of the Custom Installation Wizard. To override the organization name specified in a transform, use the DONOTUSECIWORGNAME property with the COMPANYNAME property on the command line. For example:DONOTUSECIWORGNAME=1 COMPANYNAME="Your Company"
ENTERPRISE_IMAGE=[Boolean]
Does not create a digital license identification based on the computer used to create a hard-disk image. Instead, Setup creates a unique digital license identification after the hard-disk image is copied to a new computer and the user starts Microsoft Project. For example:ENTERPRISE_IMAGE=1 NOUSERNAME=1
INSTALLLOCATION=[string]
Specifies the installation location for Microsoft Project. On the Setup command line or in the Setup settings file (Setup.ini), you must use an absolute path. On the Specify Default Path and Organization page or Modify Setup Properties page of the Custom Installation Wizard, you can specify a path relative to a predefined folder. A value set on the command line or in Setup.ini overrides the value set in a transform. For example:INSTALLLOCATION="C:\Program Files\MyApp"
Note Unlike previous versions, Microsoft Project is installed in a version-specific folder. If you choose to keep a previous version of Microsoft Project on the computer, you can specify the same location without overwriting any files.
LIMITUI=[Boolean]
Disables Interactive Setup user interface; equivalent to using the /qb command-line option or setting the Display property to Basic in the Setup settings file. When the LIMITUI property is set, Setup ignores the /qf and /qr command-line options and the Display=Full and Display=Reduced property settings. For example:LIMITUI=1 ARPNOMODIFY=1
Setting the LIMITUI property on the Modify Setup Properties page of the Custom Installation Wizard does not affect the initial installation; however, it disables the Setup user interface only when Setup runs in maintenance mode after the initial installation.
Tip You can use the LIMITUI and ARPNOMODIFY properties together to prevent users from running Setup after Microsoft Project has been installed, or to prevent users from making changes to the installation.
NOFEATURESTATEMIGRATION=[Boolean]
Disables default feature installation state migration for the Microsoft Project package. When you upgrade to Microsoft Project, Setup detects and matches feature installation states from the previous version. Setting the NOFEATURESTATEMIGRATION property overrides this default behavior. For example:NOFEATURESTATEMIGRATION=1
Note You can also override default installation state migration on a per-feature basis on the Set Feature Installation States page of the Custom Installation Wizard.
NOUSERNAME=[Boolean]
Prevents Setup from defining a user name during a quiet installation. Setting the NOUSERNAME property allows users to enter their own user names the first time they run Microsoft Project. Set this property when you install Microsoft Project on a computer from which you plan to create a hard-disk image. For example:NOUSERNAME=1
OPCREMOVAL=[string]
Prevents Setup from removing previous versions of Microsoft Project during
the installation or performing any other clean-up tasks. To turn default removal behavior back on, you must set OPCREMOVAL to On. Any other value turns the property off, as shown in the following examples:OPCREMOVAL=OffOPCREMOVAL=0
Note Turning off the OPCREMOVAL property is not the same as selecting the option Remove the following versions of Microsoft Office applications on the Remove Previous Versions page of the Custom Installation Wizard and then clearing all the check boxes. Even with all the check boxes cleared, Setup performs some general cleanup operations. If this property is turned off, however, Setup does not perform any cleanup.
PIDKEY=[string]
Enters a 25-character product identification key on the Setup command line or in the Setup settings file. When you set the PIDKEY property, users are not required to enter a product key when they install Microsoft Project. For example:PIDKEY="12345ABCDE12345ABCDE12345"
SOURCELIST=[string]
Specifies additional network servers to use when the primary Microsoft Project administrative installation
point is unavailable; equivalent to the list specified on the Identify Additional Servers page of the Custom Installation Wizard. For example:SOURCELIST="\\backup1\Project;\\backup2\Project"
After Microsoft Project is installed, Windows Installer continues to reference the administrative installation point for installing on demand, repairing features, or running Setup in maintenance mode. Copying the original administrative image to backup servers helps ensure that users always have access to a network source.
Note Separate a list of server shares with semicolons. Use a drive letter only if the drive is part of a standard drive scheme used throughout the organization.
TARGETDIR=[string]
Specifies the location where the Microsoft Project package is copied during an administrative installation; used only when running Setup with the /a command-line option. For example:TARGETDIR="\\server\share\Project"
TRANSFORMS=[string]
Specifies a transform to apply to the installation; use only on the Setup command line. The TRANSFORMS property is equivalent to the Transform (MST file) to apply during installation option in the Setup INI Custom Installation Wizard. The value can be a path relative to the folder that contains Setup.exe, an absolute path, or an environment variable. For example:TRANSFORMS="\\server\share\ProjectCustom.mst"
You cannot use the TRANSFORMS property in the Setup settings file to specify a transform for the Microsoft Project package or any chained packages. However, you can use the TRANSFORMS property in the [SystemPackOptions] section of Setup.ini to specify a transform to apply to the System Files Update package.
Note If you misspell the TRANSFORMS property on the command line as TRANSFORM (singular), Setup automatically corrects it during the call to the Windows Installer. However, if you enter TRANSFORM in the [SystemPackOptions] section of Setup.ini, the incorrect option is passed to the Windows Installer and your transform is not applied. You can avoid this error by using the Setup INI Customization Wizard to specify a transform for the System Files Update.
TRANSFORMSSECURE=[Boolean]
Caches the transform on the local computer in a location where the user does not have write access, and applies the transform only if the MST file is located at the root of the administrative installation point (that is, in the same folder as the MSI file). The TRANSFORMSSECURE property applies to the package regardless of the user; it provides secure transform storage for traveling users under Windows 2000 and Windows XP. For example:TRANSFORMSSECURE=1
USERNAME=[string]
Specifies a default user name, which appears in the About box (Help menu) and on the banner page of Microsoft Project. The name is also used in Microsoft Project documents to identify the author or the source of revision marks and comments. For example:USERNAME="Don Funk"
The following properties are used by Setup to change text and button labels in the Setup user interface. These properties allow you to customize the Choose the type of installation you need page of Setup if you need to provide a different description of the installation choices to your users.
Note In the English language version of Setup, the button labels are &Install Now, C&ustomize, &Help, &Back, and &Next. Take care in choosing an accelerator character (preceded by an "&") and make sure it does not conflict with accelerator characters already in use in the dialog. To select an option in the dialog box that has an accelerator character, press down both the shortcut key and the ALT key.
COMPLETEINSTALLDESCRIPTION=[string]
Customizes the text displayed by Setup to describe the Complete installation option. The following example shows the default value in the English version of Microsoft Project. For example:COMPLETEINSTALLDESCRIPTION="Install all of Microsoft Project on your computer, including all optional components and tools."
CUSTOMINSTALLDESCRIPTION=[string]
Customizes the text displayed by Setup to describe the Custom installation option. The following example shows the default value in the English version of Microsoft Project. For example:CUSTOMINSTALLDESCRIPTION="Customize your Microsoft Project installation, selecting which Microsoft Project features to install on your computer."
DEFAULTREMOVECHOICEDESCRIPTION=[string]
Customizes the text displayed by Setup to describe the Remove previous versions option. The following example shows the default value in the English version of Microsoft Project. For example:DEFAULTREMOVECHOICEDESCRIPTION="Choose whether to keep or remove previous versions of Microsoft Project."
Note If you use this property, you will need to add a space to the beginning of your string because this string is appended to the end of existing text.
ERRORSUPPORTEXT_ADMIN_DEFAULT=[string]
Customizes the error message displayed by Setup during installation of Microsoft Project. The following example shows the default value in the English version of Microsoft Project. For example:ERRORSUPPORTEXT_ADMIN_DEFAULT="Contact your Information Technology department for assistance.
ERRORSUPPORTEXT_ADMIN_DEFAULT_PERMISSION=[string]
Customizes the error message displayed by Setup during installation of Microsoft Project. The following example shows the default value in the English version of Microsoft Project. For example:ERRORSUPPORTEXT_ADMIN_DEFAULT_PERMISSION="Verify that you have sufficient permissions to access the registry or contact your Information Technology department for assistance."
ERRORSUPPORTEXT_ADMIN_DEFAULT_PROBLEM=[string]
Customizes the error message displayed by Setup during installation of Microsoft Project. The following example shows the default value in the English version of Microsoft Project. For example:ERRORSUPPORTEXT_ADMIN_DEFAULT_PROBLEM="If problem persists, contact your Information Technology department for assistance."
NOCANCEL=[Boolean]
Removes the Cancel button from all dialog boxes displayed during Setup. For example:NOCANCEL=1
RUNFROMSOURCEINSTALLDESCRIPTION=[string]
Customizes the text displayed by Setup to describe the Run from Network option. The following example shows the default value in the English version of Microsoft Project. For example:RUNFROMSOURCEINSTALLDESCRIPTION="Installs only the files that must be copied to your computer. Access to the installation source will be required to run Microsoft Project."
RUNFROMSOURCETEXT=[string]
Customizes the text displayed by Setup to describe the Run from Source option. The following example shows the default value in the English version of Microsoft Project. For example:RUNFROMSOURCETEXT="Run from N&etwork."
Note The ampersand (&) indicates which character in the string is to be used as the shortcut key for the button. Pressing down both the shortcut key and the ALT key selects the option.
SETUPDW=[string]
Sets or disables Setup error reporting (DW.exe). Set the SETUPDW property to 0 to prevent DW.exe from reporting installation errors to Microsoft; set it to 1 to collect information about Setup failures and send the data to Microsoft. This property affects only Setup error reporting and has no effect on application crash reporting. For example:SETUPDW=0
Note The SETUPDW property is set to 0 by default when you create an administrative installation point.
SKIPREMOVEPREVIOUSDIALOG=[string]
Does not display the Remove Previous Versions dialog box during Setup. The Custom Installation Wizard sets this property to 1 when you select the Remove the following versions of Microsoft Project applications option on the Remove Previous Versions page of the Custom Installation Wizard.
SUPPORTERRORSTRING=[string]
Adds text to the error message box directing users to an internal support organization.
TYPICALINSTALLDESCRIPTION=[string]
Customizes the text displayed by Setup to describe the Typical installation option. The following example shows the default value in the English version of Microsoft Project:TYPICALINSTALLATIONDESCRIPTION="Installs Microsoft Project with the default settings, including the most commonly used components."
TYPICALINSTALLTEXT=[string]
Customizes the text displayed by Setup for the Typical installation option button. The following example shows the default value in the English version of Microsoft Project. For example:TYPICALINSTALLTEXT="&Install Now"
Note The ampersand (&) indicates which character in the string is to be used as the shortcut key for the button. Pressing down both the shortcut key and the ALT key selects the option.
TYPICALUPGRADEDESCRIPTION=[string]
Customizes the text displayed by Setup to describe the Typical installation option when the user is upgrading from a previous version of Microsoft Project. The following example shows the default value in the English version of Microsoft Project:TYPICALUPGRADEDESCRIPTION="Upgrades your Microsoft Project installation. Setup will remove your previous versions and install the new version based on your current
configuration."
TYPICALUPGRADETEXT=[string]
Customizes the text displayed by Setup for the Typical installation option button when the user is upgrading from a previous version of Microsoft Project. The following example shows the default value in the English version of Microsoft Project:TYPICALUPGRADETEXT="U&pgrade Now"
Note The ampersand (&) indicates which character in the string is to be used as the shortcut key for the button. Pressing down both the shortcut key and the ALT key selects the option.
You can use the following properties either prior to or after installing an application to change the installation state of individual features or of the entire application. Each of these properties takes a list of feature names, separated by commas. The feature names you must use are unique strings that are defined in the MSI file for the application. These feature names correspond to the features shown in Setup and in the Set Feature Installation States page of the Custom Installation Wizard.
Note The following list of properties should only be used with either the Setup.ini file or on the command line. Do not enter these in the Modify Setup Properties page of the Custom Installation Wizard.
The following feature names are unique to Microsoft Project:
In addition to these unique Microsoft Project feature names, some Microsoft Office feature names can be used with Microsoft Project. For more information about Microsoft Office feature names, see the Microsoft Office Resource Kit.
ADDDEFAULT=[string]
Returns a set of features to their default installation states, as defined in the original Windows Installer package (MSI file) and transform (MST file). You can specify all, or you can specify a list of feature names separated by commas. For example:ADDDEFAULT=allADDDEFAULT="ProjectHelpFiles"
Note If a feature is advertised by default in the Windows Installer package, the ADDDEFAULT property sets the feature to the same state as when the user activated the feature for the first time.
Use the ADDDEFAULT property only during initial installation or if you want to return all features to their default states before using the ADDLOCAL, ADDSOURCE, or ADVERTISE properties.
ADDLOCAL=[string]
Installs a set of features to run from the user's computer. You can specify all, or you can specify a list of feature names separated by commas. For example:ADDLOCAL=allADDLOCAL="ProjectTemplates"
ADDSOURCE=[string]
Installs a set of features to run from the network server. You can specify all, or you can specify a list of feature names separated by commas. For example:ADDSOURCE=allADDSOURCE="ProjectHelpFiles"
ADVERTISE=[string]
Advertises a set of features on the user's computer. In this state, features are installed the first time a user attempts to use them. You can specify all, or you can specify a list of feature names separated by commas. For example:ADVERTISE=allADVERTISE="ProjectTemplates"
REMOVE=[string]
Removes a set of features from a user's computer. If you specify all, the entire product is removed. You can also specify a list of feature names separated by commas. For example:REMOVE=allREMOVE="ProjectHelpFiles"
The minimum version of Internet Explorer required by Microsoft Project is Internet Explorer 5 or later. By default, the System Files Update includes a typical installation of Internet Explorer version 5.01. Under Windows NT 4.0 and Windows 98, any earlier version of Internet Explorer automatically triggers the System Files Update installation.
The following properties are used by Microsoft Project Setup to instruct Internet Explorer 5.01 Setup how to customize and install Internet Explorer during Microsoft Project installation.
IESETUPLOCATION=[string]
Contains the file path of Internet Explorer 5.01 Setup. If this property is a relative path, it is relative to the folder containing the Windows Installer package (MSI file). This allows duplication of the administrative installation point to another server and a valid path to the Internet Explorer 5.01 setup directory.
The default value is a relative path to Ie5setup.exe in the administrative installation point:
.\IE5\language\IE5SETUP.EXE
This property corresponds to the file name and path of Internet Explorer 5 Setup box in the Customize Internet Explorer 5 Installation Options page. The value must end with the file reference IE5SETUP.exe.
For example:
IESETUPLOCATION=".\IE5\EN\IE5SETUP.EXE"
InstallDesktopUpdate=[string]
Possible selections are:
This private property can only be set in the Modify Setup Properties page of the Custom Installation Wizard. This is displayed when you are creating a transform for the OSP.msi.
Adding the Windows Desktop Update only applies to Windows NT 4.0 systems, where shell support for Windows Installer Shortcuts is not already installed. The minimum requirement for this support is Internet Explorer 4.01 SP1, with Active Desktop installed.
NOIE=[string]
Directs Internet Explorer 5.01 Setup not to upgrade a computer to Internet Explorer 5.01 during Microsoft Project Setup. This is the same action Setup performs if a user chooses not to install Internet Explorer 5.01 during a Microsoft Project Setup without using a transform. By default, this property is set to TRUE if you select the Do not install Internet Explorer 5 option in the Customize Internet Explorer 5 Installation Options page. This property is set to FALSE if the Upgrade to Internet Explorer 5 option is selected.
For example:
NOIE="FALSE"
SKIPIEDIALOG=[string]
Hides the Internet Explorer 5.01 installation page of Microsoft Project Setup if set to True. By default the property is not set. This property corresponds to the Do not prompt the user to install Internet Explorer 5 during Microsoft Project Setup check box in the Customize Internet Explorer 5 Installation Options page.
For example:
SKIPIEDIALOG=True