DC CORE
Use RDP without opening port 3389 to the public internet.
Keep Windows management privately reachable. Native Microsoft RDP and Central’s supported desktop capability are separate access methods, with different host and session requirements.
Choose native RDP or Central remote desktop.
For an office Windows server, keep the RDP service restricted locally and provide an authorised private route. Port 3389 may still be used by the service inside the local environment; the objective is to avoid publishing it to the public internet.
Check Microsoft’s RDP host requirements for native Remote Desktop.
Prepare and verify the connection.
- Prepare a supported host. For native RDP, verify that the Windows edition can host a session, enable the service for authorised users and retain its local firewall rules. Windows Home cannot host native RDP.
- Provide a private path. Use an approved private connection for RDP, or the supported Central desktop tool. Check compatibility and permissions before opening a session; one method does not imply support for the other.
- Verify the connection. Test from the actual remote location. Confirm the machine identity, carry out a harmless check and disconnect. Verify that public router forwarding is not part of the chosen management path.
Use Central for the setup and management tools.
Sign in to Central for the package and deployment instructions for your machine. Supported management paths use outbound agent connections, so public inbound management ports are not normally required. Your local network and target services retain their own access controls.
Central starts at £10/month for five devices, excluding VAT. See pricing and inclusions and check supported platforms.