Deploying Microsoft Windows NT Server 4.0, Terminal Server Edition

DeployingMicrosoft®WindowsNT®Server4.0,TerminalServerEdition

A Service Development andPlanningGuide

INFORMATION PROVIDED IN THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND FREEDOM FROM INFRINGEMENT. The user assumes the entire risk as to the accuracy and the use of this document.

The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.

Information in this document is subject to change without notice. The names of companies, products, people, characters, and/or data mentioned herein are fictitious and are in no way intended to represent any real individual, company, product, or event, unless otherwise noted. The documents within the portion of the Service Guide Documentation denoted as “Resource Materials section” may be reproduced, modified, and distributed to third parties in an unlimited number. You may make copies of the remaining parts of this document only for internal distribution within your organization, but you may not modify or distribute these other parts to anyone outside of your internal organization.

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

This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT.

Printed in the United States of America.

Microsoft, MS, ActiveX, BackOffice, FoxPro, FrontPage, Microsoft Press, MS-DOS, NetMeeting, Outlook, PowerPoint, Visual Basic, Win32, Windows, and WindowsNT are either registered trademarks or trademarks of Microsoft Corporation in the U.S. and/or other countries.

Macintosh is a registered trademark of Apple Computer, Inc.

Release Date: December 1998

Document Name: Deploying Microsoft® Windows NT® Server 4.0, Terminal Server Edition

Revision C

Internal Part Number: 098-xxxxx

External Part Number: xxxxxx

White text required for PostScript printing of a blank page.

END-USER LICENSE AGREEMENT

Microsoft Service Guide

IMPORTANT—READ CAREFULLY: This Microsoft End-User License Agreement (“EULA”) is a legal agreement between you (either an individual or a single entity) and Microsoft Corporation for theMicrosoft product(s) identified above, which includes computer software and associated media, and may include “online” or electronic documentation (“SOFTWARE PRODUCT” or “SOFTWARE”) together with associated printed materials (“DOCUMENTATION”). By installing, copying or otherwise using the SOFTWARE PRODUCT and the DOCUMENTATION, you agree to be bound by the terms of this EULA. If you do not agree to the terms of this EULA, you may not copy or use the SOFTWARE PRODUCT and the DOCUMENTATION.

LICENSE

The SOFTWARE PRODUCT and the DOCUMENTATION are protected by United States copyright laws and international copyright treaties, as well as other intellectual property laws and treaties. The SOFTWARE PRODUCT and the DOCUMENTATION are licensed, not sold.

GRANT OF LICENSE. This EULA grants you the following rights:

SOFTWARE PRODUCT. You may use and reproduce copies of the enclosed Microsoft SOFTWARE PRODUCT for your internal use provided that you maintain the copyright notice on all copies of the SOFTWARE PRODUCT.

DOCUMENTATION. You may modify the DOCUMENTATION in order to customize it for your customer companies for use in conjunction with your Service Guide and reproduce and distribute such modifications to your customer companies for their internal use only. You may not distribute the DOCUMENTATION as provided with the SOFTWARE PRODUCT.

If you modify the DOCUMENTATION for distribution, you must do all of the following:

remove the Microsoft copyright notice;
include a license grant consistent with the terms of this EULA;
include a provision against reverse engineering, decompiling and disassembly of code for the SOFTWARE PRODUCT;
include a disclaimer of warranties and consequential damages on behalf of your suppliers; and
include the U.S. Government restricted rights clause as provided in Section 4 below.

DESCRIPTION OF OTHER RIGHTS AND LIMITATIONS.

Limitations on Reverse Engineering, Decompilation, and Disassembly. You may not reverse engineer, decompile, or disassemble the SOFTWARE PRODUCT, except and only to the extent that such activity is expressly permitted by applicable law notwithstanding this limitation.
Termination. Without prejudice to any other rights, Microsoft may terminate this EULA if you fail to comply with the terms and conditions of this EULA. In such event, you must destroy all copies of the SOFTWARE PRODUCT and all of its component parts.

SAMPLE CODE. If the SOFTWARE PRODUCT includes Sample Code, then Microsoft grants you a royalty-free right to reproduce and distribute the sample code of the SOFTWARE PRODUCT provided that you: (a) distribute the sample code only in conjunction with and as a part of your software product distributed with your service offering, (b) do not use Microsoft’s or its authors’ names, logos, or trademarks to market your software product, (c) include the copyright notice that appears on the SOFTWARE PRODUCT on your product label and as a part of the sign-on message for your software product, and (d) agree to indemnify, hold harmless, and defend Microsoft and its authors from and against any claims or lawsuits, including attorneys’ fees, that arise or result from the use or distribution of your software product. Microsoft provides no support services related to the SOFTWARE PRODUCT.
U.S. GOVERNMENT RESTRICTED RIGHTS. The SOFTWARE PRODUCT and DOCUMENTATION are provided with RESTRICTED RIGHTS. Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 or subparagraphs (c)(1) and (2) of the Commercial Computer Software—Restricted Rights at 48 CFR 52.227-19, as applicable. Manufacturer is Microsoft Corporation, One Microsoft Way, Redmond, WA 980526399.

MISCELLANEOUS

If you acquired this product in the United States, this EULA is governed by the laws of the State of Washington.

If you acquired this product in Canada, this EULA is governed by the laws of the Province of Ontario, Canada. Each of the parties hereto irrevocably attorns to the jurisdiction of the courts of the Province of Ontario and further agrees to commence any litigation which may arise hereunder in the courts located in the Judicial District of York, Province of Ontario.

If this product was acquired outside the United States, then local law may apply.

Should you have any questions concerning this EULA, or if you desire to contact Microsoft for any reason, please contact the Microsoft subsidiary serving your country, or write: Microsoft Sales Information Center/One Microsoft Way/Redmond, WA 980526399.

LIMITED WARRANTY

NO WARRANTIES. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT EXPRESSLY DISCLAIMS ANY WARRANTY FOR THE SOFTWARE AND DOCUMENTATION. THE SOFTWARE AND DOCUMENTATION IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OR MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK ARISING OUT OF USE OR PERFORMANCE OF THE SOFTWARE AND DOCUMENTATION REMAINS WITH YOU.

LIMITATION OF LIABILITY. MICROSOFT’S ENTIRE LIABILITY AND YOUR EXCLUSIVE REMEDY UNDER THIS EULA SHALL NOT EXCEED FIVE DOLLARS (US$5.00).

NO LIABILITY FOR CONSEQUENTIAL DAMAGES. To the maximum extent permitted by applicable law, in no event shall Microsoft or its suppliers be liable for any special, incidental, indirect, or consequential damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or any other pecuniary loss) arising out of the use of or inability to use the software product, even if Microsoft has been advised of the possibility of such damages. Because some states and jurisdictions do not allow the exclusion or limitation of liability for consequential or incidental damages, the above limitation may not apply to you.

This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT.

White text required for PostScript printing of a blank page.

End-User Software License Agreement

The End-User License Agreement (EULA) for this guide—Deploying Microsoft® Windows NT® Server 4.0, Terminal Server Edition—is on the preceding pages. Read it carefully before you install any software or use the CDROM.

Your feedback is crucial for each new version of this guide

Please send your suggestions and comments to .

White text required for PostScript printing of a blank page.

Contents

Project Overview......

Overview......

Getting To Know Terminal Server......

Preparing To Use This Guide......

Using This Guide......

Service Guide Conventions......

Vision/Scope Approved Milestone......

Overview......

Understanding the Team Model......

Defining Vision and Scope......

Assessing Risk......

Defining Project Structure......

Approving the Vision/Scope......

Project Plan Approved Milestone......

Overview......

Documenting the Environment......

Creating a Functional Specification......

Creating and Approving the Logical Design......

Creating and Approving the Physical Design......

Reviewing the Risk Assessment......

Building and Approving the Master Project Plan......

Scope Complete/First Use Milestone......

Overview......

Validating the Plan......

Developing a Pilot Implementation Plan......

Deploying the Pilot Server......

Deploying Applications on the Pilot Server......

Piloting Terminal Server......

Assessing the Pilot Deployment......

Release Milestone......

Overview......

Deploying Terminal Server Throughout the Environment......

Assessing the Complete Deployment......

Planning Ongoing Maintenance, Support, and Scalability......

Resources......

Master List of Resources and Online Pointers......

White text required for PostScript printing of a blank page.

Project Plan Approved Milestone1

Project Overview

Project Plan Approved Milestone1

This page must be blank. Do not remove or hide this page.
White text required for PostScript printing of a blank page.

Overview

Deploying Microsoft WindowsNT Server version 4.0, Terminal Server Edition

This service guide provides a process for designing an implementation and deployment of Microsoft® WindowsNT® Server version4.0, Terminal Server Edition (referred to as Terminal Server in this guide).

This guide illustrates steps for deploying Terminal Server in an enterprise environment. It contains information on assembling a project team, assessing the current environment, designing a solution based on need, testing, piloting, and implementing a full deployment. By following the recommendations set forth in this guide, you can provide users with the functionality of WindowsNT and access to applications based on Microsoft® Windows® in a mixed-client environment, including Windows-based terminals, legacy desktops (Windows- and non-Windows-based), and 32-bit Windows-based desktops.

Applying Core MSF Principles

Structurally, the guide offers project plan guidance based on the core principles of Microsoft Solutions Framework (MSF) and built around the four MSF milestones—Vision/Scope Approved, Project Plan Approved, Scope Complete/First Use, and Release.

Getting To Know Terminal Server

Introducing Microsoft WindowsNT Server 4.0, Terminal Server Edition

Microsoft WindowsNT Server 4.0, Terminal Server Edition is an extension of the WindowsNT product line that provides support for remote access by using thin client software that runs on a new class of Windows-based terminals and on desktop systems running under 16-bit and 32-bit Windows. Terminal Server allows users to run both the Windows desktop operating system and Windows-based applications directly off the server, extending the scalable Windows family and providing users of low-cost terminal devices and legacy hardware with access to the latest WindowsNT–based technology and the latest Windows-based applications.

Terminal Server has three parts. The server itself is a new edition of Microsoft WindowsNT Server 4.0 with the ability to host multiple, simultaneous client sessions. Remote Desktop Protocol (RDP) is the protocol that allows a super-thin client to communicate with Terminal Server over a network. Terminal Server Client is a super-thin client application that connects to Terminal Server from a Windows-based terminal, Microsoft Windows for Workgroups 3.11, Microsoft Windows95 or Windows98, or WindowsNT.

Terminal Server includes Microsoft® Internet Explorer version 4.01 for Web and file system browsing. Active Desktop is not supported in the current release of Terminal Server.

Consult the Start Here and Administration Guide documentation that comes with the Terminal Server software for complete instructions on installing and administering Terminal Server. You can find electronic copies of these documents on the Terminal Server installation CDROM at \support\books.

For the latest Terminal Server product information, tours, and file downloads, visit the Terminal Server home page at

Determining Business Drivers

Customers who have made the decision to implement Terminal Server typically explain their decision in terms of business drivers. Although not all customers focus on the same set of drivers or give them all the same degree of consideration, a well-implemented Terminal Server deployment will often confer benefits upon the user that exceed those planned for during the initial decision-making process.

Typical business drivers for Terminal Server include administration and network usage, legacy client device replacement, cross-platform compatibility, and Year2000 issues.

Administration and Network Usage

Terminal Server can improve and simplify administration while also optimizing performance over the network.

Terminal Server centralizes administration of network resources by putting all applications on servers rather than distributing them to individual desktop computers. This is particularly useful with bandwidth-intensive applications like flat-file systems (for example, Microsoft® FoxPro®). Terminal Server clients can efficiently gain access to an application running on Terminal Server and a fast network segment because of the architecture’s efficient use of bandwidth. All application processing takes place on the server, with only video, mouse, and keyboard traffic passing between the client and Terminal Server.
Deploying applications centrally on Terminal Server allows users simultaneous access to upgraded applications. Administrators can deploy custom applications that require frequent incremental upgrades on servers running Terminal Server, significantly reducing time and labor to update the applications for all users.
Users can store sensitive data in a central data facility (glass house) rather than on their individual personal computers, substantially decreasing the risk of data loss from theft, natural disasters, and other causes.
Remote users can gain access to the same data and applications as local users over dialup or permanent Internet connections and benefit from how Terminal Server efficiently uses bandwidth.

Terminal Server system diagram

Legacy Client Device Replacement

Terminal Server simplifies the process of replacing legacy hardware and software. If the organization currently uses text-based terminals, it can deploy Terminal Server with a new low-cost, thin client device known as a Windows-based terminal to provide an upgrade path to Windows-based applications.

An organization can also easily install Terminal Server client software on older personal computers used for task-based applications such as terminal emulation or fixed function applications. In this way, end users can obtain access to the 32-bit Windows-based user interface found on Windows95 and98 or WindowsNT 4.0 and to the latest Windows-based applications before they receive new computers.

Companies with high employee turnover or seasonal or temporary workers can decrease training costs with Terminal Server because they can replace legacy text-based applications using unfamiliar and non-intuitive user interfaces with newer applications using the familiar Window-based user interface.
Many older business applications and development tools are no longer supported by the companies that released them, cannot be upgraded easily, and are often unfamiliar to today’s technical support staff. Terminal Server provides an efficient way to replace these obsolete programs and tools with off-the-shelf Windows-based applications and tools.
Terminal Server provides a smooth migration path because users with legacy software or hardware can gain access to new applications through the Terminal Server interface. For example, as an organization upgrades from Office version4.3 to Office 97, users can run older versions of Windows while taking advantage of the latest version of the application prior to a system refresh.

Cross-Platform Compatibility

Users of non-Windows–based computing platforms such as Apple® Macintosh®, UNIX, and Microsoft® MSDOS® can gain access to Terminal Server by using vendor add-on client/server software such as MetaFrame from Citrix Systems. By doing so, an organization can deploy one set of applications and one user interface across all client devices.

Organizations can lower training and administrative costs by training users on applications and interfaces together, regardless of platform. In addition, administrators can use Terminal Server to centrally manage applications and system configurations for users of all platforms.
By using Terminal Server, a company with mixed desktop environments can deploy common email clients, productivity suites, or other applications to every user while users continue to operate under their individual platforms for job-specific tasks. Thus, the company benefits from the wide range of Windows-based applications without having to replace all desktops.

See Planning Client Deployment in the “Project Plan Approved Milestone” section for more information on using vendor client software with Terminal Server.