WordType Designs™
Driven To Distractions©
The Sound of One Hand Clapping©

A rchive Date
[ 13-06-2000 ]
Category
[ Information Technologies ]
sub-Categoy
[ Microsoft ]
      [http://www.microsoft.com/office/enterprise/deployment/termserv.htm
      Office 2000 with Windows® Terminal Server
      Fast Facts
      Published: October 1998
      For the latest information, please see http://www.microsoft.com/office/

      Introduction
      Organizations that need to enable the use of Microsoft Office 2000 in cross-platform, legacy hardware, or terminal-based environments should consider using Microsoft Windows NT Server Terminal Server Edition (Terminal Server). The Windows Terminal Server platform allows different types of hardware platforms to act as Windows-based Terminals running Windows-based 32-bit applications off a back-end Windows NT-based server. This is a particularly compelling solution in maintaining a corporate standard during the co-existence or migration period of the enterprise upgrade to Office 2000. This strategy can also help reduce desktop management costs by shifting hardware requirements from the desktop to the server, since control is now maintained centrally. Office 2000 is designed as the model Windows Terminal Server application, but more importantly, it exceeds those requirements with additional intelligence and a greater level of central control. The result is a scalable solution that helps reduce cost of ownership without compromising productivity.

      This document provides an overview of the Windows Terminal Server platform and explains how the next version of Office runs in this environment.

      How the Windows Terminal Server Platform Works
      Windows Terminal Server contains a server and client piece. The multi-user server core provides the ability to host multiple, simultaneous client sessions on Windows NT Server. The client contains only the minimum amount of software necessary to boot the device, establish a connection to the server, and present the user interface. All other operating system functions run completely on the server, including running an application. The server provides the host-computing environment, including management of all computing resources on a per-user basis (for example, memory, CPU, and other resources). Thus in the Windows Terminal Server environment, all applications including Office will be run completely from the server. All users who run Office on Windows Terminal Server will open up a new instance of the application on the server and all their customizations will be stored in a per-user storage area.

      Office 2000 as a Model Windows Terminal Server Application
      By definition, an application that behaves well on the Windows Terminal Server platform should:

      Be architected to separate application bits and user data. There are two components to an application profile: the actual bits that run the application and the settings that customize the interface for the user. A good application for Windows Terminal Server must be able to separate the two. Thus, users running applications off the server should be able to customize their applications and have them persist between sessions and without interference from other user settings.

      With Office 2000, application bits go in the installed location and per-machine registry settings go in the HkeyLocalMachine (HKLM) hive in the registry. User settings can be stored as files or as registry settings. Depending on the format in which they are stored, they will reside in different locations. Files will go in the user's profile specifically under the \Profiles\<username>\Application Data folder and user-specific registry settings will go in the HkeyCurrentUser (HKCU) hive in the registry. By separating the installation of application bits from the user data, the Terminal Server will retain application access for all users while protecting the user customizations from session to session.

      Be configured so that there are no hard-coded path names in the registry. There are several keys in HkeyLocalMachine (HKLM) that are paths to file locations. Several applications, including some pre-Windows Terminal Server Office versions, used these hard-coded paths to locate installed files. Because install locations may change and coded path names may point to an invalid source, a good Windows Terminal Server application must have the flexibility to redirect the path as necessary. The Microsoft Installer, included with Office 2000, is aware of these locations and keeps track of installed files instead of requiring the administrator to hard-code them into the registry. Thus, if the default server is unavailable, the system is intelligent enough to redirect the connection to the next appropriate, available source.

      Use environment variables wherever possible. Environment variables are useful for administrators who want to point a path to different storage locations. For example, an administrator may want to store all users' Microsoft Excel files on one server and sets the path to x:\userdata\xl\%Username%. %Username% is an environment variable and needs to be expanded for each individual user. However, because the Windows Terminal Server platform behaves in the same way as a hard-coded path when saving files, it cannot expand to recognize an environment variable. Thus, a user will not be able to save to a server if it has been taken offline. Because Office 2000 fully exploits the detection capabilities of the Microsoft Installer, this problem is avoided because it enables the administrator to set the environment variables to automatically detect the next recognized storage location.

      Use the "Temp" directory to store non-persistent data. Past versions of Microsoft Office would store user data files in the "Temp" directory that was created at run-time, due to a limitation in system lockdown scenarios. Because the Temp directory has no security and the data is stored centrally in the Windows Terminal Server environment, user files are unsecured if stored in a server based "Temp" directory. Office 2000 was redesigned to use the application data folder and the "My Documents" folder as the default for user data storage. Because data is stored centrally in the Windows Terminal Server environments, the administrator will now be able to redirect the "Temp" folder itself or delete the data after every session to provide higher security for user data files.

      Office as an Intelligent Windows Terminal Server Application
      Microsoft has focused on designing Office 2000 to exceed performance and behavioral expectations for this platform. Specifically, Office 2000 automatically detects the Windows Terminal Server platform and will optimize its behavior automatically. Because Windows Terminal requires a persistent connection to a server, the application must be aware of network connection considerations. For example, Office 2000 addresses this by automatically optimizing to run in a connected state if it recognizes that it is running on a thin client. In response it will display an application splash screen that is less pixel heavy.

      Greater Level of Central Control
      The Windows Terminal Server environment is a highly desirable option for corporations that want or require complete central control over the desktop environment, even to the level of total system lockdown. This is accomplished by applying a system policy on some or all of these user settings. For example, if all users in the finance department require password access to edit spreadsheets, the administrator may enable read-only access for those profiles. As a policy, the user cannot change this setting. Because of the greater level of flexibility in configuring the Office 2000 setup, administrators will have full control of the profile settings for Office 2000 users.

      Conclusion
      A key objective in reducing the cost of ownership for Office 2000 was to decrease administration costs through greater IT administrator control. With IT administrators responsible for thousands of PCs and supporting users of all levels, maintaining standards and centralized control is critical. Office 2000 takes advantage of functionality available with the Windows Terminal Server platform to make it easier to centrally administer and control the end-user desktop, while providing a scalable solution for the enterprise and enabling users to take full advantage of the productivity applications.

      For more information: http://www.microsoft.com/office/
      This is a preliminary document and may be changed substantially prior to final commercial release. This document is provided for informational purposes only and Microsoft makes no warranties, either express or implied, in this document. Information in this document is subject to change without notice. The entire risk of the use or the results of the use of this document remains with the user. The example companies, organizations, products, people and events depicted herein are fictitious. No association with any real company, organization, product, person or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

      Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

      Unpublished work. Ó 1998 Microsoft Corporation. All rights reserved.
      Microsoft, the Office logo, Windows and Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the U.S.A. and/or other countries.
      The names of actual companies and products mentioned herein may be the trademarks of their respective owners.]


Some pages may require Adobe Acrobat Reader™


Copyright and Fair Use Information: The contents of this web site is protected by international copyright laws and may not be reproduced in any form or manner whatsoever, if for the purpose of resale or solicitation of a donation. The essays included here, may be reproduced only if: 1)They are not altered in any way; 2) reproductions must be accompanied by this copyright page ; and 3) it is given freely and without charge.
Fair use: The fair use of copyrighted work, including such use by reproduction in copies or phonorecords or by any other means specified in above sections, for purposes such as criticism, comment, news reporting, teaching (including multiple copies for classroom use), scholarship, or research, is not an infringement of copyright. In determining whether the use made of a work in any particular case is fair use the factors to be considered include : (1) the purpose and character of the use, including whether the use is of a commercial nature or is for nonprofit educational purposes; (2) the nature of the copyrighted work; (3) the amount and substantiality of the portion used in relation to the copyrighted work as a whole, and; (4) the effect of the use upon the potential market value of the copyrighted work.
Home | About Narrative? |Contact
Copyright © 2025. All Rights Reserved
HAG122125 (1998 -2026)