Thoughts from the EPS Windows Server Performance Team
One of the new features in Windows Server 2008 Terminal Services is Server Drain Mode. When a terminal server needs maintenance, the administrator may want to prevent users from logging onto a server which is about to be taken offline. In Windows Server 2003 there was a command-line tool to disable all remote connections; however, this prevented users with disconnected sessions from reconnecting, causing them to lose their work. To address this issue, in Windows Server 2008, the TS Server Drain Mode prevents new users from logging onto the server, while allowing currently logged on users to reconnect to their existing sessions. By waiting for existing users to save their work and log off, the administrator can take a terminal server down for maintenance without causing user data loss. Additionally, TS server drain mode is integrated with Session Broker Load Balancing, allowing one of the servers in a load balanced farm to be safely taken offline without any perceived change to end user experience or loss of service.
You can get more information about TS Server Drain Mode over at the Terminal Services Team Blog.
- CC Hameed
PingBack from http://www.ditii.com/2007/08/10/windows-server-2008-terminal-services-server-drain-mode/
In a load balanced environment this makes sense, but in a single TS environment this seems like a waste.
As the Admin, if I tell you the server will not be available at a certain time, then it won't be available and if you haven't finished your work, too bad. I can't wait around for you to decide you're done, while everyone else (including me) waits for you.
The least amount of downtime for all users results when the server goes down exactly at a plannned time and comes back up as soon as possible.
It would be pretty handy for everyone using 2003 also... Can Mircrosoft not put it together?