Updated: 2007-10-31
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 from the local installation source
-
Distribute the local installation to users.
For information about this step, see Precache the local installation source for the 2007 Office system.
-
In the table below, find the download code for the Office product you want to install.
-
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 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.
Office product download codes
Download codes for each Office product can be found in the Setup.xml file in the core product folder. The line in the Setup.xml for Office Standard 2007 looks like this:
|
<LocalCache DownloadCode="{90120000-0012-0000-0000-0000000FF1CE}" SkuComponentDirectory="Standard.WW"> |
Download codes are also listed in the following table. Drive equals the drive on which \MSOCache is located, which is the drive on which Office is installed—typically the C drive. These product codes represent the initial release of the product.
|
Office product
|
Core product folder
|
Download code
|
| Microsoft Office Enterprise 2007 | Enterprise.WW | {90120000-0030-0000-0000-0000000FF1CE}-drive |
| Microsoft Office Professional Plus 2007 | ProPlus.WW | {90120000-0011-0000-0000-0000000FF1CE}-drive |
| Microsoft Office Standard 2007 | Standard.WW | {90120000-0012-0000-0000-0000000FF1CE}-drive |
| Microsoft Office Professional 2007 | Pro.WW | {90120000-0014-0000-0000-0000000FF1CE}-drive |
| Microsoft Office Access 2007 | Access.WW | {90120000-0015-0000-0000-0000000FF1CE}-drive |
| Microsoft Office Excel 2007 | Excel.WW | {90120000-0016-0000-0000-0000000FF1CE}-drive |
| Microsoft Groove 2007 | Groove.WW | {90120000-00BA-0000-0000-0000000FF1CE}-drive |
| Microsoft Office InfoPath 2007 | InfoPath.WW | {90120000-0044-0000-0000-0000000FF1CE}-drive |
| Microsoft Office OneNote 2007 | OneNote.WW | {90120000-00A1-0000-0000-0000000FF1CE}-drive |
| Microsoft Office Outlook 2007 | Outlook.WW | {90120000-001A-0000-0000-0000000FF1CE}-drive |
| Microsoft Office PowerPoint 2007 | PowerPoint.WW | {90120000-0018-0000-0000-0000000FF1CE}-drive |
| Microsoft Office Project Professional 2007 | PrjPro.WW | {90120000-003B-0000-0000-0000000FF1CE}-drive |
| Microsoft Office Project Standard 2007 | PrjStd.WW | {90120000-003A-0000-0000-0000000FF1CE}-drive |
| Microsoft Office Publisher 2007 | Publisher.WW | {90120000-0019-0000-0000-0000000FF1CE}-drive |
| Microsoft Office SharePoint Designer 2007 | SharePointDesigner.WW | {90120000-0017-0000-0000-0000000FF1CE}-drive |
| Microsoft Office Visio Professional 2007 | VisPro.WW | {90120000-0051-0000-0000-0000000FF1CE}-drive |
| Microsoft Office Visio Standard 2007 | VisStd.WW | {90120000-0053-0000-0000-0000000FF1CE}-drive |
| Microsoft Office Word 2007 | Word.WW | {90120000-001B-0000-0000-0000000FF1CE}-drive |
For information about the numbering scheme for the 2007 Office system product codes, see KB article 928516 Description of the numbering scheme for product code GUIDs in 2007 Office suites and programs on the Microsoft Help and Support Web site.