Configuring Citrix MetaFrame for Windows 2000 Terminal Services

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


You are also given the option of selecting whether or not to use standard Windows NT authentication for the connection. The type of Windows NT authentication used is determined by the environment your Terminal Services Server is running in. If your Terminal Services Server is running


in an Active Directory environment, then directory authentication will be used. If your Terminal Services Server is running in a traditional Windows NT Domain model, then domain authentication will be used. If your Terminal Services Server is a stand-alone server, then users will only be authenticated against the local user database. If you have some third-party authentication software installed, you can elect to use that instead of using the Windows NT authentication.


The Sessions tab allows you to set session limits (Figure 10.11). You can limit how long a session can remain idle before it is logged off. This will keep your connections from being tied up by users who forget to log off. Automatically logging off idle users will allow the connection to be used by someone else. This is particularly important when using modem lines for dialing in, because only one person can be attached to a modem at a time. If you don’t use a modem line, this may not be an issue. Disconnecting will also be beneficial if you are using per-server licensing, which limits concurrent user connections.


Figure 10.11 Connection Properties Sessions tab.

The way users may circumvent the idle timeout is by periodically moving the mouse so that the connection doesn’t appear to be idle. This is why you can also set an active session limit. This will limit the amount of time a user can stay connected, whether idle or not. This will help to prevent users from monopolizing a connection.

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