Re: what would happen if

I disagree with the genreal comment that there won't be any problems. Using
the same account to log into the same server causes many issues with the
profile. Expect weird issues like printers not working, printers changing,
amongst a whole host of other issues.

Jeff Pitsch
Microsoft MVP - Terminal Server

Forums not enough?
Get support from the experts at your business
http://jeffpitschconsulting.com

"Gregg Hill" <bogus@xxxxxxxxxxx> wrote in message
news:%23AtoqnNrGHA.4236@xxxxxxxxxxxxxxxxxxxxxxx
You can connect with the same name without any problems with the TS
itself, but that may cause problems with the application you try to use
within the session. Some apps will lock if they see the same user. Word,
Excel, etc could not care less.

BTW, per the EULA, the two Remote Desktop sessions are for remote server
administration only and are not for users to log in and run applications.

If using the same name and the user disconnects instead of logging off,
he/she could get either session. Typically, if user1 logs in as Joe, then
user2 logs in as Joe, and user1 disconnects before user2, then user2
disconnects and reconnects before user1 tries to reconnect, user2 will get
user1's session. That has been my experience anyway.

You can set the TS to allow only one connection per user at any given
time.

Gregg Hill



"djc" <noone@xxxxxxxxxxx> wrote in message
news:eXs2mxMrGHA.492@xxxxxxxxxxxxxxxxxxxxxxx
2 users both use the same user account to log into Remote Desktop on a 2k3
server?

for instance, one logs in, a session is created and he is working away,
then after that, the second person logs in using the *same* user account.
I did this (not on purpose) and saw that another session for this user
*was* created. This raised many questions for me. As soon as I realized
the situation I logged off and back on as a different user. I don't want
to 'experiment' with this on a production server.

if both users disconnect and then one reconnects later which session
would he connect to? considering these are both the same user account
what about the user profile changes like shortcuts etc..? I would have
expected that both sessions used the same user profile since its the same
user account but I don't believe thats what happened.

just wondering. Any input is appreciated.





.

Relevant Pages

  • Re: FW: Trace of 139 attack?
    ... /complex—Forces passwords to have a mixture of upper ... > the admin account on local logins (physical security ... >> deleting the logs he cannot do it. ... >> ur Server ur logs will ...
    (Focus-Microsoft)
  • Re: Terminal Services Kiosk
    ... the locked-down account is the Active Directory account in ... the desktops, not the local accounts in the TS server. ... programs or kill the RD session? ... So one user logs in to the workstation ...
    (microsoft.public.windows.terminal_services)
  • Re: what would happen if
    ... Using the same account to log into the same server causes many issues with ... Microsoft MVP - Terminal Server ... he/she could get either session. ... Typically, if user1 logs in as Joe, then ...
    (microsoft.public.windows.terminal_services)
  • Re: what would happen if
    ... Using the same account to log into the same server causes many issues with ... Microsoft MVP - Terminal Server ... he/she could get either session. ... Typically, if user1 logs in as Joe, then ...
    (microsoft.public.windows.terminal_services)
  • Re: Single user account and terminal services 2008 printing woes
    ... Can I use a single monolithic account for all users of the Terminal Servers - This is a big "no no" and probably stems from another ... Consistently setting the same printer in a TS session - This is easily accomplished using mechanisms such as the PrintUI interfaces to map ... Server will automatically point and print the drivers from the trusted source - the print server. ...
    (microsoft.public.windows.terminal_services)
Loading