I have re-newed the old certificate when it expired recently and the new cert does not bind to TSG. I have the same symptons ans decribed in KB 959120
"In TS Gateway manager, you attempt to assign a SSL certificate to a TS Gateway, it is initially accepted but when the console is refreshed a message is displayed saying:
"TSGateway is not fully configured as a TS gateway server. To access the settings required to complete TS Gateway configuration, click the link provided in each configuration task”.
The configuration status shows "A server certificate in not yet installed or selected"."
The old certificate will still bind and so will one from our internal PKI in AD but the new one does not.
The new cert meets all requiremments as far aas i can tell as described here on technet
- It binds in IIS to * (all IPs) on port 443
- The intended purpose of the certificate is server authentication. The Extended Key Usage (EKU) is Server Authentication (1.3.6.1.5.5.7.3.1). (and 1.3.6.1.5.5.7.3.2)
- The private key is installed
- It is not expired
When I configure it in the TSG mmc it will install but when i click refresh i get "The configuration status shows "A server certificate in not yet installed or selected".""
The cert is basically like the old one but with SHA2. Could that be the issue?
You can view the cert by going here tsg.symposionline.com with https