The Windows 2000 Terminal Server is very easy to install and configure. However, the real value of using the Terminal Server is to provide applications for users that might not otherwise be available on
their client operating systems. There are a number of factors you must consider before implementing a Terminal Server solution for your organization. In this lesson, we will discuss some of those issues.
Applications that you install on a server running Terminal Services must be compatible with Windows 2000. If an application does not run on Windows 2000, it will not run in on the Terminal Server since the Terminal Server must itself run on Windows 2000.
Windows-based, 32-bit applications operate more efficiently than 16-bit applications by taking full advantage of 32-bit hardware and operating systems. Running 16-bit applications on a Terminal Server
can reduce the number of users that a processor can support by as much as 40 percent and increase the memory required per user by 50 percent. The best example of a 32-bit application is Microsoft Office 2000, which is optimized for Terminal Server deployment.
Microsoft has set up a testing program with
Man in the Middle Attack
Resources.aspindependent testing companies to assist organizations in deploying applications with Terminal Services.
Microsoft maintains a site about creating your own http://microsoft.com/ntserver/terminalserver/application compatibility script for older applications. Note: This resource applies to the Windows NT 4.0 Terminal Server, and there may be differences between it and the Windows 2000 Terminal Services. The next lesson looks at how hardware requirements affect the installation process.