Server Software Requirements

Server Software Requirements

Citrix MetaFrame Presentation Server 3.0 can be installed on Microsoft Windows 2000 Server provided that it is at Service Pack 4 or higher. It can also be installed on Windows Server 2003. In addition to installing the server software, you have to enable Terminal Services in both Windows 2000 Server and Windows Server 2003.

In Windows 2000 Server, you have to put the server in Application Server mode before users would be able to log in and before you can install Citrix MPS 3.0. With the introduction of Windows Server 2003, Microsoft shuffled things around a bit. For example, with Windows 2000 Server, you needed to enable Terminal Services in one of two modes: either Remote Administration, which allows only two simultaneous connections for administrative purposes, or Application Server, which allows multiple users to simultaneously log in to the TS.

Windows Server 2003 has Remote Desktop enabled by default and is no longer a component of Terminal Services. Now when you need to place Terminal Server in what used to be Application Server mode, you need to enable Terminal Server from the Add/Remove Windows Components screen in Add or Remove Programs.

Note

In Windows Server 2003, some Terminal Services components have been renamed . For example, Remote Administration mode has now become Remote Desktop and is installed by default.

You've surely heard the expression "a picture is worth a thousand words." In the exercises to follow, notice the difference between enabling Terminal Services in Windows 2000 Server and Windows Server 2003.

In Windows 2000 Server, do the following:

1.	Choose Start, Settings, Control Panel, Add or Remove Programs, Add/Remove Windows Components.
2.	Scroll down and check the box next to Terminal Services, as shown in Figure 3.1. Then click Next . Figure 3.1. Enabling Terminal Services in Windows 2000 Server.
3.	The next screen allows you to select between Remote Administration mode or Application Server mode, as shown in Figure 3.2. Choose Application Server mode and click Next. Figure 3.2. Terminal Server Mode selection screen.
4.	You are prompted to make a decision on the default permissions for application compatibility. You can choose between Permissions Compatible with Windows 2000 Users or Permissions Compatible with Terminal Server 4 Users. Unless you have an old application that requires more relaxed Registry permissions, choose the first option, which is Permissions Compatible with Windows 2000 Users.
5.	Click Next and then Finish to exit the wizard.

Note

In Windows 2000 Server, the component that allows multiuser access on the server is named Terminal Services, whereas in Windows Server 2003 it is renamed Terminal Server.

To enable Terminal Server in Windows Server 2003, do the following:

1.	Choose Start, Settings, Control Panel, Add or Remove Programs, Add/Remove Windows Components.
2.	Scroll down and check the box next to Terminal Server, as shown in Figure 3.3. Then click Next. Figure 3.3. Enabling Terminal Server in Windows Server 2003.
3.	You are presented with a window informing you that you are enabling Terminal Server to allow for multiple simultaneous connections. Click Next to continue.
4.	Similar to Windows 2000 Server, you are prompted to choose the application permissions you want to enable on the Terminal Server. You can select between Full Security, which offers the latest security enhancements that Windows Server 2003 offers, or Relaxed Security if you want to allow users more access to the Registry and file system. Relaxed permissions may be necessary depending on whether your application was designed for Windows Server 2003. Consult your application's vendor and then click Next to continue.
5.	Click Next and then Finish to exit the wizard.

Terminal Services Licensing

Whether you are installing Citrix MetaFrame Presentation Server 3.0 on Windows 2000 Server or on Windows Server 2003, you need to install the Terminal Services Licensing component on a server. This server must be accessible to all your TS/MPS servers and should be activated with valid Terminal Services Client Access Licenses. If you don't install any licenses, the Terminal Services Licensing Server will issue temporary licenses that are valid for a period no longer than 90 days. After this period, if no valid license is installed, connections will be refused .

In addition, a TS or MPS server has a grace period of no longer than 120 days to find and contact a Terminal Services Licensing Server. After this period, connections will also be refused.

Caution

As of this publication, Windows Server 2003 does not enforce TSCALs when the server is in Per User mode; it relies on the honor system. However, based on previous versions such as Windows 2000 Server, Microsoft is poised to enforce this policy once again. We strongly recommend you install proper TSCALs on your TS Licensing Server so that you avoid any interruptions in the event that a hotfix should be installed to address this issue.

Note

Terminal Services Licensing does not have to be installed on a domain controller but is recommended.

Protocols

Both Windows 2000 Server and Windows Server 2003 install TCP/IP by default. If this is the only protocol you will be using on your network, you don't have to worry about doing anything else. However, if you plan to use any other protocols such as IPX, SPX or NetBIOS, it is recommended that you install them prior to installing Citrix MPS 3.0.

Installing these protocols configures Independent Computing Architecture (ICA) to use these protocols properly by creating the necessary connections. In addition, if you plan to use SNMP in your environment to monitor and manage your servers, this would be a good time to install that as well.

Note

With Windows Server 2003, the only protocol that remote users can use to connect to MPS 3.0 is TCP/IP. Support for IPX/SPX and asynchronous connections has been disregarded.