After you create an administrative installation point or compressed CD image on the network and you customize Microsoft® Office 2003, you can distribute Office from this source in a number of ways. Users can run Setup.exe using the command-line options, Setup settings file, or transform that you specify. You can copy the image onto a CD and distribute the physical media to users. Or you can use other deployment tools, such as Microsoft Systems Management Server or hard disk imaging, to deploy a customized configuration of Office from the source.
The tools and procedures for customizing Office are largely the same whether you are deploying from an administrative image or a compressed CD image. After Office is deployed to users, however, each type of installation image offers some unique advantages.
For example, installing Office from a compressed CD image allows Setup to create a local installation source on users' computers, which offers the following benefits after the initial deployment:
- Users have a reliable resiliency source on the local computer for operations such as installing features on demand, repairing, reinstalling, and updating Office.
- Administrators can copy the compressed CD image onto physical media to distribute to users who do not have network access. They do not need to customize both an administrative image and a CD image.
- Administrators can distribute binary (client) patches to update Office installations and leave the original installation image on the network at a baseline level.
In some organizations, however, installing from an administrative image may be more efficient. For example:
- Organizations that use custom tools that bypass Office Setup or that rely on the Windows Installer source list should deploy from an administrative image. When users install from a compressed image, creation and maintenance of the local installation source is managed entirely by Setup and the Office Source Engine (Ose.exe) – and not by Windows Installer.
- Organizations that use Group Policy software installation, advertise Office applications, or run any Office applications from the network must install from an administrative image. A compressed CD image does not support these installation options.
- Users with limited hard disk space may not be able to install Office with a local installation source. Setup requires as much as 2 GB of free hard disk space during the installation or the process may fail. After the installation, the local installation source requires approximately 240 MB of hard disk space in addition to what is required by Office.
For more information about create a local installation source on users' computers, see Taking Advantage of a Local Installation Source.
For more information about deploying from an administrative image, see Creating an Administrative Installation Point.
When users double-click setup.exe on the installation image, Setup runs with no command-line options. To apply your customizations, users must run Setup.exe with the appropriate command-line options. For example, the command line can include the /settings option to specify a custom Setup settings file or the TRANSFORMS property to specify a transform (MST file).
To help ensure that Office 2003 is installed with the correct customizations, you can create and distribute a batch file that runs Setup.exe with your command-line options. Or you can create a Microsoft Windows® shortcut and add options to the command-line box. In many organizations, the most efficient method is to create a log-in script that runs Office Setup.
Unless you choose to install Office 2003 in quiet mode, the Setup user interface guides users through the following steps to install Office on their computers:
- Enter user information
- Select installation type and location
- Select installation options for Office features
- Select previous versions of Office to keep
- Choose whether to keep the local installation source (only when deploying from a compressed CD image)
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 help prevent users from changing the configuration during the installation, run Setup in quiet mode.
For more information about command-line options that you can use to customize the Office 2003 installation, see "Setup Command-line Options" in the Office 2003 Editions Resource Kit Reference.
For information about installing Office 2003 quietly, see Customizing How Setup Runs.
Enter user information
User information appears on users' computers in the About box (Help menu) in Office applications. When a user installs Office from an administrative installation point, Setup uses the organization name you specify without prompting the user.
Because you must enter the 25-character Volume License Key when you create an administrative installation point, users are not prompted for a product key when they run Setup from an administrative image, nor are they required to activate the product. In addition, the referral code field is not displayed when users run Setup to install Office 2003.
If you deploy Office from a compressed CD image, you can use new functionality in the Custom Installation Wizard to create a transform in which you enter a Volume License Key on behalf of users. When you apply the transform, Setup does not prompt users for a product key. For more information, see the Help for the Configure Local Installation Source page in the Custom Installation Wizard.
Accept end-user license agreement
When users install Office 2003 from the CD, Setup displays an end-user license agreement page. When users install Office from the administrative installation point, however, the license agreement that you accepted when you created the administrative installation point applies, and users do not see this page of Setup.
If you deploy Office from a compressed CD image, new functionality in the Custom Installation Wizard also allows you to accept the EULA on behalf of users. When you apply the transform, users do not see this page of Setup. For more information, see the Help for the Configure Local Installation Source page in the Custom Installation Wizard.
Select installation type 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.
Users can select one of the following installation types:
Automatically upgrades to Office 2003 and skips the remaining pages of Setup. This option removes all previous versions of Office applications and installs Office 2003 features based on the user's current configuration. This option is available only if a previous version of Office is installed on the computer.
Automatically installs the most frequently used Office features in the default installation location and skips the remaining pages of Setup.
Installs only required components of Office 2003. Additional components are configured for installation on first use and will require a connection to the installation source. This option is designed for installing on computers with limited hard disk space or when installing over limited bandwidth.
Allows the user to configure all aspects of the Office installation on the remaining pages of Setup.
Installs all Office features locally on the user's computer. This option requires the most disk space but ensures that users do not need access to the Office 2003 CD or an administrative installation point to install additional components later.
Installs all Office 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 any Office application.
Note When you deploy Office from a CD or compressed CD image, the Run from Network installation type is not available.
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 Upgrade or Typical Install. You can also change the button labels and descriptive text on this page by setting the following properties:
For more information about properties you can set to customize the Setup user interface, see "Setup Properties" in the Office 2003 Editions Resource Kit Reference.
For more information about customizing the Setup behavior, see Customizing How Setup Runs.
Users can also enter the path to the installation location they want. The default location is Program Files\Microsoft Office\Office11.
You can specify a custom default value for the installation location on the Specify Default Path and Organization page of the 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 Office features
When users choose the Custom installation mode, Setup displays a list of all the applications included in the edition of Office that they are installing. Users select the check boxes next to the applications they want, and Setup installs a typical set of features for each one.
Alternatively, users can select Choose advanced customization of applications to further customize their Office 2003 configuration. In this case, Setup displays the Office 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:
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.
Same as Run from My Computer, except that all child features belonging to the feature are also set to this state.
Setup leaves components for the feature on the administrative installation point, and the feature is run from there. Available only when you are deploying from an administrative image.
Same as Run from Network, except that all child features belonging to the feature are also set to this state. Available only when you are deploying from an administrative image.
Setup leaves components for the feature and all its child features on the administrative installation point until the user attempts to use the feature for the first time, at which time the components are automatically copied to the local hard disk.
The components for the feature, and all of the child features belonging to this feature, are not installed on the computer.
For more information about customizing what users see in the feature tree, see Customizing Office Features and Shortcuts.
For more information about setting installation states in a transform, see the Help for the Set Feature Installation States page in the Custom Installation Wizard.
Select previous versions of Office to keep
If the user is upgrading from a previous version of Office, Setup displays a list of all the Office applications currently installed — applications that Setup removes when it installs Office 2003. Users can choose to keep all or some previous-version applications on the computer.
Because Office 2003 is always installed in a version-specific folder, users can choose to keep previous versions without overwriting any files. However, Setup does redefine system settings, such as file types and shortcuts, to point to the Office 2003 applications.
On the Remove Previous Versions page of the Custom Installation Wizard, you can specify custom default settings for this Setup page. The wizard also includes an option to remove obsolete files, shortcuts, and registry settings left over from previous versions. When you customize removal options in the Custom Installation Wizard, the SKIPREMOVEPREVIOUSDIALOG property is automatically set to 1, which hides this page from users during interactive Setup.
Note You cannot install more than one version of Microsoft Outlook® on the same computer. If you are installing Microsoft Office Outlook 2003, then you must remove all previous versions of Outlook.
Delete the local installation source
When you install Office from a compressed CD image, Setup displays an additional page. On this page, users are given the options to check the Web for Office product updates and to delete the local installation source. To help ensure that users retain the local installation source, set the PURGE property to 0 in the [Cache] section of Setup.ini. When the PURGE property is set to 0, users do not see this page of Setup.
Advertising is a quick and efficient means of making Office 2003 available to users without actually installing it until they need it. If you want users to install the Office 2003 package on demand, you must create an administrative installation point. You cannot advertise Office applications from a compressed CD image.
After you create the administrative image, you log on as an administrator and run Setup with the /jm option. If you also include a Windows Installer transform (MST file) to customize the installation, you use the /t command-line option to specify the MST file. For example:
setup.exe /jm pro11.msi /t office.mst
Note When you use the /t command-line option to specify a transform, you must insert a space between the option and the transform name to help ensure that the transform is correctly applied.
When you advertise Office 2003 in this way, Windows Installer shortcuts for each application appear on the Start menu, and a minimal set of core Office files and components is installed on the computer. When a user clicks a shortcut or opens a file associated with an Office application, Windows Installer installs the feature or application from the administrative installation point. After Office is advertised, users can also run Setup directly from an administrative installation point to install Office. Because Office was advertised by an administrator, Windows Installer handles elevation of privileges for users.
Like core Office 2003, the language packs in the Microsoft Office 2003 Multilingual User Interface Pack are Windows Installer packages, and can also be advertised on users' computers. For more information, see Customizing and Installing Office 2003 MUI Packs.
If you have an Active Directory® directory service structure set up in your organization, you can use Group Policy software installation to deploy and manage Office. Because Group Policy bypasses Office Setup and deploys the MSI file directly, however, you cannot take advantage of a local installation source when you deploy from a compressed image. For more information, see Using Group Policy to Deploy Office.
If you use Microsoft Systems Management Server to distribute Office 2003 to users' computers, you also begin by creating an Office 2003 administrative installation point or compressed CD image on the network. For more information, see Using Microsoft Systems Management Server to Deploy Office.
When you create a hard disk image, you first create an administrative installation point or compressed CD image for Office 2003 and then you customize the installation image. For more information, see Creating a Hard Disk Image.