Re: RDP sessions with Terminal Services
So you are all logging on with the same credentials?
I see three possible solutions:
* ask the clients to create different credentials for each of you.
This has the added feature of trackability (you can track later who
did what)
* keep the same credentials, but ask the clients to enable multiple
connections per user. This will enable you to have simultaneous
connections. You will still need to coordinate your actions,
though.
* organise the work between you. This might be the best solution.
Multiple administrators working on the same server at the same time
without knowing about each other is a scary scenario to me.
If you actually want to avoid connecting to a client's server when
someone else is already connected, you could run the command
"netstat -b" (without the quotes) before starting mstsc, to check
if there is already an active session to the remote host.
Run netstat /? to see all the command parameters, you might want
some other output as well.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting:
http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
"Tristan" <Tristan.Salisbury@bluespier.com> wrote on 19 feb 2008
in microsoft.public.windows.terminal_services:
> Hi,
>
> Were not connecting on the console session just a standard rdp
> session. The problem we have is the clients server's are set
> their end so we cant edit the settings. Therefore we could do
> with having a local program that notifys my colleagues who's
> connected on which site.
>
> Thanks
>
>
> "Patrick Rouse" <PatrickRouse@discussions.microsoft.com> wrote
> in message
> news:8ADFBB8A-284C-4DE5-A339-D36384F672A2@microsoft.com...
>> Are you connecting to the console sessions of the remote
>> computers? If so,
>> and more than one person does this then one gets their session
>> reset. Try connecting without using the /console switch.
>>
>>
>> --
>> Patrick C. Rouse
>> Microsoft MVP - Terminal Server
>> SE, West Coast USA & Canada
>> Quest Software, Provision Networks Division
>> Virtual Client Solutions
>> http://www.provisionnetworks.com
>>
>>
>> "Tristan" wrote:
>>
>>> Our Company currently have a dedicated server with server 2003
>>> installed on
>>> it. My colleagues connect to the server and then RDP out of
>>> the dedicated
>>> server to clients servers.
>>>
>>> This is becoming an issue now as more of us are using the
>>> dedicated server
>>> and connecting to the same client servers.
>>>
>>> So this is resulting in taking over other colleagues sessions
>>> which can be
>>> very frustrating.
>>>
>>> Is their any software out their which can prompt the users on
>>> server 2003 which clients are logged onto which client
>>> machine?
>>>
>>> Any other useful thoughts would be much appreciated.
>>>
>>> Tristan