1

I have a user with 2 different AD accounts. (User1 and User2)
When User1 signs into Remote apps they see only want that account is supposed to see
When the start Chrome, or Edge as User2 (right click-Run as) and go to the Remote app page, they only see what that account is supposed to see.

here is the issue

The app they see and Run is SSMS.exe Starts up as expected…EXCEPT… the user account that it is trying to sign in as is User1.

Any ideas?

Works as i am expect when run Chrome as a different account… worked for this user previously as well

6 Spice ups
2

Why are they doing it this way?

Can’t they open a second browser ab, preferably in-private browsing as user2 and just run the app directly.

2 Spice ups
3

Same issue.
For whatever reason it is not passing the username/password of the person running the icon published to the actaul application

2 Spice ups
4

What happens when they use a separate different browser?
ie: IE, or Edge, or Opera, or insert your preference
and RUN AS on this other browser for User#2 to run the SSMS.exe

Does it still pull User#1?

2 Spice ups
5

Is there a reason that user1 can’t be granted rights to SSMS instead of trying to run as another user under the current users session?

2 Spice ups
6

due to the User1 account is a ‘regular’ account while User2 account is a priviledged account

2 Spice ups
7

correct. had them try chrome and edge…ssms still auto populate with their User1 account name…which wouldn’t normally be so bad, but changing it in ssms isn’t an option as the box is greyed

3 Spice ups
8

From a domain perspective, I get it, but for SQL, do they have to use a dedicated ‘admin’ account?

There are ways of running a .bat file before launching SSMS, so credentials are put in before it runs, this will pass the credentials through.

3 Spice ups
9

Hey @JohnFLi, I’ve seen this behavior before.

From what you described, it sounds like the issue is related to credential caching and how RemoteApps handle authentication context. Even when you launch a browser as User2, the RemoteApp (like SSMS) may still be pulling credentials from the original session (User1), especially if those credentials were cached or if the app is launched in a way that doesn’t fully isolate the user context.

  1. Try Clearing Cached Credentials using Credential Manager as they can override what you expect to be used.

  2. Even when using “Run as,” some browsers still hold onto session data. Try using a completely separate browser profile or InPrivate/Incognito mode.

  3. Avoid “Remember My Credentials” in RDP as it can sometimes persist across sessions. You can also disable that completely through GPO.

Hopefully, one of these is helpful.

2 Spice ups