Quick question: I have a situation where I need to let multiple people on different PCs log into one server 2008 machine as administrator simultaneously over remote desktop. I have the CALs for it, it's just not set up correctly. When one user tries to log in, it boots the other out. What I need is to present to them a different session, just each as logged in as admin. Sorry for the slightly rambling post, I'm new here. Thanks!
A single user account can have multiple sessions in Windows 2008. On the server, run tsconfig.msc to bring up the Remote Desktop Session Host Configuration. Under "Configuration for server", double-click any of the general settings. Uncheck the box next to "Restrict each user to a single session" and click OK.
That's by design. Give their accounts the proper permissions they need on that server and have them log on as themselves instead.
Is there any special reason for them to share an account?
If the server is set up as a real Terminal Server (ie not just using the default Administrative Remote Desktop) then the single session per user enforcement should be possible to turn off. But the additional problem of never being able to reconnect to the same session seems like an annoying prospect - so setting forced logoff after some time would be essential and so on... it's just, wrong ^^
You can do this by setting the fSingleSessionPerUser registry key: http://remotedesktoprdp.com/force-single-session-allow-multiple-sessions-per-user
Yes it is possible even on windows home or home premium it can be done both manually or with a download. I use it all the time because it saves me allot of time. Its called Concurrent RDP Patcher and can be downloaded here : http://www.raymond.cc/blog/download/?did=125
This allows more than one user to access the device with only one admin logon.
If all the users are using the same username to login, I dont even see the need to spend on the CALs. I suggest you create unique accounts for all users, and activate the CALs with per user on the terminal server.
(CALs are used per user or per device basis)
While you can do as Craig Putnam suggests, I would not. Instead, create individual admin accounts on the machine for each user. This promotes accountability. Even with auditing disabled/not configured, some things can be tracked and you can at least have a chance at identifying the person/persons who mess up the server.
Can you otherwise clarify why it must be the way they want it? When you give full details, we may be able to present other ideas that can be even better than what you were initially hoping for...