Remote Desktop Web Client Retains Old Certificate

%3CLINGO-SUB%20id%3D%22lingo-sub-3421823%22%20slang%3D%22en-US%22%3ERemote%20Desktop%20Web%20Client%20Retains%20Old%20Certificate%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3421823%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20using%20the%20Remote%20Desktop%20web%20client%20to%20deliver%20a%20%22TSVPN%22%20solution%20to%20third%20parties%20as%20well%20as%20an%20employee%20remote%20access%20method.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-server%2Fremote%2Fremote-desktop-services%2Fclients%2Fremote-desktop-web-client-admin%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-server%2Fremote%2Fremote-desktop-services%2Fclients%2Fremote-desktop-web-client-admin%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20certificate%20was%20expiring%2C%20so%20we%20updated%20the%20cert%20and%20now%20all%20users%20that%20used%20the%20service%20before%20are%20getting%20prompted%20for%20having%20a%20bad%20certificate.%26nbsp%3B%20It%20appears%20to%20be%20a%20browser%20cache%20issue%2C%20as%20dumping%20browser%20cache%20makes%20them%20re-download%20the%20web%20app%20and%20the%20problem%20goes%20away.%26nbsp%3B%20Opening%20Incognito%20or%20InPrivate%20has%20the%20same%20effect.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20question%20is%2C%20is%20there%20a%20way%20to%20tell%20the%20web%20client%20itself%20to%20dump%20its%20cache%20on%20its%20own%20when%20it%20runs%20into%20this%20cache%20problem%3F%26nbsp%3B%20Or%20are%20we%20going%20to%20have%20to%20ask%20everyone%20using%20the%20service%20to%20dump%20their%20browser%20cache%20every%20time%20we%20replace%20the%20certificate%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20tried%20fully%20uninstalling%20and%20unpublishing%20the%20web%20client%20package%20and%20reinstalling.%26nbsp%3B%20This%20successfully%20loads%20the%20new%20cert%2C%20but%20clients%20retain%20the%20bad%20cache%20and%20have%20to%20use%20the%20workaround.%26nbsp%3B%20It's%20too%20late%20to%20resolve%20this%20issue%20now%2C%20as%20users%20are%20already%20impacted%20and%20being%20instructed%20on%20the%20workaround.%26nbsp%3B%20Asking%20for%20next%20time.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-3421823%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Eremote%20desktop%20web%20client%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Occasional Visitor

We are using the Remote Desktop web client to deliver a "TSVPN" solution to third parties as well as an employee remote access method. 

 

https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/remote-deskto...

 

The certificate was expiring, so we updated the cert and now all users that used the service before are getting prompted for having a bad certificate.  It appears to be a browser cache issue, as dumping browser cache makes them re-download the web app and the problem goes away.  Opening Incognito or InPrivate has the same effect.

 

My question is, is there a way to tell the web client itself to dump its cache on its own when it runs into this cache problem?  Or are we going to have to ask everyone using the service to dump their browser cache every time we replace the certificate?

 

I've tried fully uninstalling and unpublishing the web client package and reinstalling.  This successfully loads the new cert, but clients retain the bad cache and have to use the workaround.  It's too late to resolve this issue now, as users are already impacted and being instructed on the workaround.  Asking for next time.

0 Replies