Run Setup from the local installation source to install the 2007 Office system

This Office product will reach end of support on October 10, 2017. To stay supported, you will need to upgrade. For more information, see , Resources to help you upgrade your Office 2007 servers and clients.

Topic Last Modified: 2016-11-14

When you deploy the 2007 Microsoft Office system in your organization, Setup creates a local installation source on each user's computer, and then installs Office from that location. You can reduce the load on your network by separating these two parts of the installation process. First, run Setup to distribute the local installation source to users; later, run Setup again to complete the installation.

Because the local installation source also includes a copy of Setup, you can go one step further and run Setup directly from the local installation source, rather than running it over the network. This strategy allows you to minimize the load on the network and still upgrade everyone to the new version at the same time.

To run Setup, you must identify the subfolder in MSOCache\All Users that contains the core product that you want to install. Setup.exe is located in the same folder that contains the core product file <product_name>WW.msi, for example, EnterpriseWW.msi or ProPlusWW.msi. For example, for Microsoft Office Enterprise 2007, the core product file is EnterpriseWW.msi, and the folder containing setup.exe is {90120000-0030-0000-0000-0000000FF1CE}-drive, and it includes the following files:

• EnterpriseWW.msi

• EnterpriseWW.xml

• EnterWW.cab

• ID_00030.DPC

• Office64WW.msi

• Office64WW.xml

• ose.exe

• osetup.dll

• OWOW64WW.cab

• setup.exe

• Setup.xml

Run Setup from the local installation source

1. Distribute the local installation to users.

   For information about this step, see Precache the local installation source for the 2007 Office system.

2. In the table in Office product download codes later in this article, find the download code for the Office product that you want to install.

3. Run Setup.exe from the subfolder in MSOCache\All Users that corresponds to the download code. You can use a relative path to point to the location of Setup.exe on each user's computer.

   For example, if you deployed the local installation source for Microsoft Office Standard 2007 on the C drive, use the following command line:

   C:\MSOCache\All Users\{90120000-0012-0000-0000-0000000FF1CE}-C \setup.exe

   You can send the Setup.exe command line to users by whatever means that you want—for example, in a log-in file or a batch file.

The default location of the local installation source is \MSOCache\All Users at the root of the drive on which Office is installed. Setup copies each package from the network installation point to a separate subfolder under MSOCache\All Users. The subfolder for the core product package includes a copy of Setup.exe that defaults to installing that product. Subfolders under MSOCache\All Users are named according to the download code for each package, rather than the folder naming convention used on the network installation point.

The letter appended to the end of each download code (-C in the preceding example) indicates the drive on which the local installation source for that product is installed. If a user has installed multiple Office products on different drives, each drive contains a local installation source in the MSOCache\All Users folder. The drive letter in the download code allows Windows Installer to identify the correct location for the specified product.

In the precache scenario only, Setup also copies the Updates folder from the network installation point to the local installation source. You can store both Setup customization files (MSP files) and software updates (MSP files) in the Updates folder and automatically include them in the installation. You gain the benefits of an offline installation without losing any of your customizations.

<LocalCache DownloadCode="{90120000-0012-0000-0000-0000000FF1CE}" SkuComponentDirectory="Standard.WW">