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:
- Press Windows+R, enter
certlm.msc, and select OK. - Open Certificates (Local Computer) → Remote Desktop → Certificates.
- 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:
- Renew or obtain the replacement server-authentication certificate.
- Import it into Certificates (Local Computer) → Personal → Certificates.
- Grant NETWORK SERVICE read access to its private key.
- 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