• Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint

Best Practices

  • Install Terminal Services on a member server, but install Terminal Services Licensing on a domain controller. Terminal Services uses a significant amount of memory, CPU, and network traffic. A domain controller requires the same resources.

  • Install Terminal Services in Remote Administration mode on every Windows 2000 server in your network. This will allow you to remotely administer your Windows 2000 servers without adding a significant performance load to your system.

  • Install Terminal Services and applications on an NTFS partition. Security is essential in this type of multi-user environment in which data files may be shared.

  • Use the tsshutdn command to shut down the Terminal server. Using the Shut Down option on the Start menu will not notify users before ending their sessions.

  • After you have installed Terminal Services and applications, do not remove Terminal Services without reinstalling all applications. Programs that were installed while Terminal Services was in effect were changed for multi-user access and may not work properly in single user mode.

  • Start users who need access to only one program without a desktop by using the Initial Program option. This will conserve system resources and improve security.

  • Assign users who will be logging on to Terminal Server a specific Terminal Server profile. Many of the settings used in a normal profile are too graphics-intensive for efficient use in a Terminal Services session. Creating a specific profile allows the user to store a profile just for Terminal Services sessions.


PREVIEW

                                                                          

Not a subscriber?

Start A Free Trial


  
  • Creative Edge
  • Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint