What to Expect From the Windows Terminal Services in a 64-Bit Environment
Sunday, 16 April 2006 by Michel Roth
A new aricle on MSTerminalServices.org by Brien M. Posey on what to expect from the Windows Terminal Services in a 64-Bit environment.

"In this article, I will discuss why 64-bit servers may be a worthwhile investment for organizations that are currently using Windows Server 2003 based terminal servers. One of the most frustrating aspects of administering a Terminal Server environment is the fact that it can take relatively few user sessions to max out a terminal server’s capabilities. Microsoft’s documentation states that there is an effective limit of 300 user sessions per terminal server. However, factors such as the number of applications being run, the quantity of resources consumed by the various applications, the end user’s level of activity, and the server’s hardware can all make the actual number of sessions that a terminal server can support much, much lower than the stated value. One technology that is promising to help to limit the impact of these factors though is the gradual shift to 64-bit computing."

Read the full article here.

Related Items:

What to Expect From the Windows Terminal Services in a 64-Bit Environment (Part 2) (17 May 2006)
New MSTerminalServices.org Article: Juggling Terminal Service Resources (17 November 2005)
Troubleshooting Common Terminal Service Connection Errors (13 March 2007)
Using The Terminal Services through Internet Information Server (5 December 2005)
An Introduction to Terminal Services Remote Programs (Part 1) (12 October 2006)
An Overview Of Longhorn Server’s Terminal Service Gateway (Part 1) (6 July 2006)
MSTerminalServices.org Article: Securing Windows Terminal Services (8 February 2006)
RDC Enhancements and Administrative Sessions (20 February 2008)
An Introduction to Terminal Services Remote Programs (Part 2) (21 November 2006)
Using SoftGrid In A Terminal Service Environment (16 February 2007)
Comments (0)