Microsoft Office XP

Automated Installation Guide

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

                                                                    

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Modified by:

Keith V. Klenke

http://www.abend.org

Revised 31 May 2006


Table of Contents

Preface.......................................................................................................................................................................... 3

Perform an MS Office Administrative Installation (AI).......................................................................................... 4

Updating the MS Office Administrative Installation (AI)..................................................................................... 6

Install the Microsoft Office XP Resource Kit (ORK).............................................................................................. 8

Update the Office XP Resource Kit......................................................................................................................... 11

Create Transform (MST) file..................................................................................................................................... 13

Open the MSI File Screen......................................................................................................................................... 14

Open the MST File Screen........................................................................................................................................ 15

Select the MST File to Save Screen........................................................................................................................ 16

Specify Default Path and Organization Screen...................................................................................................... 17

Remove Previous Versions Screen.......................................................................................................................... 18

Set Feature Installation States Screen.................................................................................................................... 19

Customize Default Application Settings Screen................................................................................................... 21

Change Office User Settings Screen....................................................................................................................... 22

Add/Remove Files Screen........................................................................................................................................ 23

Add/Remove Registry Entries Screen.................................................................................................................... 24

Add, Modify, or Remove Shortcuts Screen........................................................................................................... 25

Identify Additional Servers Screen......................................................................................................................... 26

Specify Office Security Settings Screen................................................................................................................. 27

Add Installations and Run Programs Screen......................................................................................................... 28

Custom Installation Wizard – Summary Screen.................................................................................................... 29

Create Application Object using MSI file.............................................................................................................. 30

Maintaining the installation..................................................................................................................................... 36

Notes............................................................................................................................................................................ 37

Credits.......................................................................................................................................................................... 38

 

 


Preface

 

This document provides an overview of the process to allow for the automated delivery of Microsoft Windows XP via Novell ZenWorks for Desktops v3.2, the basics of which can also be used by any other software distribution method.  It is the purpose of this document to provide a documented, step by step procedure on how to automate and deliver Microsoft Office XP via ZenWorks for Desktops v3.2 components.   


Perform an MS Office Administrative Installation (AI)

 

Create a directory on a server which will hold the Administrative Install.

 

From a command line, run appropriate MS Office SETUP file with the “/a” command line option. This is usually done from the “enterprise” version of the MS Office CD.

 

 

 

On the initial screen, input the name of the Organization, the location on the network which will hold the AI, and the 5x5 Product Key.  Click on the “Next” button to continue.

 

 

Click on the “Next” button to continue.


On the End-User License Agreement screen, place a check mark in the “I accept the terms in the License Agreement” box.

 

 

Click on the “Install” button to continue.

 

Microsoft Office XP will now begin installation of files and other components.  This process should take approximately 7 minutes (on a 100Mb switched LAN), and is complete when you see the following screen. Some however find it easier and quicker to do everything locally then copy the files to the server.

 


Updating the MS Office Administrative Installation (AI)

 

Go to http://www.microsoft.com/office/ork/xp/journ/adminup.htm and download the necessary Administrative Updates. These can be extracted locally or to the network. Most are self extracting files and will just ask where to be extracted.

 

 

Others are simple install files & will need to be extracted manually -

 

 

To extract it manually drop to a command prompt & run the file and the command line options, they are usually:

 

 

After this file has been extracted then the patch msp can be used just as any other Administrative update.

 

 

 

 

 

 

 

 

 

In order to update the Administrative Install run the following command:

 

“msiexec /p [path\name of update MSP file] /a [path\name of MSI file] SHORTFILENAMES=TRUE /qb /L* [path\name of log file]”

 

 

 

The name of the MSI file in question is STD.MSI for Microsoft Office Standard, PRO.MSI for Professional, PROPLUS.MSI for Professional with Front Page, and OWC10.MSI for the Office Web Components. The name of the update MSP file in question would be the extracted patch file.

 

The order in which to run the Administrative Updates against the Administrative Install is the dated order in which they have been released. Major service packs usually combine all the previous updates, resulting in only needing to run the Major update, and the minor ones that come out after it.

 

Once each patch is completed you can view the log file, and at the end it should state:

=== Logging stopped: date  time ===

MSI (X) (XX:XX): Product: Microsoft Office XP -- Installation operation completed successfully.

 

At this point you should have a fully patched Office XP Administrative Install point.


Install the Microsoft Office XP Resource Kit (ORK)

 

Run the ORK setup program (located on the Microsoft Office XP CD) from Start > Run.

 

 

On the End-User License Agreement screen, place a check mark in the “I accept the terms in the License Agreement” box.

 

 

Click on the “Next” button to continue.


Choose installation type (Complete), and location to where the install will reside. 

 

 

Click on the “Next” button to continue.

 

On the “Begin Installation” screen, review the options that will be installed. 

 

 

Click on the “Install” button to begin the installation.

 

The Microsoft Office XP Resource Kit will now begin installation of files and other components.  This process should take approximately 2 minutes (on a 100Mb switched LAN), and is complete when you see the following screen.

 

 


Update the Office XP Resource Kit

 

Go to http://www.microsoft.com/office/ork/xp/journ/orktlexe.htm and download the file OrkTools.exe. You will need to run this to bring your ORK up to the newest revision.

 

 

 

Leave the radio button selected on “Add or Remove Features” and click next to continue.

 

 

 

The Microsoft Office XP Resource Kit update will now begin installation after you click the “Update” of files and other components, and is complete when you see the following screen.

 

 

 

 

 


Create Transform (MST) file.

 

Run the Custom Installation Wizard (CIW) from the Start > Programs > Microsoft Office Tools > Microsoft Office XP Resource Kit Tools menu. 

 

 

 

The Microsoft Office XP Custom Installation Wizard (CIW) allows customization of various parts of Microsoft Office XP setup and related applications. Default features and installation settings can be changed to suit your needs within the pages of this wizard. Files and registry settings can be included as part of the setup process. Custom user settings for most features available in Office applications can be added to provide a fully configured, user-ready product installation.

 

Click on the “Next” button to continue.


Open the MSI File Screen

 

 

The Custom Installation Wizard (CIW) reads an MSI file to obtain default Setup option settings. The MSI file contains all the information Setup needs to install the Office XP.

 

Browse to the directory that holds the AI and highlight the MSI file that will be utilized for this MST.

 

Click on the “Next” button to continue.


Open the MST File Screen

 

Use this screen to select whether to Create a New MST file or Open and existing MST file.

 

For this process, select “Create a New MST file”.

 

Click on the “Next” button to continue.


Select the MST File to Save Screen

 

 

Enter the name and path you want to use for the MST file.

 

Click on the “Next” button to continue.


Specify Default Path and Organization Screen

 

 

Specify:

Default installation path: This is where the installation of Office will install on the target computer.

 

Organization name: Specify the Organization name to be used during the setup.

 

Click on the “Next” to continue.


Remove Previous Versions Screen

 

 

  • Default Setup behavior

 

During Office installation, Setup scans for previously installed versions of Office (version 4.0 through 2000). A command line option , “/q”, sets the user interface to the basic level of simple progress and error handling.  This switch is optional only on the command line.   If the user interface is not limited by any form of /q, Setup allows the user to choose the applications to remove or not remove. If the user interface is limited in any way by the /q, the user does not have the option to select specific applications to remove; the default is to remove all prior versions.

 

For this process, the default option will be utilized.

 

Click on the “Next” button to continue.


Set Feature Installation States Screen

 

First, on the Microsoft Office features selection, choose “Run all from My Computer”.  This will place the full software distribution on the local computer.

 

 

Click on the “Next” button to continue.


Next, select each component of Microsoft Office that will NOT be installed, and set it as being “Not Available”.  A red “X” will appear over the feature.

 

 

On this screen you may set the install state of each application, such as;

  • Run from My Computer
  • Run from Network
  • Not Available
  • Not Available, Hidden or Locked
  • Installed on First Use

 

Use the Properties box to set these options;

  • Disable Run from Network
  • Disable Installed on First Use
  • Do Not Migrate Previous Installation State

 

Disable Run from Network and Disable Installed on First Use, these two options remove the install states from the drop down menu for each application or feature selected in the feature tree.

Do Not Migrate Previous Installation State, uses the feature of the pervious installation of Office and goes by those settings.

 

Click on the “Next” button to continue.


Customize Default Application Settings Screen

 

 

Use this screen to specify whether or not you will be Migrating the user settings from a pervious installation of Office or you can specify the location of a OPS (Office Profile Settings) file and use those settings. (In order to use a OPS file you must use the Profile Wizard to create it.)

 

Click on the “Next” button to continue


Change Office User Settings Screen

 

 

This page allows you to make changes to the menu, toolbar, and several (but not all) user interface elements having user configuration customization capability. Most of these menu options can also be controlled through system policy settings. Some of these settings also control functions that cannot be controlled through the Office user interface.

 

After configuring the settings desired…

 

Click on the “Next” button to continue.


Add/Remove Files Screen

 

 

Use this screen if you have a Word template, or an add-in users commonly use, include it on the Add Files tab of this page. Setup installs the file on the user’s computer to the path you specify. If the path does not exist on the user's computer, it is created automatically. If a Word template or existing add-in on the user's computer needs to be deleted, add the filename and path to the Remove Files tab of this page.

 

Click on the “Next” button to continue.


Add/Remove Registry Entries Screen

 

 

Use this screen to add additional registry keys or remove registry keys to/from the user’s computer.

 

Click on the “Next” button to continue.


Add, Modify, or Remove Shortcuts Screen

 

 

From this screen, you may modify or remove default shortcuts for Office applications in the Installed tab. You can also add new shortcuts for any files currently installed on the user’s computer, or to added files installed with a transform. You can also modify shortcuts on the Not Installed tab.

 

Click on the “Next” button to continue.


Identify Additional Servers Screen

 

 

Use this screen to add any additional servers that have the distribution files replicated from the original server specified.  Click on the Add button and enter the path.

 

Click on the “Next” button to continue.


Specify Office Security Settings Screen

 

 

 

Most security requirements of a corporation or an end user can be accommodated through the setting of all of the applications and features on this page to a security level of High. This has the advantage of not disabling features of Office and offering the best protection from viruses. Usually, setting security to high on all the entries on this page along with a virus protection program provides all the necessary security a user or corporation needs.

 

Click on the “Next” button to continue.

 


Add Installations and Run Programs Screen

 

 

Add any additional commands or program installs you want to be installed, after Office XP is completed, on this page.

 

Click on the “Finish” button to continue.


Custom Installation Wizard – Summary Screen

 

 

This Screen shows the location of the MST file and shows the command you must type to use the MST file with the setup of Office XP.

 

Click on the “Exit” button to complete this section of the process.


Create Application Object using MSI file.

Launch ConsoleOne v1.3.2 or later.

Browse to and highlight the container in the tree to hold the Application object.

 

Click on File > New > Object, and select the “App:Application” class object.

 

 

Click on the “OK” button to continue.

 

On the next screen, select the “Using and .msi file” option.

 

 

Click on the “Next” button to continue.


On the next screen, browse to, and select the .msi file that is to be used.

 

 

Click on the “Next” button to continue.

 

On the next screen, name the Application object (consistent with NDS object naming rules), and enter the path to the Administrative Installation directory.

 

 

Click on the “Next’ button to continue.


On the next screen, place a check mark in the “Display details after creation” box.

 

 

Click on the “Finish” button to continue.  The NDS Application object is now created.  The object properties will open.


Go to the “Run Options - Application “ properties tab of the Application object.  Select “Path to executable file”.

Input and/or verify the correct path to the setup program in the AI directory.

Input the “/qb-“ switch in the “Parameters” field

 

 

Continue with the next page of directions.


Go to the “Availability – System Requirements“ properties tab of the Application object.

Add the Operating System(s) for which this application may be distributed.

 

 

Continue with the next page of directions.


Go to the “Common - Transforms“ properties tab of the Application object.

Add the name and path to the .MST file to be used during installation.

 

 

Click on “OK” to complete the configuration of the Application object.

 

The object can now be associated with other NDS objects that have minimum Read and File Scan rights to the Administrative Installation directory for Novell Application Launcher delivery.

 

 


Maintaining the installation

When a new patch comes out, run it against the Administrative install, then run VOMUS. (expand on this section).

msiexec /i [path to updated .msi file on the administrative image] REINSTALL=[list of features]

REINSTALLMODE=vomus /qb

 


Notes

It is recommended that workstations have MSI2 installed on them before installing msofficeXP otherwise it may prompt to restart after installation is complete.

http://www.microsoft.com/downloads/release.asp?releaseid=32832 for  NT4 & W2K

http://www.microsoft.com/downloads/release.asp?ReleaseID=32831 for Win9x & WinMe.

 

If running the installer from a win9x machine you may have to put “start” before msiexec

 

If you are installing to machines where the users are not admins, make sure to do so with “elevated rights”.

 

 

** any other gotchas?

 

Recommended settings for Terminal/Citrix servers.

 


Credits

Novell.com, Microsoft.com, and many individuals and companies that helped me along the way in pulling all the resources together into this howto.

 

 

END OF DOCUMENT