ass17 Posted July 7, 2020 Posted July 7, 2020 Hi All, Got a weird issue where last night I replaced our soon to be expired wildcard very with a new one across all our RD servers, either in Server Manager or in administrative tools. Have to replace in loads of places!! I can remote in fine using an RDP file from the RDWeb interface but if I do it in-browser I get an oops we can’t connect you error. The cert in the image is the new cert Any help would be grate my appreciated [emoji1303]
Steve21 Posted July 7, 2020 Posted July 7, 2020 By in browser do you mean the new HTML5 one? If so did you reimport the new cert for that specifically? Import-RDWebClientBrokerCert etc ? Steve
ass17 Posted July 7, 2020 Author Posted July 7, 2020 By in browser do you mean the new HTML5 one? If so did you reimport the new cert for that specifically? Import-RDWebClientBrokerCert etc ? Steve Is this a must? I though once you had applied it to all the service roles that would be enough? See image
Steve21 Posted July 7, 2020 Posted July 7, 2020 Pretty sure it had to be done each time, as same when you installed it in the first place, you had to manually install the cert for the WebClient even though it was already installed for the rest of it. If it was using the other ones surely it'd work without installing the cert during install? But not 100% If you browse to https://rdweb.yourschooldomain.com/rdweb/webclient/config/"certname.cer" does it download the new one or old? Steve
ass17 Posted July 7, 2020 Author Posted July 7, 2020 Tried the import-rdwebclientbrokercert and it worked! Thanks!!
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now