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.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

David Johnson, CD, MVPOwnerCommented:
AFAIK you can't do this.. you can launch 1 as remote app and the 2nd one as remote desktop

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
I primarily deal with Citrix and have done very little with RDS without Citrix.

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.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.