July 16, 1999

Although it is usually simpler to deploy all of Microsoft Office 2000 at once, your organization might benefit from a staggered deployment of some Office applications. For example, you might choose to install Microsoft Outlook® 2000 before Office 2000.

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

• Install the standalone version of Outlook from its own administrative installation point.
• Install the standalone version of Outlook from the same administrative installation point from which you plan to deploy Office.
• Run Office Setup to install only Outlook. Later, you can rerun Office Setup in maintenance mode to install the rest of Office.

---

Toolbox   The Office Resource Kit includes the enhanced Setup.exe file (Setup.exe version 9.0.3821) in a downloadable file named Office 2000 Setup program — updated April 20, 2000 (Setupsr1.exe). You can find this downloadable file on the Office 2000 Resource Kit Downloads page.

---

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

Deploy Outlook from its own administrative installation point

To deploy Office and Outlook separately by using this method, you use Microsoft Office 2000 plus a standalone copy of Microsoft Outlook 2000. Then you create two administrative installation points - one for Outlook and one for Office.

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

---

Important   When users run both Outlook and another Office application set to Run from Network from separate administrative installation points, Windows loads two copies of the shared Mso9.dll file. Because Mso9.dll uses approximately 5 MB of memory when loaded, running more than one Office application in this configuration uses memory needlessly.

---

To install Outlook from a separate administrative installation point

1. Using the standalone Outlook 2000 CD-ROM, run Setup 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

   
   
3. Use the Custom Installation Wizard to create a transform in which you specify the appropriate Outlook configuration for your users.

   Save the transform in the same folder as the Setup settings file.

4. Edit the Setup settings file (Setup.ini) to specify the transform that you created.

   For example, you might add the following line to Setup.ini 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.

5. Direct users to install Outlook from this administrative installation point.

When you deploy the rest of Office, you create a new administrative installation point and direct users to install the rest of Office 2000 from this location.

To install Office from a second administrative installation point

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

   \\server1\software\office

   
   
3. Use the Custom Installation Wizard to create a transform in which you set Microsoft Outlook for Windows to Not Available and Hide.

   Save the transform in the same folder as the Setup settings file.

4. Edit the Setup settings file (Setup.ini) to specify the transform that you created.

   For example, you might add the following line to Setup.ini under the [MST] section:

   MST1=Office.mst

   
   

   You must remove the comment marker (;) from the [MST] header line so that the transform is read correctly.

5. Direct users to install Office from this administrative installation point.

Deploy Outlook from the same administrative installation point as Office

Another method for deploying Outlook separately 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 standalone Outlook CD-ROM. Then you install the rest of Office from the Office 2000 discs 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 take steps to avoid overwriting the following files for both Outlook and Office:

• Setup.exe
• Setup.ini
• Data1.msi
• Autorun.inf

Install Outlook first

Begin by creating an administrative installation point for Outlook on a network share and providing unique names for the Setup files.

To install Outlook from an initial administrative installation point

1. Using the standalone Outlook 2000 CD-ROM, run Setup with the /a command-line option.
2. When prompted for the server location, enter a folder on a network server. For example:

   \\server1\software\office

   
   
3. Use the Custom Installation Wizard to create a transform in which you specify the appropriate Outlook configuration for your users.

   Save the transform in the same folder as the Setup settings file.

4. In the root folder of the administrative installation point, rename Setup.exe, Setup.ini, Data1.msi, and Autorun.inf to prevent these files from being overwritten when you install the rest of Office.

   Use consistent file names and the appropriate file name extensions. For example, OlkSetup.exe, OlkSetup.ini, OlkInst.msi, and OlkAuto.inf.

5. Edit the Outlook Setup settings file (INI file) to specify the transform that you created, plus the new names for the MSI and Autorun.inf files.

   For example:

   [MSI]
   MSI=OlkInst.msi
   [MST]
   MST1=Outlook.mst
   [Autorun] autorun.inf=OlkAuto.inf

   
   

   You must remove the comment marker (;) from the [MST] header line so that the transform is read correctly.

6. Instruct users to install Outlook by running the unique Setup.exe file that you created.

Setup automatically searches for the Setup settings file with the same file name as the Setup program. For example, if you renamed Setup.exe to OlkSetup.exe, Setup looks for OlkSetup.ini. Setup uses this settings file to find the correct MSI, MST, and Autorun.inf files.

Install the rest of Office

When you are ready to deploy the rest of Office, you can install Office on the same administrative installation point that you created for Outlook.

To install Office from the same administrative installation point as Outlook

1. Using Office 2000 Disc 1, run Setup with the /a command-line option.
2. When prompted for the server location, enter the folder on the server where you installed Outlook. For example:

   \\server1\software\office

3. Use the Custom Installation Wizard to create a transform to install all of Office except Outlook. On the Set Feature Installation States panel, set the Microsoft Outlook for Windows feature to Not Available and Hide.

   Save the transform in the same folder as the Setup settings file.

4. In the root folder of the administrative installation point, rename Setup.exe, Setup.ini, Data1.msi, and Autorun.inf.

   Use similar file names to those you used for Outlook and maintain the same file name extensions. For example, OffSetup.exe, OffSetup.ini, OffInst.msi, and OffAuto.inf.

5. Edit the Setup settings file (INI file) to specify the transform that you created, plus the new names for the MSI and Autorun.inf files.

   For example:

   [MSI]
   MSI=OffInst.msi
   [MST]
   MST1=Officemain.mst
   [Autorun]
   autorun.inf=OffAuto.inf

   
   

   You must remove the comment marker (;) from the [MST] header line so that the transform is read correctly.

6. Instruct users to install Office by running the unique Setup.exe file that you created.

Use installation options to install Outlook first

Another way to stagger your deployment of Outlook and Office from a single administration installation point is to install Outlook first from Office 2000 Disc 1. Then you can rerun Office Setup and change installation options to install the rest of Office.

To create a transform for installing Outlook only

1. Start the Custom Installation Wizard and open the Office 2000 package (MSI file).
2. On the Remove Previous Versions panel, click Remove the following versions of Microsoft Office applications.
3. Clear all the check boxes except Microsoft Outlook 97 & 98 and Obsolete Microsoft Office Files.
4. On the Set Feature Installation States panel, 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.

   ---

   Note   You can also install shared Office tools, converters, or other features that support your Outlook installation.

   ---

6. Complete the transform by configuring other custom installation options.

   For example, you can specify Outlook profile information on the Customize Outlook Install Options panel.

Now you use this transform to install Outlook.

To install Outlook separately by using installation options

1. Run Setup from Office Disc 1 with the /a command-line option.
2. When prompted for the server location, enter a folder on a network server. For example:

   \\server1\software\office

   
   
3. Edit the Setup settings file (Setup.ini) to specify the transform that you created.

   For example:

   [MST]
   MST1=Outlook.mst

   
   

   You must remove the comment marker (;) from the [MST] header line so that the transform is read correctly.

4. Instruct users to install Outlook by running Setup from this administrative installation point.

When you rerun Setup after Outlook is installed, Setup runs in maintenance mode. At that time, users can modify their installations to include additional Office applications.

Update Office installations throughout your organization

To modify Office installations throughout your organization after your initial deployment, you can use the soon-to-be-released Custom Maintenance Wizard.

Similar to the Custom Installation Wizard, the Custom Maintenance Wizard reads the Office 2000 package (MSI file) and records your changes in a 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.

The Office Resource Kit includes the Custom Maintenance Wizard (Maintwiz.exe). You can find this downloadable file on the Office 2000 Resource Kit Downloads page.

Related links

You can also deploy Outlook after you deploy Office. For more information about staggering your deployment of Office applications, see Staging Your Deployment of Office Premium in the Office 2000 Resource Kit.