I have a third-pary SSL certificate currently installed on a 2012 RDS single server which holds all of the RDS roles.  The existing certificate expires in 3 days, so I'm trying to replace it.  I've renewed the certificate with the supplier (GoDaddy) and installed it in the Personal store in the server.  I also removed the old certificate from the store, applied the new one to the Gateway server through the RDS Gateway Manager MMC, and then restarted the RDS services.  However, I can't figure out how to replace the current certificates that show under the RDS Deployment settings with the new one.  When I try to change the certificate, I'm going to Tasks/Edit Depoyment Properties. Then I select the Certificates section and get this display:

I checked the current certificate that's applied, and it's definitely the old one that expires in 3 days. I highlight and select RD Connection broker, and then choose Select existing certificate.  In that dialog box, when I select the option to apply the certificate that is stored on the connection broker host, it seems to accept it, but then it comes back with a warning:  "Could not configure the certificate on one or more servers. Ensure that the servers are available on the network...etc." Obviously, I'm doing something wrong, but I can't figure out how to apply the new cert pro

I don't have the exact same setup as you, but my RD Connection Broker and RD Gateway roles are located on the same server. Personally, I have never had any success telling it to use the same certificate installed for the Connection Broker, even though the certificate is the same. What I've had to do to get it to work is select the option to choose a different certificate instead of using the CB's cert, as follows:

Edit Deployment > Certificates > Select Existing Certificate > Choose a different certificate > Browse for the certificate file and enter the password > Check Allow the certificate to be added to the Trusted Root Certification Authorities store on the destination computers and click OK > Click Apply. 

With any luck, it will successfully change the certificate. 

I don't have the exact same setup as you, but my RD Connection Broker and RD Gateway roles are located on the same server. Personally, I have never had any success telling it to use the same certificate installed for the Connection Broker, even though the certificate is the same. What I've had to do to get it to work is select the option to choose a different certificate instead of using the CB's cert, as follows:

Edit Deployment > Certificates > Select Existing Certificate > Choose a different certificate > Browse for the certificate file and enter the password > Check Allow the certificate to be added to the Trusted Root Certification Authorities store on the destination computers and click OK > Click Apply. 

With any luck, it will successfully change the certificate. 

• Marked as answer by SYNOFF 14 hours 43 minutes ago

I had actually tried this before, and I couldn't figure out how to enter the password, believe it or not, because I didn't see anywhere designated in the dialog box for data entry! Your response made me take a second look at this process, and I discovered that the reason I couldn't figure out how to enter the password was basically due to the way the info is presented in the dialog box.  The word Password is there, but there's no obvious box or field area displayed to show you where to enter the password.  I was passing the mouse cursor over the area to the RIGHT of the word "Password" in the dialog box and nothing was happening. By chance, my cursor passed over the area BELOW the word "Password" and a faint green-outlined box popped up.  This is really idiotic on the part of Microsoft - why try to obscure the area on the screen where data has to be entered?

Anyway, I felt pretty stupid, but at least it worked. Thanks!

Glad to hear it worked! I know what you mean about the Password box, it can be tough to see especially through something like iLO. Unfortunately I'm a little too familiar with the certificates screen of 2012 RDS these days.