Self signed certificates and Remote Desktop new user question

Scott_P Renton 0 Reputation points
2026-11-19T22:33:58.39+00:00

Hello;

I recently got put in charge of some windows servers, and I am not familiar with them. I connected to one server via the Remote Desktop Connection app to the servers, using the IP address, rather than the name. I noticed that the connection is encrypted using a self-signed certificate on the server, and that that certificate has an expiration date. My question is: Do I, as the windows server admin, have to create a new self-signed certificate for the server when that self signed certificate expires, or does the server create it's own?

Thanks, a new windows server user

Windows for business | Windows Server | User experience | Remote desktop services and terminal services
0 comments No comments

2 answers

Sort by: Oldest
  1. AI answer

    2026-11-19T22:34:49.7333333+00:00

    You do not need to renew the default Remote Desktop self-signed certificate manually; Windows recreates it after it expires. ^1^

    What happens automatically

    The certificate is used by the Remote Desktop listener to encrypt RDP traffic. With the default configuration:

    • Windows generates the self-signed certificate.
    • The default certificate expires after six months.
    • Windows recreates it after expiration. ^1^
    • Because the replacement has a new identity and thumbprint, Remote Desktop clients may display another certificate warning.

    You can inspect it on the server:

    1. Press Windows+R, enter certlm.msc, and select OK.
    2. Open Certificates (Local Computer) → Remote Desktop → Certificates.
    3. Open the certificate and review Issued to, Issued by, and Valid from.

    A self-signed certificate normally identifies the same server as both issuer and subject.

    Connecting by IP address

    Even while the connection is encrypted, using the server’s IP address may prevent the client from matching the address entered with a certificate issued for the server’s host name. Prefer connecting with the server’s fully qualified domain name, such as server01.contoso.com, where DNS is available.

    The default self-signed certificate also is not inherently trusted by client computers. If you manually imported the current self-signed certificate into a client’s Trusted Root Certification Authorities store, you must import the newly generated certificate again after replacement. ^1^

    When manual certificate management is required

    Manual renewal is required if the RDP listener has been configured to use a certificate issued by an internal or public certification authority instead of the Windows-generated certificate. In that case, the administrator must:

    1. Renew or obtain the replacement server-authentication certificate.
    2. Import it into Certificates (Local Computer) → Personal → Certificates.
    3. Grant NETWORK SERVICE read access to its private key.
    4. Bind its thumbprint to the RDP listener through WMI or the documented registry configuration. ^2^

    A CA-issued certificate matching the server’s DNS name is the preferable configuration when RDP is used regularly across a managed environment, because clients that trust the issuing CA can validate the server without accepting a new self-signed certificate each time it changes.

    If the default certificate expires but Windows does not recreate it, that is a fault rather than the expected lifecycle. Microsoft’s troubleshooting guidance checks the Remote Desktop certificate-store registry setting, certificate-related services, and MachineKeys permissions before restarting Remote Desktop Services and confirming that a new certificate appears. ^3^


    References

    1. Remote desktop connection is sometimes stuck on the Securing remote connection screen
    2. Remote Desktop listener certificate configurations (windows-server-2012)
    3. "An internal error has occurred" when connecting to a remote machine
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Harry Phan 36,850 Reputation points Independent Advisor
    2026-11-19T23:05:03.0933333+00:00

    Hello Scott,

    By default, Windows Server can automatically generate a self-signed certificate for Remote Desktop Services (RDS) when one is not explicitly configured. However, you should not assume that the certificate will always be renewed automatically when it expires.

    You can check the currently assigned certificate through Server Manager > Remote Desktop Services > Deployment Properties > Certificates, or inspect it using PowerShell and the certificate store.

    For a production environment, I recommend using a certificate issued by your organization's internal CA or a trusted public CA rather than relying on self-signed certificates. This provides better certificate trust and avoids recurring certificate warnings when connecting through Remote Desktop.

    If you continue using a self-signed certificate, monitor its expiration date and verify whether a replacement is generated and assigned when needed.

    Best regards,

    Harry P.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.