Configuring Citrix MetaFrame for Windows 2000 Terminal Services
Helps administrators get up to speed on MetaFrame, including designing solutions, installing the software, and configuring remote client access.
TABLE OF CONTENTS Configuring Citrix MetaFrame for Windows 2000 Terminal Services
Introduction
A Brief History of Citrix
More than five years ago, Citrix had a product on the market that could do what no other product on the market could do. Citrix WinView allowed a single DOS or Windows 3.1 application to be simultaneously shared from a single computer to multiple computers over phone lines or network links. This meant that companies that had installed hundreds of computers with individual phone lines and remote control software could then reduce their remote services costs and administrative hassles.
Back then, a single WinView server could host an average of 14 remote dial-in users simultaneously. As a result, an application only needed to be installed one time as opposed to the administrator performing 13 separate installations. Users received a major benefit too, in the fast response that an application loaded and ran compared to other remote control software or remote node software packages. Citrix WinView worked wonders for many, until Microsoft released Windows 95.
Citrix Moves to 32-bit Applications with WinFrame
When Microsoft produced Windows 95, Citrix found that there was a problem that WinView couldn t solve. Windows 95 could not share out a 32-bit application because it was based on IBM s OS/2 using 16-bit Windows emulation.
As a result, Citrix went to work with Microsoft, licensed the Windows NT 3.5 x operating system, and built Citrix WinFrame. The new WinFrame had the Windows 3.1 Graphical User Interface (GUI) because that s the GUI that Windows NT 3.5 x also had. Even so,...
Copyright Syngress Publishing, Inc. 2000 under license agreement with Books24x7
