 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Windows Server Forum / Windows 2000 / Terminal Services / January 2005Terminal Services to Windows 2003 Server
I would like to know if there is a limited number of concurrent sessions to terminal service to Windows 2003 server. Thanks. Not to Terminal Services, which implies in Application Server mode. The number of connections is only limited by the number of licenses that you purchase and install on the TS Licensing server. And the hardware of your server, of course (performance). If you mean what was called "Terminal Services in Remote Administration mode" on a W2K server: this is now called Remote Desktop for Administration on 2003. You *don't* have to install it, it is already there. Just enable it like on XP, in System - Properties - Remote. You get a maximum of 3 concurrent connections: 2 normal connections and one to the actual console (type mstsc /console). No additional licensing requirements. -- Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server http://hem.fyristorg.com/vera/IT --- please respond in newsgroup, NOT by private email --- "Diane Walker" <ett9300@yahoo.com> wrote on 26 jan 2005 in microsoft.public.win2000.termserv.clients: > I would like to know if there is a limited number of concurrent > sessions to terminal service to Windows 2003 server. Thanks. Thank you very much for clarifying. > Not to Terminal Services, which implies in Application Server mode. > The number of connections is only limited by the number of licenses [quoted text clipped - 12 lines] >> I would like to know if there is a limited number of concurrent >> sessions to terminal service to Windows 2003 server. Thanks. What is the difference between mstsc /console and the 2 normal connections? Thanks. > Not to Terminal Services, which implies in Application Server mode. > The number of connections is only limited by the number of licenses [quoted text clipped - 12 lines] >> I would like to know if there is a limited number of concurrent >> sessions to terminal service to Windows 2003 server. Thanks. mstsc /console connects you to session 0, which is the console session. You will see exactly what is on the physical console. There can be only one connection to session 0. If someone else is logged on to the physical console, you will be offered to end that session and take over the console session (if you are Administrator). Use this if you want to install software remotely. Just starting the rdp client (which is mstsc.exe) from the start menu gives you a normal session, with numbering from 1 and higher. You won't see all the icons in the system tray and you won't see any error messages that are only visible on the console. Good for monitoring and such. -- Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server http://hem.fyristorg.com/vera/IT --- please respond in newsgroup, NOT by private email --- "Diane Walker" <ett9300@yahoo.com> wrote on 27 jan 2005 in microsoft.public.win2000.termserv.clients: > What is the difference between mstsc /console and the 2 normal > connections? Thanks. [quoted text clipped - 17 lines] >>> concurrent sessions to terminal service to Windows 2003 >>> server. Thanks. Thank you very much for the explanation. Now, I see the difference between the two. Again, thank you very much for your assistance. > mstsc /console connects you to session 0, which is the console > session. You will see exactly what is on the physical console. [quoted text clipped - 31 lines] >>>> concurrent sessions to terminal service to Windows 2003 >>>> server. Thanks. |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.