Remote App duplicate processes

Question

Remote App duplicate processes

Gergely Szabó 10

We have a Windows server 2022 with RDS role, remote apps, and also the terminal gateway. When a user reconnect after idle timeout disconnected his session, he can reconnect to his disconnected session but the remote app (e.g. SSMS) is started again as a duplicate (two processes can be seen in task manager). This way he cannot continue where he left off. This problem is new to us as our previous Server 2019 RDS did not has this "bug". Any suggestions?

Anonymous

2025-02-05T02:19:47.09+00:00

Hello,

I was wondering if the issue is affecting all the RemoteApps you have published, or just specific ones?

Have you updated your server to the latest version?

I've searched on the website and didn't find any reports from other users about the same issue, so I'm not sure if it's a bug.
Gergely Szabó 10 Reputation points

2025-02-05T15:03:10.59+00:00

Hello,

Thanks for your reply. Now as I inspected the problem per your question only the SQL management studio (SSMS) does this. version currently: 20.2 but we are upgrading as new version is released. We started with 19.x when realized the problem.

The server is updated to the latest version, yes.

Some update for the original post: When a user reconnect after idle timeout he can access both SSMS instances. The previous one and the new one.
Ashenden, Simon 0 Reputation points

2025-03-11T08:26:11.35+00:00

Hello, we have this same issue logged by 2 of our users. We are also using SSMS 20.2 for remote app users. Our application is hosted in Azure Virtual Desktop and the problems started when we migrated away from local ESX hosts and onto the Microsoft services. I have seen the problem myself when testing the application , but it is also intermittently happening.

1 answer

Your answer

Anonymous

2025-02-05T02:19:47.09+00:00

Hello,

I was wondering if the issue is affecting all the RemoteApps you have published, or just specific ones?

Have you updated your server to the latest version?

I've searched on the website and didn't find any reports from other users about the same issue, so I'm not sure if it's a bug.
Gergely Szabó 10 Reputation points

2025-02-05T15:03:10.59+00:00

Hello,

Thanks for your reply. Now as I inspected the problem per your question only the SQL management studio (SSMS) does this. version currently: 20.2 but we are upgrading as new version is released. We started with 19.x when realized the problem.

The server is updated to the latest version, yes.

Some update for the original post: When a user reconnect after idle timeout he can access both SSMS instances. The previous one and the new one.
Ashenden, Simon 0 Reputation points

2025-03-11T08:26:11.35+00:00

Hello, we have this same issue logged by 2 of our users. We are also using SSMS 20.2 for remote app users. Our application is hosted in Azure Virtual Desktop and the problems started when we migrated away from local ESX hosts and onto the Microsoft services. I have seen the problem myself when testing the application , but it is also intermittently happening.

Answer 1

Welcome to the Microsoft Q&A Platform and thank you for posting your question!

You are experiencing duplicate RemoteApp processes, which often occur when multiple concurrent Remote Desktop sessions are allowed for the same user. Enforcing a single session per user can help resolve this.

Restrict Users to a Single Remote Desktop Session

This policy ensures each user can only have one active RDP session at a time. If a session already exists, Windows will reconnect to it instead of starting a new one, even when using a shared account. Troubleshooting steps:

1.Open Local or Domain Group Policy Editor (gpedit.msc or gpmc.msc).

2.Navigate to Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Connections

3.Locate Restrict Remote Desktop Services users to a single Remote Desktop Services session

4.Set it to Enabled

5.Run gpupdate /force to apply immediately on the RDS host

This prevents duplicate RemoteApp instances by reconnecting to the existing session instead of opening a new one.

Additionally, if you use Remote Desktop Gateway or RDS Collections, review their timeout and session limit policies to ensure there are no conflicts.

Please let me know if applying this policy resolves the duplicate session issue. Wishing you a smooth and successful fix!

Share via

Remote App duplicate processes

1 answer

Your answer