Configuring Citrix MetaFrame for Windows 2000 Terminal Services

Скачать в pdf «Configuring Citrix MetaFrame for Windows 2000 Terminal Services»

additional CALs for users connecting from a Windows 2000 Professional client. To see how these pieces fit together see Figure 5.1.

Figure 5.1 Representation of Microsoft’s licensing scheme.



Terminal Terminal Terminal Terminal

Terminal Terminal Terminal Terminal


Be careful where you put your Terminal Servers in your domain when using Domain License servers. Terminal Servers use broadcasts to find the License Server. In a Windows 2000 domain with Enterprise License servers, the Terminal Servers will query the Active Directory for the location of the License Server. So, if you have a network device (such as a router) that does not forward broadcasts, you may have a problem. Most devices will let you configure them to forward broadcasts.

A Windows 2000 Terminal Server will keep track of all of the License Servers in its broadcast domain if it’s a Domain License server. It will check to ensure that its primary license server is available every one to two

hours. If its License Server doesn’t respond, then it will switch to another License Server in the domain. For this reason, you should have a backup License Server in each broadcast domain.

Licensing a Terminal Services Client

Users connecting to a Terminal Services session will need a separate license from the one required to connect on a file and print sharing basis. Windows 2000 Terminal Services requires the configuration of a Licensing Server. When a Terminal Services client wants to connect to a Windows 2000 Terminal Services server, it must first contact a License Server. The License Server will then assign a license to the client, and the connection will be allowed.

Скачать в pdf «Configuring Citrix MetaFrame for Windows 2000 Terminal Services»