This article explains how to resolve the "Identity Certificate" warning that appears when connecting to a Hostek Windows Server via Remote Desktop Protocol (RDP). This issue typically occurs when the client device does not recognize the server's certificate as trusted, and it can be resolved by configuring the local client or the server's certificate settings.
Before you begin
You will need:
Administrator access to the Windows Server.
Access to the client device (PC or Mac) used to connect to the server.
Resolve the warning on the client device
In most cases, the warning occurs because the client device is not configured to automatically trust the server's certificate. You can resolve this by adjusting the settings on the machine you are using to connect.
Open the Remote Desktop Connection application on your local computer.
Click Show Options at the bottom of the General tab.
Navigate to the Advanced tab.
Click the Settings button under the Connect from this computer section.
In the Remote Desktop window, select the Experience tab.
Ensure that the Persistent bitmap caching is enabled (this is a standard setting, but ensures the connection remains stable).
To specifically address the certificate, you may need to click More... or navigate to the Experience tab and ensure the connection is configured to accept the certificate from the specific server address.
Note: If the warning persists on a specific machine, it may be due to the local machine's certificate store not containing the root certificate for the server. In this case, the certificate must be manually imported into the "Trusted Root Certification Authorities" folder on the local machine.
Resolve the warning via server configuration
If the warning appears for all users connecting to the server, the issue may lie with the certificate assigned to the Remote Desktop service on the server.
Log in to the Windows Server.
Open Server Manager.
Select Tools > Remote Desktop Services (or Remote Desktop Services Configuration).
Navigate to the Remote Desktop section and select RD Gateway or Remote Desktop Session Host depending on your configuration.
Locate the Certificates tab.
Ensure a valid, non-expired certificate is assigned to the service.
If the certificate is self-signed, the warning will continue to appear for users unless the certificate is manually trusted on every client device.
Confirm the result
When you initiate a Remote Desktop connection, the "Identity Certificate" warning should no longer appear.
You should be prompted directly for your credentials (if not already saved) or connected directly to the desktop.
If the warning still appears after configuration
If the warning persists after updating the server's certificate, the issue is likely a local cache or a specific security policy on the client machine.
Clear the RDP Cache: On the client machine, go to the Control Panel and search for Internet Options. Under the Content tab, click Clear next to "Delete files for Internet Explorer" (this clears the SSL state).
Check the Hostname: Ensure you are connecting using the Fully Qualified Domain Name (FQDN) of the server (e.g.,
server.example.com) rather than the IP address. Certificates are often tied to the hostname; connecting via IP address will frequently trigger a certificate warning.
Limitations
This procedure does not resolve issues caused by an expired certificate; if the certificate is expired, the connection will be blocked by the client's security policy.
If you are using a third-party Remote Desktop client (such as Microsoft Remote Desktop for Mac or mobile devices), the certificate management may differ based on the specific application's security settings.
