microsoft.com Home | |||
http://www.microsoft.com/office/ork |
Installing Office in a Windows Terminal Server EnvironmentHow to Install Office Disc 1 on a Windows Terminal ServerYou install Microsoft Office 2000 from Microsoft Office 2000 Disc 1 on a Microsoft Windows Terminal Server computer in much the same way you install Office on a client computer. With some careful planning and a few modifications, Office performs well in the Windows Terminal Server environment. To run Office 2000 in this environment, follow these steps:
Running Office on individual users’ computers is different from running it in a Terminal Server environment. When you install Office on a Terminal Server computer, the users who connect to the server are limited to your Office configuration and cannot install or remove features. In other words, all users running Office from the Terminal Server computer inherit the features you select during installation. If your users need different sets of Office functionality, you might need several Terminal Server computers — one for each unique Office configuration. Because of the multiuser nature of the Terminal Server computer, and users’ restricted access to the server, you cannot select the following installation options for any Office features: Instead, you must predetermine which Office features your users need and select one of the following installation options for each feature: Customize the Terminal Server transformThe Microsoft Office 2000 Resource Kit includes a Windows installer transform that you must use when installing Office on the Terminal Server computer – Setup does not install Office on the Terminal Server computer without the transform. This transform, named TermSrvr.mst, is configured to install all Office features to run from the local computer or not be installed at all. Toolbox Because of the special requirements for running Office in a Windows Terminal Server environment, you must use the transform provided in the Office Resource Kit to install Office on the Terminal Server computer. Office Setup does not install Office on the Terminal Server computer without this transform. For information about installing TermSrvr.mst, see Terminal Server Tools. What the TermSrvr.mst file does The Windows installer transform included in the Office Resource Kit, TermSrvr.mst, is configured to install Office correctly on the Terminal Server computer. Office Setup does not install Office on the Terminal Server computer without this transform. The primary function of the TermSrvr.mst file is to modify the feature tree so that all Office features are installed to run from the local computer. There are a few exceptions – those features that are not recommended or that do not perform well in the Terminal Server environment are set to not be installed at all. In addition, the NOUSERNAME property is set so that Setup does not supply a default user name when you install Office on the Terminal Server computer. This setting ensures that users who log on to the Terminal Server computer are asked to provide a user name when they run an Office application for the first time. This property is set internally in the transform – if you examine the transform with the Custom Installation Wizard, you do not see the NOUSERNAME property listed on the Modify Setup Properties panel. The TermSrvr.mst file also sets a property to increase the amount of registry space allocated for Office on the Terminal Server computer. This setting allows Office to store necessary information in the registry for each Office user. Again, this property is not listed on the Modify Setup Properties panel. In the TermSrvr.mst file, all Office features are set to one of the following installation states:
Toolbox A number of Outlook features, normally hidden in the Office Setup feature tree, are exposed in the Terminal Server transform. This arrangement allows you to choose whether to install these features. The Office Resource Kit includes an Excel worksheet named OutlFeat.xls that describes these Outlook features. For information about installing OutlFeat.xls, see Terminal Server Tools. If you want to accept the default Office configuration, you do not need to modify TermSrvr.mst. However, if there are Office features that are not needed by your users, you can improve overall performance and conserve disk space by customizing TermSrvr.mst so that Office Setup does not install these features on the Terminal Server computer. Installing nonEnglish versions of Office The TermSrvr.mst file was created using the Windows installer package (Data1.msi) for the US English version of Office 2000. Some other language versions of Office have additional features that are not present in the US English version, and the TermSrvr.mst file does not change the installation states of those features. If any of these additional features are set to Run from Network or Installed on First Use, then they do not function correctly on the Terminal Server computer. To install a nonEnglish version of Office on a Terminal Server computer, use the Office Custom Installation Wizard to make sure that all features in the transform are set to either Run from My Computer or Not Available. To customize the Terminal Server transform
Toolbox By default, the Terminal Server transform (TermSrvr.mst) does not install any Office Assistants. However, after running Office Setup you can install the Motionless Office Assistant (Stillogo.acs) included in the Office Resource Kit. This Office Assistant uses no animation, so there is minimal network traffic between the Terminal Server computer and the Terminal Client computer. For information about installing the Motionless Office Assistant, see Terminal Server Tools. Install Office on the Terminal Server computerTo install Office, run Office Setup on the Terminal Server computer. You can run Setup from a network administrative installation point or from the Office Disc 1. You must specify the Terminal Server transform (TermSrvr.mst) and additional command-line options. Note Before you install Office on a Terminal Server computer, log on to the server with administrator privileges. To install Office Disc 1 on the Terminal Server computer
Important You must use Add/Remove Programs in Control Panel with the All users begin with common application settings option selected. This setting runs Setup in Install mode, which installs Office for all Terminal Client users who connect to the Terminal Server computer. If you run Setup directly from Office Disc 1, then Setup runs in Execute mode, which installs Office only for the user running Setup. Set default Office application settingsYou can use the Profile Wizard to customize the default Office user settings for all users logging on to the Terminal Server computer. For best performance in this environment, consider setting the following options in Office applications. Microsoft Access 2000
Microsoft Excel 2000
Microsoft FrontPage 2000
Microsoft Outlook 2000
Microsoft PowerPoint 2000
Microsoft Word 2000
After you customize all the application settings you want, run the Profile Wizard and save your settings in an OPS file. Store the OPS file in a folder that is accessible to users running Office from the Terminal Server computer. To point users to your customized settings
When users log on to the Terminal Server computer, Windows runs the Profile Wizard using the command line in the RunOnce subkey and restores the settings you saved in the OPS file. This command runs one time for each user the first time the user logs on to the Terminal Server computer. Configure Microsoft Outlook 2000To complete the installation of Outlook 2000, you need to perform two additional steps after running Office Setup. First: run Outlook 2000 once; and second, optionally provide write access to a portion of the Windows registry. Outlook 2000 performs a number of initialization tasks when it runs for the first time on the Terminal Server computer. These tasks complete the Outlook installation and require write access to system areas on the Terminal Server computer. To allow Outlook to finish installing
By default, users have write access to all portions of the Windows registry on the Terminal Server computer. However, if you have any custom Outlook forms installed on the computer, and you have configured the Windows registry on the Terminal Server computer to restrict user access, then you need to make sure that users have write access to the HKEY_CLASSES_ROOT\CLSID key in the Windows registry. Outlook registers custom forms the first time that they are opened, and this requires that the user have write access to this portion of the registry. To give users write access to the CLSID key
See alsoOffice 2000 Setup contains other options that you may want to take advantage of, such as installing Microsoft Internet Explorer 5 and removing previous versions of Office. For more information about Office 2000 Setup, see Office Setup Program. By using the Office 2000 Custom Installation Wizard, you can modify TermSrvr.mst to further customize your Terminal Server installation. For more information about the Custom Installation Wizard, see Office Custom Installation Wizard. For more information about the user settings that the Profile Wizard saves and restores, see Profile Wizard. |
|
Topic Contents | Previous | Next | Top Friday, March 5, 1999 © 1999 Microsoft Corporation. All rights reserved. Terms of use. | ||
License
|