Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Greater Than 2 Remote Desktop Connections

Status
Not open for further replies.

gharabed

Programmer
Sep 7, 2001
251
US
I am being told by a Windows Sys Admin that it is NOT possible to acquire additional licenses (I expect this would be Terminal Server licenses) to allow more than 2/3 Remote Desktop connections to our Windows 2003 server. Is this correct, or is it possible to purchase additional licenses to allow more than just 2 connections via Remote Desktop to Win2003? I'd like to allow at least 5 Remote Desktop sessions if possible.
 
For Remote Admin only you are allowed 2+1 console based RDP sessions. If you need more than this you will need to install full blown terminal services.
 
itsp1965 said:
If you need more than this you will need to install full blown terminal services.

Which you don't want if it's a DC.

The 2 existing connections are for REMOTE ADMINISTRATION USE ONLY, and are not for standard user application access.

Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -
 
What do you mean when you say "Remote Admin only"? What functionality does that entail. Basically I want to be able to have up to 5 users remote desktop in and perform various tasks such as SQL Server administration, and various other functions.

58sniper...you say "Which you don't want if it's a DC"...what is a "DC"? What type of functionality is considered "REMOTE ADMINISTRATION USE ONLY"? If you are saying that I don't need full blown terminal services then how would I legally establish more than 2 connections?
 
Why don't you just install the client admin tools such as SQL manager on a workstation and only use remote desktop to the server when absolutely necessary. I have most of my admin tools running on my workstation and I can perform most if not all tasks necessary...

:: baronne
------------------
"lekker, shot bru
 
There are times when you must be logged on to the server. In the case of SQL Server, there are certain DTS packages we have that require that the be run from the server itself (it not run as a job.) In addition, if we have to do anything on the local file system then we have to be logged on locally. Regardless, I just want to know if it is possible to have more than 2 users remote desktop in at any given time and if so, what licensing or products do I need in order to accomlish this.
 
There are two types of remote access; remote administration, and application.

Remote administration is for server and network administration only. Not for your domain users.

Application mode is for using hosted applications on the server itself.

As fore remote administration, which is what it sounds like you need, you don't want more than one person working on the server at any given time anyways. Why would you want 5 people all doing administrative tasks on the server at the same time? Even in the largest enterprises that doesn't happen.

Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -
 
Ok, well lets say I want multiple users to be able to connect in "application mode" to the server. Do I need additional Terminal Services licenses to be able to Remote Desktop in to the server? If not, then how do I get additional connection in application mode to be able to remote desktop into the server?
 
Not only do you need TS licenses, but you have to install the applications and have the licenses for the users that will be using them.

Let's say you have 5 users who you want to connect to the server and use Word. You would need 5 TS CALs and 5 Word CALs.

Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -
 
gharabed...
I am not convinced you need to have all these admins connecting and using the server at the same time.
If this is really what you want you're either going to have to license TS as sniper says, or find some third party tools to get around this.... sounds to me like you're being a bit stubborn and not thinking "outside the box"


:: baronne
------------------
"lekker, shot bru
 
I can tell you in my case, I am not constantly RD'd into the server all of the time. However, when I do need to get in there I am constantly stopped by the 2 user limitation because others are logged in. I can't say if they need to be RD'd in but I can tell you that I need to be. Again, it is not that common that I need to be RD'd in but when I need to I need to. I mean how do I get around having to debug a DTS package that runs as a job on this server when (because of the the way the DTS package is written) I have to be logged on to the server in order to run it? Looks like I need TS licenses.

All, thanks for your help on this.
 
There is seldom a technological solution to a behavioral problem, as Ed Crowley says.

If you people holding onto RDP sessions too long, you need to resolve that problem.

If you have to have more than two people connected to a server doing admin work at one time, there is a problem with the resources on that server. I've never seen a need to have more than 1 person logged onto a server at a given time. And would never recommend it. How do you know that the others that are connected aren't causing you more problems?

Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -
 
If you are concerned about users "hogging" RDP connections for remote admin, you can easily use the built-in TS command line or GUI utilities, to reset/logoff sessions or even send messages (if you need to ask nicely). It's all a matter of educating users. If users are not willing to logoff once they are done, then throwing a full blown TS environment is not the going to help.
 
I'm sure you can do stuff with DTS packages from the client admin tools...
you can check event logs remotely.
you can connect to the local drives remotely.
you can do all sorts remotely.


:: baronne
------------------
"lekker, shot bru
 
You could always use MSTSC with the /CONSOLE switch to connect to the server console session as long as no one is already using it.

--------------------------------------
"Insert funny comment in here!"
--------------------------------------
 
Correct, MSTSC /CONSOLE will get you connected when two sessions are in use. Other than that I would recommend using the timeout settings to boot users who have stayed idle too long.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top