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

Although it is usually simpler to deploy all of Microsoft Office 2003 at once, your organization might benefit from deploying Office and Microsoft Office Outlook 2003 in stages. For example, you might choose to wait to upgrade to Outlook 2003 until after you have installed Office 2003 and have upgraded your messaging server to a new version of Microsoft Exchange Server.

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

Note

Installing Outlook after Office is one example of staging the deployment of an Office application; the methods described here can be used to install any Office application after installing the rest of Office. You can also install any Office application before you install the rest of Office. For more information about staging your deployment in this way, see “Installing Outlook 2003 Before Office 2003” earlier 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 after you install Office:

Run Office Setup (on the Office 2003 CD) to install Office applications except for Outlook, then use the Custom Maintenance Wizard to install Outlook when you are ready.

In this case, you use the same administrative installation point for both Office and Outlook.
Install Office applications by using the Office CD, excluding Outlook. Then install the stand-alone version of Outlook.

In this case, you can choose to install Outlook from its own administrative installation point or from the same administrative installation point used for the Office files.

There are advantages to each of these approaches. Using a stand-alone version of Outlook to install Outlook separately from Office has the advantage of allowing you to remove the previous version of Outlook (for example, Outlook 2002) at deployment. Since you are installing two separate software packages, you can use the Custom Installation Wizard to create two transforms, one for each deployment. In each transform, you specify to remove earlier versions of the applications you are installing.

By contrast, if you deploy Office and then Outlook from the Office CD, you can use a customized transform with only your Office deployment. When you deploy Outlook by using the Custom Maintenance Wizard, you cannot specify to remove older versions of Outlook. You must use the Office Removal Wizard to remove previous versions of Office applications.

Note

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

Installing Outlook after Office using the Office CD

One way to stage your deployment of Outlook 2003 and Office 2003 is to install Office first from an Office 2003 CD and customize your installation to exclude Outlook. Then, later, you change the installation options in the Custom Maintenance Wizard to configure Outlook to be installed as its own package. 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 Office 2003 without Outlook 2003 from the Office 2003 CD. First, if you plan to use the Office Profile Wizard to capture Outlook settings, you must configure these settings and include the Office profile settings file (OPS file) when creating the Custom Installation Wizard transform to deploy Office. The Custom Maintenance Wizard does not allow you to include an OPS file.

Also, when you add Outlook 2003 to your Office 2003 installation by using the Custom Maintenance Wizard, you cannot specify in the wizard to remove earlier versions of Outlook. When you deploy Office 2003 by using the Custom Installation Wizard, you can choose to remove earlier versions of the applications you are installing; however, when you deploy Outlook by using the Custom Maintenance Wizard, you must use the Office Removal Wizard separately to remove the previous version.

Start by using 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 stage an installation of Office 2003 and Outlook 2003:

Use the Custom Installation Wizard to create a transform that is used to install Office but excludes Outlook. You include Office customizations in the transform (and, optionally, customizations for Outlook). You then install Office 2003 using the transform.
Use the Custom Maintenance Wizard to install Outlook 2003. You can include both Outlook and Office customizations in the second installation.

Note

As part of an initial Outlook customization, you can capture and include settings in an OPS file. To do this, first install Outlook on a test computer and make your changes to the Outlook settings and environment. Then capture the settings with the Office Profile Wizard.

To install Office from the Office 2003 CD while excluding Outlook 2003

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, click on Microsoft Outlook, then click the Details… button to open a dialog box.

Clear the check box next to the version of Outlook you want to retain on users’ computers, then click OK.
On the Set Feature Installation States page, set the Microsoft Outlook for Windows feature to Not Available, Hidden, Locked.
Set all other Microsoft Office applications in the feature tree (that you want to be installed) to Run from My Computer.
Configure any other installation options, then complete the transform.
To specify this transform for your installation, 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 by running Setup from the administrative installation point.
Later, use the Custom Maintenance Wizard to install Outlook and to modify any existing Office installations throughout your organization.

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). To add Outlook 2003 to your initial Office 2003 installation, you create a CMW file with the appropriate configuration and then run the Custom Maintenance Wizard on users’ computers. For more information about using the Custom Maintenance Wizard to update your installation to include Outlook, see “Updating Feature Installation States and Application Settings” in Chapter 18, “Updating Users’ Office 2003 Configurations.”

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.”

Installing a stand-alone version of Outlook after Office

Another way to install Outlook 2003 after Office 2003 is to use an Office 2003 CD along with a stand-alone version of Outlook. With this option, you can choose to use one administrative installation point for Outlook and Office, or separate installation points.

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 Office, the other for Outlook—or you can use the same 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 installing Office and Outlook, respectively. These administrative installation points can be in different folders on one network server, or they can be on separate servers. Users install Office from one administrative installation point, and then install Outlook 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 after 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 Office 2003 CD. Then you install the stand-alone version of Outlook into the same folder structure.

This method saves 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 Setup files (Setup.exe and Setup.ini), however, you must rename these Setup files to avoid overwriting the unique Outlook and Office versions.

Important

When users set Outlook and another Office application to Run from Network from separate administrative installation points, Windows loads two copies of the shared Mso.dll file if both Outlook and another Office application are being used. Mso.dll uses approximately 5 megabytes (MB) of memory each time it is loaded. Having the administrative images in the same location avoids this additional memory requirement.

Exclude Outlook when installing Office from the Office CD

The process for excluding Outlook when installing Office applications from the Office CD includes these steps:

Copying Office files to an administrative installation point.
Customizing your Office installation to exclude Outlook.
Saving your customizations in a transform.
Installing Office with the custom transform on users’ computers.

Note

As part of an initial Office customization, you can capture and include custom settings in an OPS file. To do this, install Office on a test computer, and then 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 from the Office 2003 CD while excluding Outlook 2003

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
If you are using the same administrative installation point that you will use for your Outlook deployment, rename the Setup files (Setup.exe and Setup.ini) to prevent these files from being overwritten when you install Outlook.

Use consistent file names and the appropriate file name extensions; for example, OffSetup.exe and OffSetup.ini. (If you created the administrative image from the Microsoft Select CD subscription, the files have already been renamed for you.)
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, click Microsoft Outlook, then click Details to open a dialog box.

Clear the check box next to the version of Outlook you want to retain on users’ computers, then click OK.
On the Set Feature Installation States page, set the Microsoft Outlook for Windows feature to Not Available, Hidden, Locked.
Set all other Microsoft Office applications in the feature tree (that you want to be installed) to Run from My Computer.
Configure any other installation options, then complete the transform.
To specify this transform for your installation, 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 by running Setup from the administrative installation point.

Install the stand-alone version of Outlook after installing Office

When you deploy Outlook from a stand-alone version, you can use the same administrative installation point as Office or create a new location for your Outlook files. If you use the same administrative installation point as Office, then you must make sure that the Office Setup files have been renamed so the Outlook Setup files do not overwrite them. Then you customize your Outlook deployment, save the customizations in a transform, and direct users to install Outlook from the Office administrative installation point.

Note

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 by running the Office Profile Wizard and creating an OPS file, be sure to configure only Outlook settings, not other Office settings. Then include the OPS file in the Custom Installation Wizard when you create the transform for installing Outlook.

To install Outlook after Office by using a stand-alone version of Outlook 2003

Using the stand-alone version of Outlook 2003, 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 used for your Office deployment. For example:

\\server1\software\office

If you use the same folder as you used for your Office deployment, make sure that the Office Setup files (Setup.exe and Setup.ini) have been renamed before you copy the files for Outlook. For example, you might rename the Office Setup files to OffSetup.exe and OffSetup.ini. Otherwise, the Outlook Setup files will overwrite the existing Office Setup files.
Use the Custom Installation Wizard to create a transform in which you specify 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. Save the transform in the same folder as the Setup settings file.
If you are using the same administrative installation point that you used for your Office deployment, optionally rename the Outlook Setup files to make it clearer which Setup files belong to which installation.

To do this, in the root folder of the administrative installation point, rename 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, files have already been renamed for you.)
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.
Direct users to install Outlook from the administrative installation point using the Outlook Setup.exe file.

Resources and related information

There are a number of considerations when choosing 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 Customization 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.”

You can use the Office Removal Wizard to remove applications after completing your initial Office installation. For more information about using the Removal Wizard, see “Customizing Removal Behavior” in Chapter 4, “Customizing Office 2003.”