Topics in this chapter   Ensuring a Quiet Installation and Startup     Installing in a Terminal Services Environment     Installing Before or After Office     Configuring Outlook for Roaming Users

Installing Before or After Office

Although it is usually simpler to deploy all of Microsoft Office XP at once, your organization might benefit from a staged deployment of some Office applications. For example, you might choose to install Microsoft Outlook 2002 before Office XP, allowing users to benefit immediately from enhancements in Outlook 2002. Or, you might upgrade Outlook 2002 after you have installed Office XP and upgraded your messaging server to Microsoft Exchange 2000 Server.

Installing Outlook before or after Office is one example of staging the deployment of an Office application. However, you can use the methods described here to install any Office application before or after installing the rest of Office.

Options for installing Outlook before Office

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

• Install the stand-alone version of Outlook from the same or a different administrative installation point from which you plan to install Office.
  
  
• Run Office Setup to install only Outlook, then rerun Office Setup in maintenance mode to install the rest of Office when you are ready.

Installing a stand-alone version of Outlook before Office

One way to install Outlook 2002 before Office XP is to use an Office XP 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.

Choosing whether to use one or more administrative installation points

When you use the stand-alone version to install Outlook, you can create two administrative installation points — one for Office, the other for Outlook — or you can deploy the stand-alone version of Outlook from the same administrative installation point from which you deploy Office. Each scenario has unique benefits, depending on your deployment plans.

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 Microsoft Office XP plus a stand-alone copy of Microsoft Outlook 2002.

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 XP disc 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 two Setup files (Setup.exe and Setup.ini), however, you must rename the 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, Microsoft Windows® operating systems load two copies of the shared Mso.dll file if both Outlook and another Office application are being used. Mso.dll uses approximately 5 MB of memory each time it is loaded. Having the administrative images in the same location avoids this additional memory requirement.

Installing Outlook from the stand-alone Outlook version

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 customizations in a transform.
  
  
• Installing Outlook with the custom transform on users' computers.

Note   As part of an initial Outlook customization, you can capture and include settings in a profile settings file (OPS file). To do this, install Outlook on a test computer, and then make any desired 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 include only Outlook settings. Then include the OPS file in the Custom Installation Wizard when you create the transform for installing Outlook.

To install Outlook by using a stand-alone Outlook 2002 version

1. Using the stand-alone Outlook 2002 version, run Setup.exe with the /a command-line option.
   
   
2. 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

3. Use the Custom Installation Wizard to create a transform that references the Outlook MSI file in the root of this administrative installation point, 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.

4. If you are using the same administrative installation point that you will use for your Office deployment, rename the Setup files to prevent these files from being overwritten when you install the rest of Office.

   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, the files have already been renamed for you.)

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

6. Direct users to install Outlook from this administrative installation point by using Outlook Setup.

Installing Office after installing a stand-alone version of Outlook

When you deploy the rest of Office, you can use the same administrative installation point or create a new location for your Office files. 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 direct users to install the rest of Office XP from the Office administrative installation point.

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 then make any desired 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 Outlook.

To install Office after installing stand-alone Outlook

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

   \\server1\software\office

3. Use the Custom Installation Wizard to create a transform to customize Office for your deployment.

   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.

4. To specify this transform when you install Outlook, start the Setup INI Customization Wizard.
   
   
5. On the Specify options for each package in your INI file page, select the Outlook MSI file and specify your transform in the Transform (MST file) to apply during installation box.

   The Setup INI Customization Wizard adds the following entry to the INI file:

   [MST1]
   MST1=Office.mst

   Note that if you elect to edit the INI file manually, you must remove the comment marker (;) from the [MST] header line so that the transform is read correctly.

6. Direct users to install Office from the administrative installation point.

Using installation options to install Outlook before Office

Another way to stage your deployment of Outlook 2002 and Office XP is to install Outlook first from an Office XP SKU that includes Outlook. Then you can configure Office to be installed by using the Custom Maintenance Wizard and changing installation options to install the rest of Office. In this case, you use a single administrative installation point for both installations.

Issues to consider

If you are upgrading from an earlier version of Office, there are several issues to consider when using this method for installing Outlook 2002 before Office XP. 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 XP by using the Custom Maintenance Wizard, you limit your options for easily removing earlier versions of other Office applications. When you deploy Outlook 2002 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.

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:

First, you use the Custom Installation Wizard to create a transform that includes any Outlook and Office customizations you might have. Then, install Outlook using that 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.

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 any desired 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 include only Outlook settings.

Optionally, you can install all of Office on the test machine and capture settings for other Office XP applications as well as 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 XP CD

1. Start the Custom Installation Wizard and open the Office XP package (MSI file).
   
   
2. On the Remove Previous Versions page, click Remove the following versions of Microsoft Office applications.
   
   
3. In the table of applications, for each Office application except Microsoft Outlook, click the application name, then click the Details… button.

   Clear all the check boxes to retain the current versions of the application on users' computers, then click OK. Repeat for each application.

4. On the Set Feature Installation States page, set all Microsoft Office applications in the feature tree to Not Available.
   
   
5. 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.

6. Configure any other installation options, then complete the transform.

   For example, you can specify Outlook profile information.

7. To specify this transform when you install Outlook, start the Setup INI Customization Wizard.
   
   
8. On the Specify options for each package in your INI file page, select the Outlook MSI file and specify your transform in the Transform (MST file) to apply during installation box.

   The Setup INI Customization Wizard adds the following entry to the INI file:

   [MST1]
   MST1=Office.mst

   Note that if you elect to edit the INI file manually, you must remove the comment marker (;) from the [MST] header line so that the transform is read correctly.

9. Instruct users to install Outlook by running Setup from this administrative installation point.
   
   
10. 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 XP package (MSI file) and records your changes in a configuration maintenance file (CMW file). To add Office applications to your initial Outlook installation, you create a CMW file with the appropriate configuration, and then run the Custom Maintenance Wizard on users' computers.

Toolbox   The Office XP 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 the Toolbox.

Options for installing Outlook after Office

When you install Microsoft Outlook 2002 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 to install Office applications except for Outlook, then rerun Office Setup in maintenance mode 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, excluding Outlook, first, then install Outlook from the Outlook 2002 stand-alone version.
  
  

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

Issues to consider

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 at deployment. Since you are installing two separate SKUs, you can use the Custom Installation Wizard to create two transforms, one for each deployment. In each transform, you can specify to remove earlier versions of the applications. For example, when you deploy Outlook, you can specify in the transform to remove earlier versions of Outlook when Outlook 2002 is installed.

In 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. The Office Removal Wizard can be used to remove previous versions of Office applications.

Installing Outlook after Office is one example of staging your deployment of Office applications. However, you can use the methods described here to install any Office application after installing the rest of Office.

Using installation options to install Outlook after Office

One way to stage your deployment of Outlook 2002 and Office XP is to install Office first from an Office XP SKU and customize your installation to exclude Outlook. Then, later, you can configure Outlook to be installed by using the Custom Maintenance Wizard and changing installation options to install just Outlook. In this case, you use a single administrative installation point for both installations.

Issues to consider

If you are upgrading from an earlier version of Office, there are several issues to consider when using this method for installing Office XP before Outlook 2002. First, if you plan to use the Office Profile Wizard to capture Outlook settings, you must configure these settings and include the 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 deploy Outlook 2002 by using the Custom Maintenance Wizard, you limit your options for easily removing earlier versions of Outlook software. When you deploy Office XP by using the Custom Installation Wizard, you can choose to remove earlier versions of Office while leaving existing Outlook software. However, when you deploy Outlook by using the Custom Maintenance Wizard, you cannot specify to remove older versions of Outlook. However, you can use the Office Removal Wizard to remove files instead.

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 install Office XP and Outlook 2002 in stages:

First, you 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 XP using the transform.

Then, later, you use the Custom Maintenance Wizard to install Outlook 2002. 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, install Outlook on a test computer, and then make any desired changes to the Outlook settings and environment.

To install Office from the Office XP CD, excluding Outlook 2002

1. Start the Custom Installation Wizard and open the Office XP package (MSI file).
   
   
2. On the Remove Previous Versions page, click Remove the following versions of Microsoft Office applications.
   
   
3. 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' computer, then click OK.

4. On the Set Feature Installation States page, set the Microsoft Outlook for Windows feature to Not Available, Hidden, Locked.
   
   
5. Set all other Microsoft Office applications in the feature tree (that you want to be installed) to Run from My Computer.
   
   
6. Configure any other installation options, then complete the transform.
   
   
7. To specify this transform when you install Outlook, start the Setup INI Customization Wizard.
   
   
8. On the Specify options for each package in your INI file page, select the Outlook MSI file and specify your transform in the Transform (MST file) to apply during installation box.

   The Setup INI Customization Wizard adds the following entry to the INI file:

   [MST1]
   MST1=Office.mst

   Note that if you elect to edit the INI file manually, you must remove the comment marker (;) from the [MST] header line so that the transform is read correctly.

9. Instruct users to install Office by running Setup from the administrative installation point.
   
   
10. 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 XP package (MSI file) and records your changes in a configuration maintenance file (CMW file). To add Outlook 2002 to your initial Office XP installation, you create a CMW file with the appropriate configuration and then run the Custom Maintenance Wizard on users' computers.

Toolbox   The Office XP 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 the Toolbox.

Installing a stand-alone version of Outlook after Office

Another way to install Outlook 2002 after Office XP is to use an Office XP 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.

Choosing whether to use one or more administrative installation points

When you use a stand-alone version to install Outlook, you can create two administrative installation points — one for Office, the other for Outlook — or you can deploy the stand-alone version of Outlook from the same administrative installation point from which you install Office. Each scenario has unique benefits, depending on your deployment plans.

You might choose to use separate installation points, for example, if two different groups in your organization will be used to install 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 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 XP CD. Then you install Outlook from the stand-alone Outlook version 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, however, you must rename these files to avoid overwriting the unique Outlook and Office versions:

• Setup.exe
  
  
• Setup.ini

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 MB of memory each time it is loaded. Having the administrative images in the same location avoids this additional memory requirement.

Excluding Outlook when installing Office applications from an Office CD

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

• Copying Office files to an administrative installation point.
  
  
• Customizing your Office deployment 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 any desired 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 XP CD, excluding Outlook 2002

1. Using an Office XP CD, run Setup.exe with the /a command-line option.
   
   
2. When prompted for the server location, enter a folder on the network server.

   For example:

   \\server1\software\office

3. If you are using the same administrative installation point that you will use for your Outlook deployment, rename the Setup files to prevent these files from being overwritten when you install Outlook.

   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, 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.)

4. Start the Custom Installation Wizard and open the Office XP package (MSI file).
   
   
5. On the Remove Previous Versions page, click Remove the following versions of Microsoft Office applications.
   
   
6. 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' computer, then click OK.

7. On the Set Feature Installation States page, set the Microsoft Outlook for Windows feature to Not Available, Hidden, Locked.
   
   
8. Set all other Microsoft Office applications in the feature tree (that you want to be installed) to Run from My Computer.
   
   
9. Configure any other installation options, then complete the transform.
   
   
10. To specify this transform when you install Outlook, start the Setup INI Customization Wizard.
    
    
11. On the Specify options for each package in your INI file page, select the Outlook MSI file and specify your transform in the Transform (MST file) to apply during installation box.

    The Setup INI Customization Wizard adds the following entry to the INI file:

    [MST1]
    MST1=Office.mst

    Note that if you elect to edit the INI file manually, you must remove the comment marker (;) from the [MST] header line so that the transform is read correctly.

12. Instruct users to install Office by running Setup from the administrative installation point.

Installing a stand-alone version of Outlook after installing Office

When you deploy Outlook from a stand-alone Outlook 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 any desired 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 include only Outlook 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 Outlook 2002 version

1. Using the stand-alone Outlook 2002 version, run Setup.exe with the /a command-line option.
   
   
2. 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

   Note that if you use the same folder as you used for Office deployment, make sure that the Office Setup files (Setup.exe and Setup.ini) have been renamed before you copy 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.

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

4. 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, the files have already been renamed for you.)

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

6. Direct users to install Outlook from the administrative installation point using the Outlook Setup.exe file.

See also

There are a number of considerations to examine 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.

The Office Customization Wizard provides a straightforward way to configure and install Outlook 2002. For more information about Outlook configuration choices, see Customizing an Outlook Installation.

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 Removing Applications or Features After Installation.