The Microsoft Office XP Resource Kit ReadMe file is organized into two sections, Issues and Errata. The Issues section contains information regarding deployment performance, configuration, suggestions for problem avoidance, and known pitfalls that may obstruct the ability to install and use important segments of Office XP. The Errata section contains corrections to the Office Resource Kit documentation discovered after it was submitted for publication.
Quick Glossary of terms
|
CIW |
Custom Installation Wizard |
|
CMW |
Custom Maintenance Wizard |
|
MSI |
Windows Installer Package file (ie: proplus.msi, std.msi, lpk.msi). |
|
MST |
Transform file (ie: *.mst). |
Corporate Error Reporting tool
"Allow External URLs" label in the Corporate Error Reporting tool is mislabeled
The Allow External URLs label in the Corporate Error Reporting tool (Edit | Default Policy dialog) should read: Allow Microsoft Responses.
Help documents command line of Corporate Error Reporting tool incorrectly
Within the CER.hlp file, it is documented that a command line switch -s exists to synchronize reporting. This command line option does not exist. It should be -r for reporting. See downloadable CER.hlp from ORK website to replace existing help file if needed (available in the near future post release).
Documents a -v command line option which should not be used. Do not use the -v command line option with CER.exe.
Definition of Advanced Data is not the same between DW.exe and CER.exe
An inconsistency between definitions exists between the Error Reporting Tool (DW.exe) and the Corporate Error Reporting tool (CER.exe). If global memory is requested, the CER tool incorrectly indicates that Advanced Data is requested. Global memory is treated as if it were Basic Data by the Corporate Error Reporting tool.
If you set the policy Allow Basic Data Collection to checked and the Allow Advanced Data Collection policy to unchecked (using either the Default Policy dialog or Selected Buckets' Policy dialog) the following will occur for any content governed by the policy setting.
When a memory dump is requested by Microsoft, the memory dump is collected from users and reported to Microsoft when an administrator clicks “Report”
Organization Name field in CIW is not active for Language Pack MSI files
Though the Organization name field in the Custom Installation Wizard is available to administrators when creating a transform for a LPK.MSI, has no effect when a transform has this field set with a different value and is applied as part of an installation of a language pack.
Terminal Server and Clips feature installation state from Media Content CD
Installation of Media Content from the Media Content CD should not use the default installation state when installing to a Terminal Server system directly from a CD (not installed from an administrative installation point). The default installation state for Clips is Run from CD when installed directly from the Media Content CD. Install Clips to a drive using the Run from My Computer installation state so all users have access, or create an administrative installation point and install the Clips/Media Content from that location using a transform created by the Custom Installation Wizard. Be sure to use the Run from My Computer installation state for the Clips feature of the Media Content CD. It is not advised to make further changes to the remaining pages in the wizard.
Custom Maintenance Wizard now recognizes "versioned" maintenance files
The Custom Maintenance Wizard uses versioning to make sure it only applies and modifies maintenance files (.CMW) created specifically by the correct version of the wizard. Older maintenance files, including Beta release versions of maintenance files, cannot be used with this version of the Custom Maintenance Wizard.
You can check the version of the maintenance file by examining the version data in the header of the file using the CMW File Viewer.
Outlook requires %USERPROFILE% environment variable to configure user accounts but this environment variable is not defined on Windows 98 or Windows Millennium systems
Please see the Custom10.hlp Outlook: Customize Default Profile, Personal Folders File (PST) Settings, and Microsoft Exchange Server (Exchange tab) topics for further information regarding this issue.
Installation URL for Instant Messaging (an Outlook setting) does not work when set from the CIW or CMW Change Office User Settings page
If you use the System Policy Editor and set the Microsoft Outlook 2002 | Instant Messaging | Installation URL system policy and post the policy, the Installation URL for Instant Messaging works correctly. However, setting it in a transform using the CIW or a maintenance file in the CMW from the Change Office User Settings page does not work properly because Outlook does not examine the registry setting posted by either the CIW or CMW. Use the System Policy Editor to set the Installation URL policy for Instant Messaging.
Timeout on RPC calls for high latency (slow) networks with Outlook 2002
Outlook will prompt a user to cancel the RPC call to an Exchange Server if a timeout has occurred due to a slow network or high demand for the Exchange Server. To change the timeout value:
Use the Group Policy Editor, System Policy Editor, or Change Office user Settings page of the CIW or CMW and configure the Microsoft Outlook 2002 | Miscellaneous | Exchange Settings settings:
Set Disable cancelable RPC progress dialog to Apply Changes and set the Check to turn setting on; uncheck to turn setting off check box to checked.
Set Time before displaying cancelable RPC progress dialog to Apply Changes and set the Time to wait during any user initiated operation and Time to wait during background synchronization to the time values you would like to use.
Outlook 2002 does not resolve recipient names correctly
Administrators must deploy Outlook configured to use an Outlook Address Book (OAB) if they are using an Exchange Server profile (PRF) to configure user accounts. For example, as part of a default installation, administrators should deploy an Outlook Address Book (OAB) to allow proper resolution of recipient names to the Exchange Server Global Address List (GAL).
Setup INI Customization Wizard
Setup INI Customization Wizard fails when a chained msi is added
If you select to include an msi as a chained msi to the setup.ini, it may cause the Setup INI Customization Wizard to fail. To avoid this failure:
In the Specify options for each package in your INI file page of the wizard, use the keyboard or mouse to select (or review) each of the newly added MSI files and examine their advanced properties. By reviewing the options of the MSI file in the INI file, the system will not place NULL entries in the CmdLine property.
Automatic Repair of Office XP fails after an Operating System upgrade to Windows 2000 or Windows Millennium
This can occur if the computer used to capture the OPS file from (using the Office Profile Wizard) is running Windows 2000 or Windows Millennium. When the Office Profile Wizard reads in the registry contents from this system one of two registry values may be incorrectly added to the OPS file that when applied to the target computer will insert erroneous data to the registry of the target computer. If the target computer's operating system is upgraded after Office is installed, Office may not be repaired (as is required after an Operating System upgrade) due to the existence of either of these registry values.
The following registry values may suppress automatic repair of Office after an operating system upgrade:
HKCU\Software\Microsoft\Office\10.0\Common\General\
Value Name: InstalledOnWin2K
- or -
Value Name: InstalledOnWinME
These registry values are not excluded by the OPWAdm10.ini file used by administrators to create OPS files. To correct this situation, instruct the Office Profile Wizard to not collect these registry values from the administrators test computer by adding registry values to the INI file used to create OPS files (OPWAdm10.ini). If you wish to ignore these registry values in the INI file, add the following entries to the [ExcludeIndividualRegistryValues] section in the OPWAdm10.ini.
HKCU\Software\Microsoft\Office\10.0\Common\General\InstalledOnWin2K
HKCU\Software\Microsoft\Office\10.0\Common\General\InstalledOnWinME
Features requiring a repair may or may not be installed on a user's computer depending on the deployed configuration of Office. Therefore, users may or may not experience problems with the use of Office applications after a suppressed repair because the feature that would cause a problem is not installed. In case an OPS file does cause a problem, it is possible for users to perform a manual repair by selecting Help | Detect and Repair… | OK from any Office application.
Content within this section will appear in future releases of updated reference materials and will be available as downloads from the Office Resource Kit website.
In the CER.HLP help file, the topic Command line options for Corporate Error Reporting should be changed to read.
Corporate Error Reporting allows for one command line option, -r.
-r <path to File Folder Tree root> Automatically performs the equivalent of "Report" (File menu). Running Corporate Error Reporting with this command line option starts Corporate Error Reporting using the supplied path to the File Folder Tree and then automatically links to the Microsoft crash reporting server through the Internet and reports all the active bucket information.
Custom Maintenance Wizard Help
In the custom10.hlp for the CIW, CMW, and OPW help, an entry in the Add Program Entry / Modify Program Entry topic should be revised. The following line (the fourth entry under the third procedural step):
Run this program once for each user - Run this program only the first time this product is installed
This program runs for every user who logs on and starts an Office application, but will not run again, even if Office is reinstalled.
Should be changed to read:
Run this program once for each user - Run this program every time the product is installed
This program runs for every user who logs on and starts an Office application, and will run again for any user who reinstalls Office.
Documentation for the CIWEXTRASHORTCUTDIRS changed significantly and requires changes to both the custom10.hlp and setupref.doc. The following documentation found in both of these references should be amended from:
CIWEXTRASHORTCUTDIRS [string] - start menu path
Directs setup to search additional folders for Office XP custom shortcuts to be removed during maintenance mode or during an uninstall of Office XP. You can enter folder keywords for use with this property or specify a literal folder path. Separate multiple entries with a semi-colon.
Example
CIWEXTRASHORTCUTDIRS="<StartMenu\Programs\Startup>;C:\Office\Start Folder"
The previous reference should be changed to:
CIWEXTRASHORTCUTDIRS [string] - path1;path2;path3…
Directs setup to search additional folders for Office XP custom shortcuts to be removed during maintenance mode or during an uninstall of Office XP.
Paths without a supplied token at the beginning are not supported by this property
Path information must be relative to - and start with - a valid token (see list provided)
Multiple path entries must be separated with a semi-colon
Individual folders represented by these tokens are automatically examined to see if additional shortcuts are present whenever Office, or a feature of Office, is removed from the computer using Setup or Windows Installer. Folders represented by tokens are examined by default. This property is provided explicitly for removal of shortcuts from subfolders of the defined tokens. If you have placed additional shortcuts in subfolders of these token locations, then use this property to search and remove the shortcuts from these locations.
List of valid tokens:
<StartMenu>, <StarMenu\Programs>, <StartMenu\Programs\Startup>, <Desktop>, <ApplicationData>, <Favorites>, <NetHood>
Example
CIWEXTRASHORTCUTDIRS="<StartMenu\Programs>\CorpApps;<Desktop>\My Programs"
A note has been added to the bottom of the Default Installation Path definition in the Specify Default Path and Organization topic in the custom10.hlp.
A future update of this content will be available in the near future from the Office Resource Kit website.
Default installation path Path on the user’s computer where Office should be installed. You can specify a predefined installation path by entering a keyword in this text box (see keywords for a list). The string entered here is added to the INSTALLLOCATION property for setup. For more information about the property INSTALLLOCATION see the topic Properties for Office.
This entry is used as a dynamic keyword by the wizard. Several controls are automatically updated to reflect this path. For example, if you select the Remove Files tab in the Add/Remove Files page and select the Add… button, the Path and file name of file to be deleted on the File Path dialog will display this path. Changing this path in the future from the Specify Default Path and Organization page will automatically update all associated entries you have created using this dynamic keyword in the wizard.
Note The Custom Maintenance Wizard uses the <Program Files\Microsoft Office> token to reference the default installation path you define in this combo box. Do not use the custom string you may have created in this combo box within the CMW to reference this path. Instead, use the <Program Files\Microsoft Office> token available in the Destination path on the user's computer combo box (File Destination Path dialog) or Path and file name of the file to be deleted combo box (File Path dialog) in the CMW. This token represents the install path of Office on the user's computer regardless of where it was instructed to be installed by an entry in the Default installation path combo box.