Skip to content

← All integrations

Windows · Identity and remote access

Puts the certificate on the RDP listener, so Remote Desktop shows a valid certificate.

The service agent on the server fetches the task from the appliance over outbound HTTPS on port 443 and installs the certificate locally on the server. The appliance never connects to the server.

What happens

  1. The service agent on the server fetches the task from the appliance over outbound HTTPS, port 443.
  2. The Windows basics first import the certificate into the Windows certificate store (LocalMachine\My).
  3. The certificate is assigned to the RDP listener. TermService is restarted only when chosen and the listener still serves another certificate after the wait. This disconnects RDP sessions. If it fails: Rollback puts the previous certificate back and checks that the RDP listener serves it over TLS.
  4. Verification: the package checks the RDP listener configuration and the certificate it actually serves over TLS.

Technical details

Connection
The package runs through the service agent on the server. The agent connects over outbound HTTPS to the appliance, port 443 by default. You open no port into the server.
Service ports
3389
You need
The service agent installed on the server.
Platform
Windows Server 2012 and later, Windows 10 and 11
Actions
Discovery, Installation, Verification, Rollback
Packages
windows-rdp 1.1.0
Note
  • Discovery finds the RDP certificate, port and Network Level Authentication setting.
  • Covers the RDP listener on the server. RD Gateway and the other RDS roles are not included.

Get started