Skip to content

Knowledgebase

Securing RDP access to a self-managed Windows Server

servers

Limit Remote Desktop access to authorised administrators and a controlled network path. This guide is for a self-managed Windows Server where you have permission to change Windows and the surrounding firewall.

01 Prepare a recovery route

Confirm that the provider console or another approved management route works before changing RDP settings. Keep the current session open until a second connection succeeds. Record the server hostname, actual management port and the source addresses that need access.

02 Configure remote access

  1. Review the accounts permitted to sign in. Use named accounts with strong, unique credentials and remove obsolete access. Grant administrative rights only where the work needs them.
  2. On a Desktop Experience installation, open the Remote Desktop settings and enable the service for the intended users. On Server Core, run SConfig, choose 7 for Remote desktop, and enable the option requiring Network Level Authentication.
  3. Keep Network Level Authentication enabled. It requires authentication before the desktop session is established; it does not replace the network access policy.
  4. Prefer an approved private management path, such as a VPN or managed gateway, when available. Apply its own authentication and access requirements.
  5. Open wf.msc and inspect the relevant Remote Desktop inbound rules. Restrict their remote-address scope to the approved management sources and apply the correct network profiles.
  6. Review the provider or perimeter firewall separately. Its allowed sources and destination port must agree with the Windows configuration.
  7. From an approved source, establish a fresh session with the intended user. Also confirm that a source outside the permitted scope cannot reach the management service.

03 Keep access maintainable

Document how authorised staff update the allowlist when their management address changes. Check certificates and connection warnings through a trusted channel rather than accepting an unexpected server identity automatically. Apply Windows and client updates through the normal maintenance process.

Common questions

Does changing the RDP port make unrestricted public access safe?

A different port changes where the listener is reached. It does not provide the protection of restricted sources, appropriate authentication and maintained software.

What if a new restriction blocks my connection?

Use the verified console or remaining authorised session to correct the specific rule. Confirm the actual source address and active network profile before broadening access.

Was this answer helpful?

Need a little more help?

Our support team can help you find the next step.

Contact support