*EDITED AS INITIAL INVESTIGATION WAS WRONG*
Windows Server 2016 standard - AD Environment - Clients are working from home
RemoteApps worked fine for a while; then we had to create a new certificate because it expired (used for RD connection Broker, RD Web Access, RD Gateway).
Certificate is installed on local machine, put into trusted root.
On some of my clients machines; the remoteapps will connect; but the app wont launch! (Then the client get disconnected after a few seconds.) They are machines were it worked great before the new certificate.
Here are some tests / investigation I did :
- Not related to Windows edition (happened on a Win 7 pro, Win10 enterprise and some Win10 home)
- Not related to AD profil the user uses to connect (Profiles work on a computer that doesnt have this problem; and every AD profiles will do the same on computer affected by the problem)
- Does not seem to be network related (my own personnal PC has the same issue at my home; but my laptop works fine on my same network. NOTE : My laptop is not on their AD)
- FOR ALL : the remoteapps says it connected to the Gateway; but the app won't launch. (I see the user poping-up on the server; then they get disconnected almost instantly.
- FOR ALL : If I start their application before on a computer not affected by the problem; they CAN connected and see the app. Moreover; all additionnal apps will launch (from different rdp files)
- FOR ALL : They were able to connect ONCE without problem; then the problem appeared.
- I tried clearing the "cache" in HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default. But the problem persist.
- In one case (my personnal PC who had the problem); creating a new local Windows profile solved this issue. It didn't on 2 other PC I tried.
This has me racking my brain...
Thanks
(Sorry for original title who was wrong)