Citrix Ships the following Terminal Server products:

• Citrix MetaFrame XP for Windows 2003 Server
• Citrix MetaFrame XP for Windows 2000
• Citrix MetaFrame XP for NT 4.0 Server, Terminal Server Edition
• Citrix MetaFrame 1.8 for Windows 2000
• Citrix MetaFrame 1.8 for Windows NT 4.0 Server, Terminal Server Edition
• Citrix MetaFrame 1.0 for Windows NT 4.0 Server, Terminal Server Edition
• Citrix WinFrame 1.8
• Citrix WinFrame 1.7
• Citrix WinFrame 1.6

Notes:
Citrix MetaFrame XP and Citrix MetaFrame 1.8 support published or seamless applications. A seamless application is one that appears to run on the client desktop; while there may be a server desktop, on which the client's application runs, there is no way for the client to see that desktop. This creates some rather unique problems for the programmer who wants an application on the desktop to arbitrarily open a window that the user can see. As the desktop is not in the client's process tree, things that happen on the desktop do not get seen by the client.

Terminal Services is a licensing addition to Windows 2000 Server and Windows 2003 Server. Before any Citrix Metaframe product will work on W2K or W2K3, you must license Terminal Services.

Microsoft Windows NT 4.0 Server, Terminal Server Edition (NT4S-TSE) is a separate product from Windows NT4 Server.

Citrix WinFrame 1.6, 1.7, 1.8 are rewritten versions of Windows NT 3.51 Server. All the MetaFrame products are wrappers that ride on top of an existing Terminal Server / Terminal Services application. Our Terminal Services version will work with a Citrix wrapper around Terminal Services.

Note that there will not be a Terminal Services for Windows XP. XP is workstation only, and TS is for servers. Thus Citrix Metaframe XP will never work with Windows XP.

The main advantages of the Metaframe wrapper are:

• ICA protocol (less network bandwidth than the TS standard)
• Better load-balancing between servers and CPUs
• Seamless applications

Support for Windows Citrix XP Published Applications:

To support Published applications in Citrix XP:

1. Administrator first publishes the application.
2. Administrator modifies the application string in the published application to support 'print to fax'.

When the user 'runs' the published application, the daemon is launched, which in turn runs the published application. When the user closes the application, the daemon goes away. We support all concurrency issues. From the user's point of view, nothing is different (except that faxing now works). From the Administrator's point of view, they have only one extra step to publish the application.

To support running applications from the desktop, the daemon has to be activated in the normal way (run with no command line, ideally started from the start-up group when the user signs on).