| Event Information | According to Microsoft :
Cause :
This event is logged when the Terminal Services Gateway service requires a valid Secure Sockets Layer (SSL) certificate to accept connections.
Resolution :
Obtain, install, and configure a certificate that meets TS Gateway server certificate requirements
To resolve this issue, do the following:- Obtain a certificate that meets TS Gateway certificate requirements.
- Install the certificate on the TS Gateway server.
- Configure the TS Gateway server to use the certificate for SSL.
To perform these procedures, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
Install the certificate on the TS Gateway server
To install the certificate on the TS Gateway server:- On the TS Gateway server, open the Certificates snap-in console. If you have not already added the Certificates snap-in console, you can do so by doing the following:
a.Click Start, click Run, type mmc, and then click OK.
b.On the File menu, click Add/Remove Snap-in.
c.In the Add or Remove Snap-ins dialog box, in the Available snap-ins list, click Certificates, and then click Add.
d.In the Certificates snap-in dialog box, click Computer account, and then click Next.
e.In the Select Computer dialog box, click Local computer: (the computer this console is running on), and then click Finish.
f.In the Add or Remove Snap-ins dialog box, click OK. - In the Certificates snap-in console, in the console tree, expand Certificates (Local Computer), and then click Personal.
- Right-click the Personal folder, point to All Tasks, and then click Import.
- On the Welcome to the Certificate Import Wizard page, click Next.
- On the File to Import page, in the File name box, specify the name of the certificate that you want to import, and then click Next.
- If the Password page appears, if you specified a password for the private key associated with the certificate earlier, type the password, and then click Next.
- On the Certificate Store page, accept the default option, and then click Next.
- On the Completing the Certificate Import Wizard page, confirm that the correct certificate has been selected.
- Click Finish.
- After the certificate import has successfully completed, a message appears confirming that the import was successful. Click OK.
- With Certificates selected in the console tree, in the details pane, confirm that the correct certificate appears in the list of certificates on the TS Gateway server. The certificate must be under the Personal store of the local computer.
Configure the TS Gateway server to use the certificate for SSL
After you install an appropriate certificate on the TS Gateway server, you must use TS Gateway Manager to configure the TS Gateway server to use the certificate for SSL. If you do this by using any other method, TS Gateway will not function correctly.
To configure the TS Gateway server to use the certificate for SSL:- Open TS Gateway Manager. To open TS Gateway Manager, click Start, point to Administrative Tools, point to Terminal Services, and then click TS Gateway Manager.
- In the TS Gateway Manager console tree, right-click the local TS Gateway server, and then click Properties.
- On the SSL Certificate tab, click Select an existing certificate for SSL encryption (recommended), and then click Browse Certificates.
- In the Install Certificates dialog box, click the certificate that you want to use, click View certificate, and then review the certificate properties to ensure that it meets TS Gateway requirements.
- If the certificate meets the requirements for TS Gateway, click Install. If the certificate does not meet the requirements for TS Gateway, select another certificate that does and install it (if another certificate is available), or do the following:
a.Obtain another certificate that meets TS Gateway certificate requirements.
b.Install the certificate on the TS Gateway server, as described earlier in this topic.
c.Use this procedure to configure the TS Gateway server to use the certificate for SSL. - Click OK to close the Properties dialog box for the TS Gateway server.
- If this is the first time that you have configured the TS Gateway server to use an SSL certificate, after you complete this procedure, you can confirm that the procedure was successful by viewing the TS Gateway Server Status area in TS Gateway Manager. Under Configuration Status and Configuration Tasks, the warning stating that a server certificate is not yet installed or selected and the View or modify certificate properties hyperlink are no longer displayed.
Certificate requirements
Certificates for TS Gateway must meet these requirements:- The name in the Subject line of the server certificate (certificate name, or CN) must match the DNS name that the client uses to connect to the TS Gateway server, unless you are using wildcard certificates or the SAN attributes of certificates. Multiple CNs are not supported. If your organization issues certificates from an enterprise certification authority (CA), a certificate template must be configured so that the appropriate name is supplied in the certificate request. If your organization issues certificates from a stand-alone CA, you do not need to do this.
- The certificate is a computer certificate.
- 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).
- The certificate has a corresponding private key.
- The certificate has not expired. We recommend that the certificate be valid one year from the date of installation.
- A certificate object identifier (also known as OID) of 2.5.29.15 is not required. However, if the certificate that you plan to use contains an OID of 2.5.29.15, you can only use the certificate if at least one of the following key usage values is also set:
CERT_KEY_ENCIPHERMENT_KEY_USAGE, CERT_KEY_AGREEMENT_KEY_USAGE, and CERT_DATA_ENCIPHERMENT_KEY_USAGE. - The certificate must be trusted on clients. That is, the public certificate of the CA that signed the TS Gateway server certificate must be located in the client's Trusted Root Certification Authorities store on the client computer.
|