Microsoft KB Archive/230775

OFF2000: Contents of Readme.doc in the ORK 2000 (2 of 2)

PSS ID Number: Q230775 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 readme file called Readme.doc. This file contains information about last-minute updates to the Office Resource Kit tools and documentation as well as additional notes about Office. The “More Information” section of this article contains the second-half of the text of the Readme.doc file.

The first-half of the Readme.doc text is in the following Knowledge Base article:

Q230698 Contents of ORK Readme.doc File (Part 1 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 =

OSA9.exe - Office Startup Assistant command line options

Office Startup Assistant (OSA) launches various Office 2000 utilities and features (e.g. FindFast, Office Shortcut Toolbar (OSB), New Office Document, Open Office Document). It also provides boot time initialization benefits for applications by initializing common fonts and OLE. OSA is designed to launch Office utilities at login time. This happens when Setup.exe adds the shortcut “osa9.exe -b -l” to the user’s startup group. The -b and -l command line options launch FindFast and OSB based on the user’s registry settings. It also provides an entry in the start menu for the “Open Office Document” (-f) and “New Office Document” (-n) dialog shortcuts. OSA can launch OSB (-o) or the current screen saver (-s). In a Run From Network environment, it is recommended to install OSA to the local system, especially if Outlook is installed locally as well.

-b Start the Office Shortcut Toolbar (when used in conjunction with -l) -f Start the Open Office Document (File Open/Save As dialog) -l Start FindFast -n Start the New Office Document dialog -o Start the Office Shortcut Toolbar -s Start the current screen saver.

OSA will launch the OSB if the following registry setting is present:

HKEY_CURRENT_USER\9.0Bar AutoStart 1 - dword

OSA will launch FindFast if FindFast.exe is present and the following registry is not present:

HKEY_CURRENT_USER\9.0NotFindFast 1 - dword

Typically, when OSA9.exe is present in the startup folder, it has the -b and -l switches set (osa9.exe -b -l).

OSE/Frontpage/Windows 2000 - No access to Web Server registry keys with Windows 2000

If you logon to a Windows 2000 system and try to change any features which attempt a write or edit of the Web Server registry keys, the changes will not succeed. With Windows NT 4.0 this is not an issue. The increased security configuration for Windows 2000 allows only Power Users and above to have Full Control access to the registry. To avoid this issue, log on with at least Power User privileges prior to adding any application making modifications to Web Server registry key entries. If it is not possible to logon as a Power User, but you still want OSE admins to have write access to the registry, have the machine administrator perform the process listed below.

  Start regedt32.   Select or add the following subkey. HKEY_LOCAL_MACHINE\9.0Server   On the Security menu, click Permissions, and then click Add.   Select the OSE Admins group   Click Add.   Set Type of Access to Full Control and click OK. </li>  Select the Replace Permission on Existing SubKeys check box and click OK. </li></ol>

Outlook - Data loss with versions prior to 8.02 when accessing PST files of Outlook 9x and Outlook 2000

If users with Outlook 2000 have a personal folder file (PST) with any individual folder containing 16,000 or more items and the “Allow Large Tables” feature is enabled, they will encounter data loss if they roam to the PST from a version of Outlook 8.02 or earlier. You should upgrade all computers to a release of Outlook 8.03 or higher if you want to avoid this issue. If you do not upgrade, users should be told to reduce the number of entries in all individual folders to less than 10,000. This issue also applies to e-mail archived or autoarchived to a PST by Outlook 9x or Outlook 2000 and accessed from any version of Outlook earlier than 8.03.

Outlook 2000 - Does not run locally if Office 2000 is installed as Run From Network and network share is unavailable

If you are using the Custom Installation Wizard (CIW) to install Office 2000, and you have the top branch in the CIW set to “Run from Network,” but set Outlook 2000 to install with “Run all from My Computer,” Outlook will not run if the network share for Office 2000 is unavailable. Shared files used by Outlook are present on the Office 2000 server share and cannot be accessed. To avoid this issue, set the top node to “local.”

Outlook 2000 - Terminal Server - NetMeeting does not work

If you attempt to use NetMeeting with Terminal Server, it will fail. It is recommended you remove NetMeeting from computers using Terminal Server by running the Add/Remove program in the Control Panel. Outlook 2000 - Terminal Server - OLE embedding failures in email messages If a Terminal Server connection is established using the Client Connection Manager (CCM) to run Outlook on a server and the “Prompt me for a profile when starting Outlook” is checked (the default), OLE embedding features will not work. The failure is associated with multiple simultaneous connections and an OLE configuration issue. To avoid this issue, install the latest Terminal Server Service Pack, available from the Windows NT Server Downloads page on http://pbsweb2/NTServer/all/downloads.asp. This update to Terminal Server prevents “Multiple Outlook Sessions” from being started. Outlook 2000 - Terminal Server performance issue To increase the performance of Terminal Server, it is recommended that you disable the “Publish Calendar to Web” option within Outlook. If you want to use the Publish Calendar to Web feature, you must first unlock the [HKEY_CLASSES_ROOT] registry node so users will have write access to this segment of the registry. To unlock the [HKEY_CLASSES_ROOT] and allow users access to the CLSID keys: 1. Log on to the Windows Terminal Server computer as the administrator. 2. On the Start menu, click Run. 3. Type regedt32.exe and click OK. 4. Under HKEY_CLASSES_ROOT, select CLSID. 5. On the Security menu, click Permissions. 6. In the Registry Key Permissions dialog box, select the Replace Permission on Existing Subkeys check box, and then click Add. 7. In the Name box, click Everyone, click Add, and then click OK. If you do not want to give all users this access, you can add specific users or groups of users in the Name box, rather than selecting Everyone. 8. In the Type of Access box, select Special Access, and then select the Query Value, Set Value, and Create Subkey check boxes. 9. Click OK and close the Registry editor. Outlook 2000 Custom Forms - Not accessible from locked-down Windows NT 4.0 systems If [HKEY_CLASSES_ROOT] is locked-down (not writable), MAPI forms cannot be added to the system. To avoid this issue, do not lock down this registry key until after all forms are installed. To avoid future problems with applications attempting to register controls and forms in this registry key, consider not securing the [HKEY_CLASSES_ROOT] registry key. This issue is also a concern for Outlook when used in a Terminal Server environment, since many different configurations of Outlook with Terminal Server and forms may be required by different users. It is recommended that you do not secure this registry key. This is especially important if users are creating custom forms and need to register them after creation. If you need to register custom forms on a locked-down system, you will need to logon as an Administrator and register the control (since Administrator privilege can update the registry key). Keep in mind, some custom forms can attempt to write to the [HKEY_CLASSES_ROOT] registry key during use (even though they are registered, the design of the custom form accesses and modifies content in the registry for the given form during use). Forms of this type will not work on a locked-down system and should either be redesigned or the registry key should not be secured. Outlook 2000 IMAP accounts - No means to configure with the Custom Installation Wizard (CIW) Currently, no method exists to configure an Outlook Internet Mail Access Protocol (IMAP) account using the Custom Installation Wizard. To add IMAP as a service to Outlook 2000: 1. On the Tools menu, click Services, click the Services tab, and then click Add. 2. In the Available information services box, click Internet E-mail. 3. Click OK. 4. Enter required information on all tabs in the Mail Account Properties dialog box. 5. Exit Outlook and then restart to initialize the new settings. Outlook 2000 Meeting Calendar - Meeting disappears from calendar If a delegate deletes a user’s meeting request after a meeting has been placed in the user’s calendar, the user’s meeting request will display “This meeting is not in the Calendar; it may have been moved or deleted.” To avoid this issue: - Configure the delegate to be the only one who receives meeting requests. The user will not receive any meeting requests. -or- - The delegate should not delete meeting requests. This should be a decision the user makes (a procedural issue, not a software configuration issue). Outlook 2000 Meeting Calendar - Two instances of same meeting If an Outlook calendar is configured to receive meeting requests and has a delegate who also receives meeting requests, it is possible for duplicate meetings to appear in the user’s calendar. To avoid this, have users use their online Calendar (not a local Calendar). To set this Calendar option: 1. On the Tools menu, click Options, and then click the Preferences tab. 2. Click the Calendar Options button. 3. Clear the Always use local calendar check box 4. Exit Outlook and then restart to initialize the new settings. Outlook 2000, Schedule+, and Terminal Server – Unable to view Schedule+ calendar with a Terminal Server connection If you attempt to use Outlook 2000 through Terminal Server and open a meeting request and direct book a Schedule+ account, you will encounter an error message “Cannot log on to Microsoft Schedule+. Unable to direct book a resource for this meeting.” To avoid this, unlock (allow write access by affected users) the following registry key: [HKEY_LOCAL_MACHINE+ ] Outlook versions prior to Outlook 2000 - Loss of data when roaming between earlier versions If users roam and use different versions of Outlook, data loss may occur when using Exchange Servers. If roaming is important, it is best to facilitate a quick migration from earlier versions of Outlook to Outlook 2000. If upgrading is not possible, users who roam between earlier versions of Outlook and Outlook 2000, must be aware that data loss will occur when the expanded functionality of Outlook 2000 meets with the limitations of earlier versions of Outlook. Password Protection - Disabling user access within the Save As/File Open dialog If you need to disable the setting of password protection by users for Word or Excel files, you can disable the Password option by changing the policy in the Word or Excel user policies. This process turns off features in Excel. Use only if it is absolutely necessary to disable password protection. Before you disable the password setting option in Excel, make sure you have loaded the Excel policy templates. Note: Do not load an existing policy until the policy templates have been added to the System Policy Editor. To load the Excel policy templates: 1. On the Options menu, click Policy Template, and then click Add. 2. In the Open Template File box, navigate to the Windows directory (for example, WINNT, WINDOWS, WIN, and so on) and then to the INF subdirectory. 3. Select the Excel9.adm file and click Open to add it to the template list. 4. In the Policy Template Options box, click OK. To disable the password setting option in Excel: 1. On the Start menu, point to Programs, point to Microsoft Office Tools, point to Microsoft Office 2000 Resource Kit Tools, and then click System Policy Editor. 2. On the File menu, click Open Policy to use an existing policy, or click New Policy to create a new policy. 3. Double-click the Default User icon (or any other user or group that you want to set policy for). 4. In the Properties box, select the following policy: Microsoft Excel 2000 | Disable

items in user interface | Custom | Disable command bar buttons and menu items. 5. In the Settings for Disable command bar buttons and menu items area, click Show. 6. In the Show Contents box, click Add. 7. In the Add Item box, type 4108, and then click OK. This is the control ID for the General Options (Tools menu). 8. In the Show Contents box, click OK. 9. In the Properties box, click OK. 10. Save your policy settings. Before you disable the password setting option in Word, make sure you have loaded the Word policy templates. Note: Do not load an existing policy until the policy templates have been added to the System Policy Editor. To load the Word policy templates: Note: This procedure also disables access to the Tools | Options as well as the File Save As | Tools | General Options menu options. This restriction can present a major inconvenience to users. 1. On the Start menu, point to Programs, point to Microsoft Office Tools, point to Microsoft Office 2000 Resource Kit Tools, and then click System Policy Editor. 2. On the File menu, click Open Policy to use an existing policy, or click New Policy to create a new policy. 3. Double-click the Default User icon (or any other user or group that you want to set policy for). 4. In the Properties box, select the following policy: Microsoft Word 2000 | Disable items in user interface | Predefined | Disable command bar buttons and menu items. 5. In the Settings for Disable command bar buttons and menu items area, select Tools | Options. 6. Click OK. 7. In the Properties box, click OK. 8. Save your policy settings. PowerPoint 2000 - Presentation Broadcasting feature does not work (aka: Windows Media Technologies server (NetShow) When you attempt to run the Presentation Broadcasting feature of PowerPoint 2000 as a broadcasting server, it will not work. Office 2000 does not ship with the OnLBroad.exe file to enable Presentation Broadcasting from within PowerPoint 2000. To install this feature, connect to the following Web site http://www.microsoft.com/ office/ork/ to download and install the OnLBroad.exe or examine the tools folder of the CD. Previous Office versions - Keeping and not installing over - Custom Installation Wizard issue If you are using the Custom Installation Wizard to install Office 2000 on a computer hosting earlier versions of Office, you must not install to the same directory where a previous version of Office exists. The Custom Installation Wizard does not warn you about installing Office 2000 into the same directory as a previous version. If you choose to keep previous versions of Office, do not install into the same directory. If you do install over a previous version, you will have a mixed version situation with possibly corrupt registry settings and files. Save As/File Open dialog - Places Bar customization If you want to add user-defined entries to the Places Bar in the Office 2000 Save As/File Open dialog, modify or add the registry keys and entries described below. Office 2000 applications can display up to 10 user-defined items (Place1 through Place10). You can display only 5 user-defined items if you also show all the default-predefined items. If you disable the predefined items, you can display up to 10 user-defined items. Add the “ItemSize” entry to the [HKEY_CURRENT_USER\9.0 Find] and set it to 0 (zero). For example: [HKEY_CURRENT_USER\9.0 Find] “ItemSize” 0 - dword ItemSize sets the use of large or small icons in the Places Bar. You can only display 5 large icons if you set ItemSize to 1 (large icons). The Places Bar section of the Save As/File Open dialog does not scroll and limits you to a maximum of 10 items in small icon format. Then add or modify the following key and associated entries: [HKEY_CURRENT_USER\9.0 Find] (where X is 1 - 10) “Name” “Shortcut Folder Text” “Path” “C:&quot;”SortAscending&quot; 1 - dword “Index” 0 - dword The values for the keys are as follows: - Name is the text displayed in the Places Bar for the shortcut you are adding. - Path contains the entry to any drive or UNC path combination. - If SortAscending is set to 1 and Index is set to 0, it places the user defined item in ascending order within the list of user defined items. - If Index is set to 1 through 10, the PlaceX Name entry appears in that position in the user defined list and ignores the sort order. Do not change entries in the registry while a Save As/File Open dialog is currently open. When the dialog closes, it automatically overwrites the registry settings with the settings the dialog was opened with. To remove each default icon (Favorites, Web Folders, etc) add or modify the following registry key entries: [HKEY_CURRENT_USER\9.0 Find] “Show” 0 - dword “Show” 0 - dword “Show” 0 - dword “Show” 0 - dword “Show” 0 - dword “Show” set to 1 displays the icon. “Show” set to 0 hides the icon. Setup.exe - Destination Path - Character limitation If you attempt to install Office 2000 with the /a setup option and a path string longer than 260 characters (including filename, drive, UNC, etc) the setup will fail. You must consider the maximum number of characters in a path string before submitting it as a portion of a setup string. Setup.exe - Recommended upgrade version available with Office Resource Kit The Office Resource Kit has an upgraded version of the Setup.exe for Office 2000. It is recommended you use it for all your deployment needs. This version has increased string space for complex or long [Options] lines (such as ADDLOCAL, ADVERTISE, and ADDSOURCE found in the setup.ini). This is important if you are creating staged deployment scenarios where the ADVERTISE line can become very lengthy due to long PropName=PropValue associations (feature names, see filelist.xls in the Office Resource Kit tools section). Currently, the shipped version of Setup.exe can only pass a PropName=PropValue pairing of no more than 1024 characters. With the upgraded version available within the Office Resource Kit, it is possible to pass a pairing of 32,768 characters, however Windows Installer can only accept a 1024 character pairing. The upgraded version of Setup.exe is nearly identical to the Setup.exe shipped with Office 2000 except for the following: - Larger string variable handling for the [Options] section. - An SMS correction for Rollback failures. - An increased security buffer for really long security group strings. If the administrator is a member of a large number of global groups, Setup.exe may not recognize the admin state, preventing Setup from launching on Windows NT. - An increased stack area to reduce possible corruption of variable space. - A new command line option /chained that allows for chaining several installs together into one process. See the topic “MultiLanguage Pack installation - US and MultiLanguage packs single install example” for information on how to use this new feature. You can find the upgraded Setup.exe on the Office Resource Kit CD at: <CD Root>:.EXE or search the http://www.microsoft.com/office/ork/ web site. Setup.exe - UNC versus Drive letter startup issue An administrator may want to control the form of the path (UNC vs. mapped drive) used by Office 2000 to access the source location after an install. Unlike previous versions of Office, this is not determined at the time the Administrative installation is performed. The only control of the path

form for Windows Installer packages is the path used to reference the .msi file. For example, if a user has a drive mapped to the Setup.exe location and the .msi Windows installer package, but launches setup from a UNC path (i.e. using the Run option and entering a fully qualified UNC path to the Setup.exe), the controlling element is the UNC path. The Setup.ini, by default, contains only a filename reference to the .msi file. If an administrator wants to explicitly control the path used by the Setup.exe, but does not care how a user starts Setup.exe, they can modify the Setup.ini file in the source location. To do so, add a fully qualified UNC or drive letter path to the .msi file entry in the Setup.ini. When setup is complete, all references to the source location in the System Registry are then of the path form used to reference the .msi file. Setup.exe and batch files - using the “start /wait” prefix If you use batch files as part of your setup process for Windows 95 or Windows 98 clients, use the “start /wait” prefix. This is not required for Windows NT 4.0 or Windows 2000. If you need to have one batch file for all versions of Windows, use the following example of batch file code as a means of detecting the version of Windows currently in use. rem Detect the Operating System if “%OS%”==“Windows_NT” set start= if “%OS%”==&quot;&quot; set start=start /wait rem Call Office Setup %start% setup.exe /wait /qb Note: In the second line of the example batch file code (if “%OS%”==“Windows_NT” set start= ) there must be a space after the “start=”. Setup.exe and Msiexec.exe - “/t” command line option syntax usage difference If you use Setup.exe with either /jm or /ju (advertise) with the /t command line option, the /t requires a space between the option switch and the input parameter. Unlike Msiexec.exe, which requires no space, Setup.exe requires the space to properly locate and identify the name of the appropriate transform you want to use. For example: msiexec /ju .msi /tYourTransform.mst setup /ju .msi /t YourTransform.mst Shared components/files - Making sure local applications do not fail when other Run From Network applications are installed and the network share is unavailable If you want shared components to be installed locally, set the top branch (in the Custom Installation Wizard) to “local,” then change the sub features to RNS. It is not possible to segregate and have some components local and have others present on the network, they must either all be local or all on the network. SMS Installations - Additional information on deploying Office 2000 with SMS The topics in the Office Resource Kit chapter entitled “Deploying Office with Systems Management Server,” present a high-level overview of using Systems Management Server to deploy Office 2000. For important information on installing SMS and detailed procedures on using it to deploy Office 2000 with the supplied PDF files, see the SMS documentation available on the Office Resource Kit Web site at: http://www.microsoft.com/Office/ORK. This information will be available after the release of Office 2000. Staged Deployment and existing earlier versions of Office If you plan a staged deployment of Office 2000 applications to systems with existing installs of earlier versions of Office, and you have changed the default removal properties of setup, you should use the Office Removal Wizard prior to running setup for any subsequent staged deployments. If you use Office Setup (OPC) with the default settings, it removes all prior Office applications. The first time an Office 2000 application is installed with a modified transform, it will remove the prior Office version applications per the settings in your transform. However, the next time you attempt to install an Office 2000 application to the same system, it will not remove any previous instances of Office applications. Setup will continue though, and you will end up with both versions of the selected Office applications on your system. Using the Office Removal Wizard ensures you will not have a mixed registry and directory configuration. Make sure you run the Office Removal Wizard before you run setup. Terminal Server - Motionless Office Assistant - Install considerations If you intend to configure an Office 2000 installation to use Terminal Server and the Motionless Office Assistant, you should make sure you do not install any of the other Office Assistants. When you install Office, set all the Office Assistants to “Not Available” (in the Windows Installer). You can either install the Office Resource Kit before or after the installation of Office 2000. If you install the Office Resource Kit prior to installing Office 2000, Office 2000 automatically takes advantage of the motionless Office Assistant without having to configure Office to use it. Currently, the Office Logo is the only assistant available without animation. The Motionless Office Assistant optimizes your communication link with the Terminal Server from the client computer and provides for faster interaction with the system. Terminal Server - Recommendation for Windows NT 4.0 If you are using Windows NT 4.0 with Service Pack 3 installed, and have users taking advantage of Terminal Server, it is highly recommended that you install the Windows NT 4 Service Pack 4 update. Service Pack 4 includes updates to Terminal Server. Installing the Service Pack 4 update prior to installing Office 2000 installs the latest updates for Terminal Server and allows Office 2000 to properly take advantage of all the advanced features of the latest release of Terminal Server. Tools or Information - Most recent or up-to-date Check the http://www.microsoft.com/office/ork Web site for new or updated tools. Also, check this site on a regular basis for new information or articles about issues you may encounter where help or other sources do not provide the information you need. Errata Glossary Add the following item to the Glossary: NEWPROF.exe - Reads the contents of a .prf file to create an Outlook profile. Outlook uses profiles to store information about a user’s e-mail servers, where Outlook information is stored (on the server or in a local file), and other options. The Office Resource Kit contains a sample .prf file (outlook.prf) for use in creating an Outlook profile with the Exchange Server service and an Internet E-Mail service. Installing Office 2000 in Your Organization - Deploying Office 2000 - Installing Office in a Windows Terminal Server Environment - How to Install Office Disc 1 on a Windows Terminal Server - Set default Office application settings The paragraph: On the Tools menu, click Options, and then click the Preferences tab. Click Calendar Options and clear the Use Microsoft Schedule+ as my primary calendar check box. Should read: On the Tools menu, click Options, and then click the Preferences tab. Click Calendar Options and clear the Use Microsoft Schedule+ as my primary calendar check box. Schedule+ does not run with Terminal Server and must be disabled. It is advised to uninstall Schedule+ or change the related policy under the “Microsoft Outlook 2000 - Prevent users from changing primary calendar application.” Set the “User cannot change primary calendar app” check box to checked. Installing Outlook after Office 2000 Step 6 should be removed from the procedure. Instead, the following action should be carried out prior to the procedure: Before performing the following steps, if there is an existing installation of the current Office 2000 application already on the target system, it should be uninstalled just prior to the installation of Outlook 2000 and should have no user prompts or User Interface dialog displayed to the user.

Office 2000 System Policy Reference - System Policies in the Windows Installer Policy Template Below the “USER SETTINGS” heading, cross out the following policy: “Pin transform at Transform source” Office 2000 System Policy Reference - System Policies in the Windows Installer Policy Template Add the following policies under the “MACHINE SETTINGS” heading and below the “Disable Patching” policy. Allow user control over installs Disable IE security prompt for Windows Install scripts. Tools Information - Terminal Server Tools - Other support information for Windows Terminal Server The table entry: Termsrvr.mst Provides the transform (.mst file) used to install Office on a Terminal Server computer Should read: Termsrvr.mst Provides the transform (.mst file) used to install Office on a Terminal Server computer. This transform installs all components and sets Outlook to Corp mode by default. Upgrading to Microsoft Office 2000 - Upgrading to Outlook 2000 - Upgrading fromMicrosoft Schedule+ 7.x All references to Schedule+ 95 should be changed to read Schedule+ 7.x. Schedule+ 95 is Schedule+ 7.0. Upgrading to Microsoft Office 2000 - Upgrading to Outlook 2000 - Sharing Information with Microsoft Schedule+ The paragraph: Note: Outlook 2000 users with Corporate/Workgroup e-mail support have the option to substitute Microsoft Schedule+ 7.x for the Outlook Calendar. Should read: Note: Outlook 2000 users with Corporate/Workgroup e-mail support have the option to substitute the Outlook 2000 Calendar with the Microsoft Schedule+ 7.x calendar. However, a user must have Schedule+ 7.x installed if they intend to use it as their primary calendar. Schedule+ 7.x is not installed as part of Outlook 2000. Upgrading to Microsoft Office 2000 - Upgrading to Outlook 2000 - Upgrading from Microsoft Schedule+ 1.0 The sentence: You have the option to use either Microsoft Schedule+ or the Microsoft Outlook 2000 native Calendar as your calendar client. Should read: You have the option to use either the Microsoft Schedule+ 7.x or Microsoft Outlook 2000 native Calendar. Releases of Microsoft Schedule+ prior to 7.x are not supported for use as the primary calendar within Outlook 2000.

Additional query words: OFF2000

=
========================================================= Keywords :

Version : WINDOWS:2000 Platform : WINDOWS Issue type : kbinfo ============================================================================= Copyright Microsoft Corporation 1999.