G
Guest
I have a client that has two RDP sessions pointed to the same terminal
server. He uses a separate user ID for each session because the server
force-runs a specific app depending on which user ID he uses. However, when
he saves the user ID for Session #1, it also changes the user ID for session
#2 (i.e. they are always both the same). This happens even when I log onto
his PC as a domain admin, and it never happens on the other five computers in
the office that function the same way for their respective users.
In fact, when I delete the RDP session and attempt to create a new one, the
last-saved user name is already there. Is there a setting somewhere that
locks in all RDP sessions to a single user ID (or a registry hack to set it
back to the way it should be)? This is, of course, RDP client 6.0 that was
just released.
server. He uses a separate user ID for each session because the server
force-runs a specific app depending on which user ID he uses. However, when
he saves the user ID for Session #1, it also changes the user ID for session
#2 (i.e. they are always both the same). This happens even when I log onto
his PC as a domain admin, and it never happens on the other five computers in
the office that function the same way for their respective users.
In fact, when I delete the RDP session and attempt to create a new one, the
last-saved user name is already there. Is there a setting somewhere that
locks in all RDP sessions to a single user ID (or a registry hack to set it
back to the way it should be)? This is, of course, RDP client 6.0 that was
just released.