OFF2000: Contents of the ORK Readme.doc File (Part 1 of 2)
PSS ID Number: Q230698 Article last modified on 06-02-1999
WINDOWS:2000
WINDOWS
======================================================================
The information in this article applies to:
- == Microsoft Office 2000 ==
SUMMARY
The Microsoft Office 2000 Resource Kit (ORK) contains a file titled Readme.doc that contains information about last-minute updates to the Office Resource Kit tools and documentation, as well as additional notes about Office 2000. The “More Information” section of this article contains the first-half of the text of the Readme.doc file.
The second-half of the Readme.doc text file is in the following article:
Q230775 Contents of the Readme.doc File in the Office 2000 Resource Kit (Part 2 of 2)
You can download the complete Readme.doc file by clicking the Readme.doc link at the bottom of the following Microsoft Web page:
http://www.microsoft.com/office/ork/2000/appndx/toolbox.htm
MORE INFORMATION
Office 2000 Resource Kit ReadMe
The Office 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 2000. The Errata section contains corrections to the Office Resource Kit documentation which were discovered after it was submitted for publication. Each Errata entry title contains the path (based on titles and headings) for discovering the location for correction.
Issues
16-bit applications - Excel 5.0 Converter Pack process installs incorrect files
If you run the Converter Pack on a system with Excel 5.0 installed, it will unintentionally install the files Xlqpw7.exe (Quattro 7/8 converter) and Openwb3.xla. If you attempt to run Xlqpw7.exe, it attempts to run in 32-bit mode. Xlqpw7.exe is a 16-bit utility and will not work in 32-bit mode. Delete these two files if you find them on your system after running the Converter Pack.
Always Install with elevated privileges - Policy issue
If you intend to use the “Always install with elevated privileges” policy setting for a users machine, take note that the “Always install with elevated privileges” policy is enforced on a users machine only if both instances of the policy in the Computer and User settings groups are set to ON.
To set the “Always install with elevated privileges” policies:
- Make sure the Instrl1.adm template is loaded into the System Policy Editor before you open any saved policy file.
- Open the Default Computer (or your specific Computer policy group) and select Windows Installer.
- Select the Always install with elevated privileges check box.
- Select the Check to force setting on, uncheck to force setting off check box.
- Repeat Steps 2-4 for the Default User group or for a specific user.
Banyan Vines Server - Cannot complete install of Office 2000
If you create an Admin image of Office 2000 on a Banyan Vines Server, and you want to install Office 2000 so the program files run from the network server instead of being installed to the users local drives, you must make changes to the install process. The problem stems from the Banyan Vines Server not being available after the Office 2000 setup process reboots to complete setup and configuration. If the Banyan Vines Server is not found, the install process aborts, leaving registration of several file types, and other lesser issues, unfinished. The following is an outline of the possible steps you can take to avoid this issue.
Note: This is not a tested and approved process, it is a suggested course of action and is up to the administrator to resolve any issues not covered in the outline.
- Change the REBOOT property on the Setup command line to REBOOT=ReallySuppress.
- In the Windows registry, move the Windows Installer RunOnce command from the HKEY_LOCAL_MACHINE Microsoftsubkey to another private registry key (any key you create in the HKEY_CURRENT_USER registry key will suffice) or save it to a file on an available drive so after rebooting you can read it back into your program after restarting.
- Reboot the system.
- After the system reboots and the network connection is established, start the Windows Installer with the command line saved in the private key or file (from Step 2).
- Delete the temporary registry key or file (from Step 2).
Beta installs - Admin image install error
If you have been part of the beta testing of Office 2000, you may encounter the following error message if you are performing an install using the /a setup option:
Error 1316: A network error occurred while attempting to read from the file <path>.msi.
To avoid or correct this situation, be sure to completely remove (uninstall) any previous beta releases of Office 2000 prior to performing an install from an admin image.
Changing installation states after Office installation - Filelist.xls - Feature tree list and hidden features
When you configure an initial installation of Office 2000 using a transform, you may want to hide features you do not want deployed during the initial setup. Hiding features forces a user to see only the features (software and components) you choose to reveal. Visible features appear in the Add/Remove Programs utility. If you do not hide features you are not ready to deploy, users have the ability to install or modify them through the Add/Remove Program utility at any time - before you are ready to deploy the additional features or applications.
There is a condition involved with hiding features. After you deploy a feature using the PropName=PropValue method, it remains hidden from the user in Add/Remove Programs. This has no affect on the functionality of the feature, only on the user’s ability to configure it after installation.
If you modify the following property entries in the Setup.ini file [Options] section; ADDLOCAL, ADDSOURCE, ADVERTISE, or REMOVE, you must use the feature names found in the Filelist.xls file [<install path>Lists Samples] to create valid PropName=PropValue pairings. Several features listed in this spreadsheet do not appear in the feature tree list of the Custom Installation Wizard and are noted in this spreadsheet. If you install the parent feature, you must also specify any of the related hidden features you want to install in the appropriate Property list.
“Hidden features” refers to any features authored in the .msi file to never be displayed in the visible feature list within Setup or the Custom Installation Wizard (CIW). This does not apply to features you have selected to hide within the CIW.
Note: There will be an updated version of the Filelist.xls available on the Office Resource Kit web site http://www.microsoft.com/office/ork). This update adds a new sheet in the Workbook containing a hierarchical list of all feature names, including the authored hidden features described above.
If you add features to these command line entries, you are restricted to a 1024 character limitation for each line (ADDLOCAL, ADDSOURCE, ADVERTISE, or REMOVE). If you need to include more features, you must create multiple Setup.ini files and link them together using a batch file. For example:
start /wait setup.exe /wait /qb /settings setup#1.ini REBOOT=ReallySuppress
start /wait setup.exe /wait /qb /settings setup#2.ini REBOOT=ReallySuppress
start /wait setup.exe /wait /qb /settings setup#3.ini REBOOT=ReallySuppress
start /wait setup.exe /wait /qb /settings setup#n.ini REBOOT=Force
See the topic “Setup.exe and batch files - using the ‘start /wait’ prefix” for further information on the use of start /wait.
You must use the Setup.exe available with the Office Resource Kit toolbox. See the topic “Setup.exe - Recommended upgrade version available with Office Resource Kit” for further information.
Also, as part of the Office Resource Kit, is an executable you can include in your batch file for forcing a reboot of your computer. Reboot.exe, when run, will shutdown windows gracefully and then force a hard boot restart of your computer. Look in: [<install path>Definition Files] to find reboot.exe.
Configure Office Collaboration function - Internet Information Server 4 - Unavailable for use
If you attempt to select the “Configure Office Collaboration function” option of Internet Information Server (IIS 4) (right-click on the Default Web Site, select Properties, select Server Extensions tab from the Default Web Site Properties dialog) the feature is grayed-out and unavailable. There is no way to enable this option, however you can get to the intended function by entering http://name of machine/msoffice/msoadmin in the URL textbox of Internet Explorer or by choosing Run from the Start menu and typing the appropriate string.
Error applying transform error message
If you configure an install of Office to begin from a Web hyperlink, you may encounter the following error:
Error applying transforms. Verify that the specified transform paths are valid.
This is due to an issue with Windows Installer not properly resolving the relative path of the source. See the topic “Setup.exe - UNC versus Drive letter startup issue” for further information. To avoid this issue, specify the full path to the .mst file and not the relative path.
Excel - Two-digit year always expands to four-digit year with all Far East operating system languages
When using Excel with Far East operating systems, entering a date with a two-digit year always expands to a four-digit year. There is no work around for this issue.
Excel 4 - High Security and .xlm add-ins
If you plan on using Excel 4 style macros (.xlm) you will need to add a registry entry to enable their use if you also plan on using High Security. Excle .xlm macros cannot be digitally signed and cannot load when High Security is enabled. Some Excel add-ins were created using .xlm. To allow add-ins written as .xlm macros to run as exceptions under High Security with Excel 2000, add the following registry entry.
[HKEY_LOCAL_MACHINE \9.0] XLM 1 - dword
Creating and setting the “XLM” registry DWORD value to 1, allows users to load .xlm macros. Setting this value to zero defeats this feature and returns to the default behavior.
When this registry entry is added and set to 1, the end-user receives a warning about .xlm macros and has the option to open the workbook. End-users should run a virus heck on any .xlm prior to using it. Even though .xlm macros are allowed through the High Security check, the High Security feature for VBA macros is still enabled.
Use of this option is similar to that of Medium Security except it allows for automatic and silent disabling of non-signed VBA macros (a feature of High Security). The administrator of the machine can force the running of signed and trusted VBA macros, but also allow exceptions for Excel 4 macros. If this option is used, users should be educated about Excel 4 viruses and how they are enabled if the workbook is opened.
Note: Addition of this registry entry provides no indication through the User Interface to the end user that the system is running a modified/lesser version of High Security.
Excel Microsoft Query - Intllimit.xls - error regarding Traditional Chinese codepage requirements
Intllimit.xls contains an entry for Excel Microsoft Query stating “Traditional Chinese user interface available on Traditional Chinese system locale only.” This is an unnecessary entry. Microsoft Query is ANSI format and must match the system code page. If it does not match the codepage, it defaults to English.
Far East languages - Non-core international support files - User interface corruption with Windows NT 4.0 (with SP 4) in locked-down configuration with Active Desktop
If you install the MultiLanguage pack using the /j setup option (to deploy Office 2000 and the Language Pack) and have Active Desktop, then change the codepage/language settings from any non-Far East language to a Far East language, like Chinese or Korean, your User Interface will corrupt when you start any Office 2000 application. This is due to National Language Support (NLS) files not being copied to the system during setup by default. When the Office Tools, International Support Files, and core support files are installed locally, the issue is resolved.
Find Fast - May cause unresponsive system
If you use Find Fast, be aware that it is a disk-intensive program. It may appear to suspend applications when it begins to index a drive, and may degrade performance for all drives indexed. It is recommended to reduce the indexing interval from the two-hour default, to at least an eight-hour period. It is even advised to reduce it to once in a 24-hour period and to have it run during a time when a user is not present on the system.
It is also recommended to not run Find Fast on a server during a period of expected usage by client systems since it will give the appearance that the server is down or unavailable.
Find Fast - Does not automatically create an index for each local, fixed volume after initial installation.
If you want Find Fast to automatically create an index for a specific drive, you must manually add or modify, the registry entries for the following key. During installation of Office 2000 the Find Fast indexes are not created by the Windows Installer process.
[HKEY_LOCAL_MACHINE\9.0 FastList] Folder[DrivePath] <— Replace with drive name (i.e. "C:")
Type 0 dword Property Cache 1 dword Automatic 1 dword Index Operation 1 dword
After creation or modification of this registry key, open the Find Fast application in the Control Panel. If you successfully created or modified the registry key, it will automatically begin creating an index file of all files present on the drive you specified in the “Folder” entry of the key. An index is not created until you run the Find Fast utility in the Control Panel or Find Fast is started by the Office Startup Assistant (osa9.exe -b -l). Reboot the computer to validate that Find Fast has been added to background tasks and examine the Task Manager for FindFast.exe.
Note: FindFast is a disk intensive program when it is indexing a drive. It may even appear to stall a drive when it is indexing. It is advised to increase the indexing interval to once in an eight-hour period of time, for instance, once at the beginning of the day, or at a time when the user is away from the computer.
Folder.asp - Active Server Page - AutoNavigation, Encoded characters in the URL
If you use the AutoNavigate viewing feature of the Folder.asp and access the string variable returned by the ActiveURL or CurrentURL properties, examine the URL to make sure it does not contain any encoded characters. You cannot use the URL as returned by the ActiveURL or CurrentURL properties if they contain encoded characters. The reason for this is that most non-alphanumeric characters in a URL become HTML encoded characters after they are submitted to the AutoNavigate feature. The characters are translated to the
%xx
HTML encoding protocol, where xx is the HTML encoding number for the given non-alphanumeric character. Any URL with an HTML encoded character is incompatible with processes/functions/methods not capable of interpreting HTML encoding of this format and should be converted prior to use.
If you intend to use the string within either of these two properties with external processes, convert all encoded characters back to their original form before submitting them.
Non-alphanumeric characters are:
@ : ; < > " # % { } | \ ^ ~ [ ] ` , & + = $
and any characters between 0x00-0x1f (ASCII 0 - 31) and 0x7f-0xff (ASCII 127 - 255)
HTML Help - does not work if Internet Explorer 5 is not installed/upgraded
If the administrator sets a policy to install all of Office 2000 with elevated privileges (Always install with elevated privileges - Instlr1.adm), but decides not to install/upgrade Internet Explorer 5 on a Windows NT 4.0 system, HTML Help will not work with Office. To correct this situation:
Log onto the user’s system as an administrator (or with administrator privileges).
From the Command Prompt (MS-DOS window) move to the Internet Explorer 5 setup directory in the Admin image created on the server.
Enter the following command line:
ie5setup.exe /c:“ie5wzd.exe /m: /q:a /r:n /E:Gensetup,HTMLHelp /s:”“#e”""
- or -
Add the Ie5setup.exe command line option to the end of a setup batch file so it is run after Office 2000 has completed installation.
Run this process immediately after Office 2000 is installed to the user’s system.
HTML Help - Hyperlink failure with Office 2000 on Netscape Navigator browser only systems
When a computer is configured to use Netscape Navigator exclusively (and Internet Explorer is disabled by the Proxy server), Office 2000 will encounter an error when attempting to execute an HTML Help hyperlink jump within an Office application. You can add or modify the following registry key entry to correct the error.
[HKEY_CURRENT_USER\9.0 ] “ForceShellExecute”
1 - dword
Change the ForceShellExecute entry to 1.
Internet Explorer Administration Kit (IEAK) - Custom Installation Wizard (CIW) silent install issue.
The installation selection for the Custom Installation Wizard (CIW) always includes the separate installation of the IEAK. Since the IEAK Setup is performed silently, it always is installed in the default location. This can have several side effects:
- If you currently have a version of the IEAK version 4 installed in the default location, the IEAK version 5 install overwrites the existing install with the new version. The IEAK version 4 setup does not offer the ability to change the install location.
- If you have installed the IEAK version 5 from the Web, you may have a later version than that supplied with the Office Resource Kit. In this case, when you install the Office Resource Kit and reach the IEAK portion of the installation you will see a standard “Confirm File Replace” dialog. To preserve your later version of the IEAK answer “No to all”. If the version you installed from the Web is older it will automatically be updated to the newer Office Resource Kit version.
Internet Explorer 5 - Windows NT 4.0 locked down - Install order prevents use of oleaut32.dll
If you install Internet Explorer 5 on a locked-down Windows NT 4.0 system prior to installing Office 2000, you will encounter a problem after Office 2000 is installed. Installing Internet Explorer 5 prior to Office 2000 sets the oleaut32.dll to a permission setting other than Everyone. When this happens, some DLLs will not run (i.e.: riched20.dll, stdole.dll) and will cause PowerPoint and sections of Word to spawn alerts and error messages. This is not an issue if Internet Explorer 5 is installed with Office 2000.
To correct this issue, if Internet Explorer 5 was installed prior to Office 2000, set the oleaut32.dll group permissions to Everyone.
Internet Explorer 5 - Internet Connection Wizard, restricted from running
If you are using Windows NT 4.0 with Service Pack 4, or Windows 2000, you may encounter the following error the first time you attempt to use Internet Explorer 5 if you log on to your system without administrator privileges.
Access Denied: You are restricted from running the Internet Connection Wizard because you are not an administrator on this machine.
In order to avoid this message, you must log on with Administrator privileges when you decide to run Internet Explorer 5 for the first time. When the Internet Connection Wizard completes, and Internet Explorer 5 has access to the web, you no longer are required to logon as an administrator.
Internet Explorer 5 - .ocx installation/download under Windows NT 4.0 Service Pack 4 with high security option
When using Internet Explorer 5 on a Windows NT 4.0 system with Service Pack 4 installed, you will not be able to install an .ocx control when NT security is set to High. Since many Web sites download .ocx’s, you should consider the tradeoff between functionality and security. Setting security to any level below high allows .ocx controls to install.
Internet Explorer 5 - Requires extra reboot after install on systems with Lotus Smart Suite
If you are installing Internet Explorer 5 to a system with Lotus Smart Suite already installed, there is a possibility you may require an extra reboot. This is not a problem, it is by design to overcome a lock on the Wininet.dll by Lotus Smart Suite. If you have Internet Explorer 4.0 or 4.01 already installed on the target system, you will not encounter this issue.
Language settings - LCID not removed after uninstall of Office 2000
If you install US Office 2000 on a localized operating system, and then later uninstall it, the uninstall process does not change the LCID back to the settings of the localized operating system. If you then install a localized version of Office 2000, you will have the wrong settings and will encounter problems with codepage dependent applications and utilities. To correct this situation, run Langver.exe and set the LCID to the correct settings for your localized operating system (or use the /LCID Auto command line option with Langver.exe). For more information, see the Readme topics “Langver.exe - Setting LCID from within a batch file process” and “Langver.exe - Possible language settings corruption.”
The following table summarizes the different scenarios for mixed language installations of the operating system and Office 2000.
Operating First Upgrade or Need Comment System Installation Reinstallation Langver ———————————————————– Localized English O2K Localized O2K YES Use to set Install Language to Local language
Localized Localized O2K English O2K YES Use to set Install Language to English
Localized Localized English NO Install Language will be App X App Y localized and English app will behave correctly
Localized English Localized YES Use to set Install App X App Y language to Local language
Localized Localized Localized NO App X App Y
Localized English English NO App X App Y
US English Optional Use to set all defaults Office + LPK to a specific language (for advanced users only)
US English Localized Not Not a supported Office Office Supported configuration.
Langver.exe - Possible language settings corruption
When using Langver.exe, there are instances where possible unintended side effects may cause corruption of user preferences/settings, operating system settings, and/or application startup configuration. Langver.exe is only for use with:
- English version of Office 2000 with the MultiLanguage pack installed on a localized operating system.
- Mix of English version of Office components and localized components, where a localized component was installed after the English version was installed.
Use of Langver.exe on localized systems can corrupt the MAPI, encoding, spell checker, proofing tools, sorting, localized add-ins, and wizards. Use of Langver.exe on non-English operating systems with incorrect settings, forces Office 2000 to run in “fall-back” mode. Fall-back mode might cause incorrect startup of Office, use of the wrong version of Help, or the display of the incorrect User Interface. If you need to change settings for Office, use the SetLang.exe utility to adjust language settings. Using SetLang.exe protects the user from unintentional changes to language critical settings.
LCID - Setting LCID from within a batch file process
If you need to specify the LCID for Office from a batch process, you can use the Langver.exe utility and add a command line option. The option /LCID can accept either the LCID (example: langver /LCID 1041) or “Auto” (example: langver /LCID Auto). Any entry not recognized by Langver.exe as a valid LCID is ignored.
Specifying the /LCID option on the command line disables the User Interface for the utility.
If you run Langver.exe with the /LCID Auto option, Office configures itself to the language used by the operating system. This option is different than just starting the utility without the /LCID option. Starting Langver.exe without /LCID displays the UI, and if you select OK, it keeps your current settings (without defaulting to the operating system settings). If you run with /LCID specified, it will reset the system to the operating system settings (which may be different than what you had originally set through the UI).
If you use Langver.exe, consider any unintentional effects to the Normal.dot template of Word 2000 by a change to the LCID and any user settings, which may be overwritten because of this change. If you run Langver.exe, it resets the Normal.dot to the new language/codepage settings and will delete any previous language settings.
Macro Security - Security set to High still allows users to override customized settings
When macro security is set to High, it is still possible for a user to override customized settings. It is possible for a user to select the checkbox “Always Trust this Source” option and set it to True when the system asks a user to accept a given executable from an external source, thereby allowing a possible virus to enter into the system. To prevent this, move the trusted list from the [HKEY_CURRENT_USER VBA] key entry to the [HKEY_LOCAL_MACHINE Microsoft] key entry and remove the list from the previous key entry. This does not change the Checkbox State in the interface, but it does keep the user from enabling macros the administrator has chosen to avoid.
MAPI - Failure with Internet Explorer 5
If you have an .ocx making calls into the MAPI (Microsoft Messaging Application Programming Interface) to create and send automated mail messages, you will encounter an error when Internet Explorer attempts to use this .ocx. The error is due to CDO (Collaborative Data Objects) not being registered or installed. To avoid this issue, install CDO.
MultiLanguage Pack installation - US and MultiLanguage packs single install example
If you need to install Office 2000 and the MultiLanguage pack in one step, use the following process.
Create an admin image of Office.
Create an admin image of the MultiLanguage Pack.
Replace the Setup.exe in the MultiLanguage Pack admin image with the new version of Setup.exe found on the Office Resource Kit.
You can get the new Setup.exe from the Office Resource Kit CD-ROM (<CD Root>: .EXE), or you can download it from the Toolbox in Office Resource Kit Web site at http://www.microsoft.com/office/ork/.
Warning: Do not change the Setup.exe in the Office admin image.
Create a transform for Office using the Custom Installation Wizard.
On the Add Installations and Run Programs panel of the wizard, add the command line to install the Language Pack and include the new /chained option. For example:
<fully qualified UNC and path>setup.exe /chained TRANSFORMS=lpksettings.mst
Deploy Office using this custom transform.
When the Office install completes, the MultiLanguage pack installation will begin automatically.
Using the /chained option results in the MultiLanguage pack install waiting until the Office 2000 install is completely finished before starting. The one requirement is for the Office install to finish completely. You can also use this same Office 2000 transform to make other customizations to your Office 2000 deployment. For example, you can add custom files, registry keys, or any customization allowed by the Custom Installation Wizard.
Note: You can also use the chained Setup.exe when creating a transform for the MultiLanguage pack to start the installation of a second MultiLanguage pack CD or even another product. It is possible to chain many installs together by using this mechanism, however, it is recommended to only chain a few.
ODBC - Translation error on a locked-down system
If you attempt to use ODBC on a locked-down system with an upgraded MDAC of version 2.1 (the version shipping with Office 2000), you may encounter an error if you are using Jet database drivers from Office 95 (DAO 2.5, Access 95) and earlier versions. During the first attempt by an application to open a system Data Set Name (DSN), the driver attempts to upgrade the DSN. This process fails when it attempts to open the registry key [HKEY_LOCAL_MACHINE] because the application does not have permission to write to this registry key. The driver fails to load, and then displays the Translation Error message. To avoid this condition, install MDAC version 2.5 (shipping with Windows 2000).
As a workaround to this situation, an Administrator would need to:
Remove the offending DSN before upgrading and then recreate the system DSN after the upgrade.
-or-
Open a connection with administrator privileges using the DSN (in order to have permissions to rewrite content).
-or-
Allow write permissions to the [HKEY_LOCAL_MACHINE] portion of the registry by all users.
User-created DSNs do not encounter this issue since DSNs created by users are in the [HKEY_CURRENT_USER] key and users have access to this registry for read/write.
Office 2000 - Run From Network (RFN) uninstall fails if source files are not available
If you install Office 2000 configured to run from the network, and later choose to uninstall it, the source install point must be available in order to have Windows Installer properly remove the application from the client’s local system. If the source install location is not available to the Windows Installer program, it will not remove the installed files on the user’s local system.
Office 2000 - Does not start
If you run setup with the /jm option (advertise) on a locked-down system to advertise Office 2000 but the user installs Office 2000 from a non-administrator install point (for instance, the CD), Office 2000 will not start. To avoid this issue, install Office 2000 from the administrative installation point created by the administrator.
Office 2000 - Unexplained shutdown after startup
If a non-administrator installs an Office 2000 image on a locked-down system using the /j or /jm setup option, when Office 2000 is installed to a clients system and started by a user (and asked to register), it may shutdown after what appears to be a normal startup. This is a license verification issue and is by design. Applications loaded to a locked-down system are expected to have been placed there by an administrator. After the administrator has created the image and registered it using the product verification number from the CD, the application should be available for use without requiring the product registration number.
Office User Data - Office 2000 user configuration settings retained after uninstall
If you intend to uninstall and then reinstall Office 2000 (or any components of Office), all previous information regarding user configuration and User Interface settings are retained (not deleted from the registry during uninstall). This allows the user to retain their personalized settings in the event they must uninstall Office, and then install again later.
The initial Office Setup writes required default user related settings during installation. You can force a reset to defaults for these settings for any subsequent reinstall of Office. To do so, you must delete the UserData entry from the following registry keys:
[HKEY_CURRENT_USER\9.0] [HKEY_CURRENT_USER\9.0] [HKEY_CURRENT_USER\9.0] [HKEY_CURRENT_USER\9.0] [HKEY_CURRENT_USER\9.0] [HKEY_CURRENT_USER\9.0]
The absence of the UserData value from any of these keys instructs Office to recreate the default settings for the related application - resetting any user modifications - during a subsequent install.
Note: The settings affected by these entries can be viewed under each of the named keys after Office is installed - and before any of the applications are booted. Each application may write additional settings at first boot time, which are not controlled by the UserData values.
Additional query words: OFF2000
====================================================================== Keywords :
Version : WINDOWS:2000 Platform : WINDOWS Issue type : kbinfo ============================================================================= Copyright Microsoft Corporation 1999.
