Allow a user to launch 2 RDS RemoteApps as two different users
All Servers: Windows Server 2008 R2
All Clients: Windows 7 Pro 64-bit
We have a RDS server with which we do not give any of our users console access. They all use the 'RemoteApp' feature to launch apps via shortcuts on their desktop.
I have a unique situation where I need a single user (person) to be able to launch RDS RemoteApps both as himself (using his AD user), and as other (AD) users simultaneously. It doesn't seem possible that I'd be the first person to want to do this yet I can't find anything about it.
I want to be clear that the two RDS RemoteApps would have to be open as two different AD users (with two separate sessions on the RDS server) at the same time. Currently I am able to switch between launching the RemoteApp as different AD users but only if I close the App first which closes the RDS session. Once I've established a connection to RDS as the first user, the second App always opens in that same session as the same user.
All Clients: Windows 7 Pro 64-bit
We have a RDS server with which we do not give any of our users console access. They all use the 'RemoteApp' feature to launch apps via shortcuts on their desktop.
I have a unique situation where I need a single user (person) to be able to launch RDS RemoteApps both as himself (using his AD user), and as other (AD) users simultaneously. It doesn't seem possible that I'd be the first person to want to do this yet I can't find anything about it.
I want to be clear that the two RDS RemoteApps would have to be open as two different AD users (with two separate sessions on the RDS server) at the same time. Currently I am able to switch between launching the RemoteApp as different AD users but only if I close the App first which closes the RDS session. Once I've established a connection to RDS as the first user, the second App always opens in that same session as the same user.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
One thing you might try is having the user open a command prompt locally as the 2nd AD user account, and then launching the application from that command prompt. I do this frequently with local apps, and and frequently open up secondary network applications with the secondary account, and it maintains the security context correctly.
Coralon