Installing Outlook 2003 Before Office 2003 | Microsoft Office 2003 Editions Resource Kit (Pro-Resource Kit)

Microsoft Office Outlook 2003 is designed to provide the best supported experience when it is installed together with Microsoft Office 2003. However, in some cases your organization might benefit from deploying Outlook and Office in stages—for example, deploying Outlook first, then deploying Office later.

This section of the chapter discusses several options for installing Outlook before Office and includes specific procedures for doing so.

Note

Installing Outlook before Office is one example of staging the deployment of an Office application; the methods described here can be used to install any Office application before installing the rest of Office. You can also install any Office application after an installation of the rest of Office. For more information about staging your deployment in this way, see “Installing Outlook 2003 After Office 2003” later in this chapter.

When you install Outlook 2003 over the network by using an administrative installation point, you can use one of the following methods to install Outlook before you install Office 2003:

Install the stand-alone version of Outlook 2003 from the same or a different administrative installation point from which you plan to install Office.
Run Office Setup from an Office CD to install only Outlook 2003, then use the Custom Maintenance Wizard to install the rest of Office when you are ready.

Note

Outlook 2003 cannot coexist with previous versions of Outlook. If you choose to keep previous versions, do not install Outlook 2003.

Installing a stand-alone version of Outlook before Office

One way to install Outlook 2003 before Office 2003 is to first install the stand-alone version of Outlook from a CD, then use the Office 2003 CD to install the rest of Office. With this method, you can also select whether to use one administrative installation point for both Outlook and Office, or separate installation points for each package.

Choose whether to use one or more administrative installation points

When you deploy the stand-alone version of Outlook, you can create two administrative installation points—one for Outlook, and one for the rest of Office—or you can use one administrative installation point for both packages. Each scenario has its benefits, depending on your deployment needs.

You might choose to use separate installation points, for example, if two different groups in your organization will be deploying Office and Outlook, respectively. In this scenario, you use the Office 2003 CD plus a stand-alone copy of Outlook 2003.

The separate administrative installation points can be in different folders on one network server, or they can be on separate servers. Users install Outlook from one administrative installation point, and install the rest of Office later from the second administrative installation point. In this scenario, files that are common among all Office applications are duplicated on each administrative installation point.

Another method for deploying Outlook before Office is to create a single administrative installation point that includes both Outlook and Office. You create the initial administrative installation point by running Setup with the /a command-line option from the stand-alone Outlook version. Then you install the rest of Office from the Office 2003 CD into the same folder structure.

Using one administrative installation point for both packages saves hard disk space because files that are common among all Office applications are shared on the single administrative installation point. Because Outlook and Office use the same names for their respective Setup files (Setup.exe and Setup.ini), however, you must rename the files to avoid overwriting the unique Outlook and Office versions.

Install the stand-alone version of Outlook

The process for installing Outlook from a stand-alone version includes these steps:

Creating an administrative installation point for the stand-alone version of Outlook.
Customizing your Outlook deployment.
Saving your Outlook customizations in a transform.
Installing the customized version of Outlook on users’ computers.

Note

As part of an initial Outlook customization, you can capture and include settings in an Office profile settings file (OPS file). To do this, you first install Outlook on a test computer and make your changes to the Outlook settings and environment. You then capture your customizations in an OPS file by running the Office Profile Wizard. Finally, you include the OPS file in the Custom Installation Wizard when you create the transform for installing Outlook.

To install the stand-alone Outlook 2003 version

Using the stand-alone Outlook 2003 version, run Setup.exe with the /a command-line option.
When prompted for the server location, enter a unique folder for Outlook on a network server. For example:

\\server1\software\outlook

or

Enter the same folder that you will use for your Office deployment. For example:

\\server1\software\office
Use the Custom Installation Wizard to create a transform that references the Outlook MSI file in the root of the administrative installation point used in step 2, and that specifies the appropriate Outlook configuration for your users.

For example, you can include an OPS file for Outlook (if you created one), specify Outlook settings, and configure user profiles in the Custom Installation Wizard. Save the transform in the same folder as the Setup settings file.
If you are using the same administrative installation point that you will use for your Office deployment, rename the Setup files (Setup.exe and Setup.ini).

Use consistent file names and the appropriate file name extensions; for example, OlkSetup.exe and OlkSetup.ini. (If you created the administrative image from the Microsoft Select CD subscription, the files have already been renamed for you on the CD.)
Edit the Outlook Setup settings file (INI file) to specify the transform that you created.

For example, you might add the following line under the [MST] section:
```
MST1=Outlook.mst
```
You must remove the comment marker (;) from the [MST] header line so that the transform is read correctly.
Instruct users to install Outlook by using Outlook Setup from this administrative installation point.

Install Office after installing Outlook

After you have deployed the stand-alone version of Outlook, you can deploy the rest of Office by using the same or a different administrative installation point. If you use the same administrative installation point as Outlook, then you must make sure that the Outlook Setup files have been renamed so the Office Setup files do not overwrite them. Then you customize your Office deployment, save the customizations in a transform, and instruct users to install the rest of Office 2003 from the Office administrative installation point. For more information about customizing and deploying Office, see Chapter 4, “Customizing Office 2003.”

Note

As part of an initial Office customization, you can capture and include settings in an OPS file. To do this, install Office on a test computer and make your changes to the Office settings and environment. When you capture your customizations by running the Office Profile Wizard and creating an OPS file, be sure to exclude Outlook settings. Then include the OPS file in the Custom Installation Wizard when you create the transform for installing Office.

To install Office after installing stand-alone Outlook

Using an Office 2003 CD, run Setup.exe with the /a command-line option.
When prompted for the server location, enter a folder on the network server. For example:

\\server1\software\office
Use the Custom Installation Wizard to create a transform to customize Office.

As part of your customization, on the Set Feature Installation States page, set Microsoft Outlook for Windows to Not Available, Hidden, Locked. In addition to customizing options for other Office applications, you can optionally fine-tune your Outlook customizations in this transform as well. When you are finished, save the transform in the same folder as the Setup settings file.
To specify this transform when you install Office, edit the Office Setup.ini in a standard text editor (such as Notepad) to add an entry for the Office transform in the [MST1] section. For example:
```
[MST1] MST1=Office.mst
```
Be sure to remove the comment marker (;) from the [MST] header line so that the transform is read correctly.
Instruct users to install Office from the administrative installation point.

Installing Outlook before Office using the Office CD

Another way to stage your deployment of Outlook 2003 and Office 2003 is to install Outlook first from an Office 2003 CD that includes Outlook. Then you use the Custom Maintenance Wizard to configure the rest of Office to be installed after Outlook by changing the installation options configured in the original Office transform. In this case, you use a single administrative installation point for both installations.

Upgrading from an earlier version of Office

If you are upgrading from an earlier version of Office, there are several issues to consider when you install Outlook before Office by using an Office CD. First, if you plan to use the Office Profile Wizard to capture Office settings, you must configure these settings and include the OPS file when creating the Custom Installation Wizard transform to deploy Outlook. (The Custom Maintenance Wizard does not allow you to include an OPS file.)

Also, when you deploy Office 2003 by using the Custom Maintenance Wizard, you limit your options for easily removing earlier versions of other Office applications. When you deploy Outlook 2003 by using the Custom Installation Wizard, you can choose to remove earlier versions of Outlook while leaving other existing Office applications. However, when you deploy Office by using the Custom Maintenance Wizard, you cannot specify to remove older versions of Office applications. However, you can use the Office Removal Wizard to remove files instead. For more information about using the Office Removal Wizard, see “Customizing Removal Behavior” in Chapter 4, “Customizing Office 2003.”

Start by running Setup with the /a option to copy Office files to your administrative installation point. When prompted for the server location, enter a folder on a network server. For example:

\\server1\software\office

Then follow these steps to install Outlook and other Office applications in stages:

Use the Custom Installation Wizard to create a transform that includes your Outlook and Office customizations.
Install Outlook using the transform.
When you want to install the rest of Office, you use the Custom Maintenance Wizard. You can include both Office and Outlook customizations in the second installation.

Using the Office Profile Wizard to capture Outlook settings

As part of an initial Outlook customization, you can capture and include settings in an OPS file. To do this, install Outlook on a test computer, and then make your changes to the Outlook settings and environment. When you capture your customizations in an OPS file by running the Office Profile Wizard, be sure to include only Outlook settings.

Optionally, you can install all of Office on the test computer and capture settings for other Office 2003 applications as well as for Outlook. In this case, capture all customizations when you run the Office Profile Wizard to create an OPS file.

Then include the OPS file in the Custom Installation Wizard when you create the transform for installing Outlook.

To install Outlook by using the Office 2003 CD

Start the Custom Installation Wizard and open the Office 2003 package (MSI file).
On the Remove Previous Versions page, click Remove the following versions of Microsoft Office applications.
In the table of applications, for each Office application except Microsoft Outlook, click the application name, then click Details.
Clear all the check boxes to retain the current versions of the application on users’ computers, then click OK.

Repeat for each application.
On the Set Feature Installation States page, set all Microsoft Office applications in the feature tree to Not Available.
Set the Microsoft Outlook for Windows feature to Run from My Computer.

You can also install shared Office tools, converters, or other features that support your Outlook installation.
Configure any other installation options, then complete the transform.

For example, you can specify Outlook profile information.
To specify this transform when you install Outlook, edit the Office Setup.ini in a standard text editor (such as Notepad) to add an entry for the Office transform in the [MST1] section. For example:
```
[MST1] MST1=Office.mst
```
Be sure to remove the comment marker (;) from the [MST] header line so that the transform is read correctly.
Instruct users to install Outlook by running Setup from this administrative installation point.
Later, use the Custom Maintenance Wizard to install additional Office applications and to modify existing Office installations (including your Outlook installation) throughout your organization after your initial deployment.

Similar to the Custom Installation Wizard, the Custom Maintenance Wizard reads the Office 2003 package (MSI file) and records your changes in a configuration maintenance file (CMW file).

On the Resource Kit CD

The Office 2003 Editions Resource Kit includes the Custom Maintenance Wizard, which is installed by default when you run the Office Resource Kit Setup program. For more information, see “Custom Maintenance Wizard” in Appendix A, “Toolbox.”

Resources and related information

There are a number of considerations when you choose the timing of your Outlook deployment. For more information about the advantages and disadvantages of staging an Outlook installation, see “Determining When to Install Outlook” in Chapter 6, “Planning an Outlook 2003 Deployment.”

The Office Custom Installation Wizard provides a straightforward way to configure and install Outlook 2003. For more information about Outlook configuration choices, see “Customizing Outlook Features and Installation with the Custom Installation Wizard” in Chapter 7, “Deploying Outlook 2003.”