| Event Information | According to Microsoft :
Cause :
This event is logged when the server certificate is not valid because the public key of the certificate contains an object identifier of 2.5.29.15, but does not support the Extended Key Usage (EKU) for encryption.
Resolution :
Check whether the TS Gateway server is configured to use a certificate that meets TS Gateway requirements
To resolve this issue, do the following:- Check whether the TS Gateway server is configured to use a certificate that meets TS Gateway requirements. For information, see "Check whether the certificate that the TS Gateway server is configured to use meets the certificate requirements" later in this topic. For information about TS Gateway certificate requirements, see "Certificate requirements" later in this topic.
- If the certificate that the TS Gateway server is configured to use does not meet TS Gateway certificate requirements, check whether another certificate is installed on the TS Gateway server that does meet the certificate requirements.
- If no other certificate is installed on the TS Gateway server that meets the certificate requirements, do the following:
- Obtain another 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.
Check whether the certificate that the TS Gateway server is configured to use meets the certificate requirements
To check whether the certificate that the TS Gateway server is configured to use certificate meets the certificate requirements:- 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, note the properties of the certificate that the TS Gateway server is configured to use, so that you know which certificate to check. At the top of the tab, the following properties for the certificate are displayed: Issued to, Issued by, and Expiration date.
- Click Select an existing certificate for SSL encryption (recommended), and then click Browse Certificates.
- In the Install Certificates dialog box, click the certificate that the TS Gateway server is currently configured to use (click the certificate with values that match the Issued to, Issued by, and Expiration date values displayed at the top of the SSL Certificate tab, as described in step 3), and then click View Certificate.
- In the Install Certificates dialog box, click the certificate that you want to check, 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. For information, see "Install the certificate on the TS Gateway server" later in this topic.
c.Configure the TS Gateway server to use the certificate for SSL. - Click OK to close the Properties dialog box for the TS Gateway server.
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, verify 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 the TS Gateway Manager snap-in console 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.
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.
|