1. Choose Download Windows setup next to your host. Your personal file is named SecureRDP-Setup-hostUUID.cmd, with your host’s unique ID in place of hostUUID. Keep it private and use it within 30 minutes.
2. Copy the file to that Windows computer, double-click it and accept the administrator permission (UAC) prompt. Administrator permission is required. Windows uses Windows PowerShell 5.1 for setup.
3. The setup window shows checks, then asks for a separate confirmation that you have independent physical, provider or hypervisor console access: type YES only if it works. Next, type Yes to consent to the listed changes. The two answers are case-sensitive. An existing RDP session is not independent console access. If you do not have it, stop.
4. Windows detects the RDP listener port and checks it against the saved port. If the port differs or firewall policy is unsafe, setup stops with an explanation. Ask your administrator to resolve it; do not guess. RDP must already be enabled.
5. After enrollment, Windows waits for an IP. Open this website on the computer you will connect FROM, select this host and click Allow current IP. Use the browser IP that matches your RDP connection, not the website server’s outbound IP. Only one IP is allowed per host.
6. A 10-minute rollback is armed before firewall changes. When the host row asks you to test, open a new RDP connection and sign in with your usual Windows account. Before the deadline, click I connected successfully in that host row from the same approved computer, with its IP still allowed. An existing session or this website is not a test. Keep the setup window open until it reports local confirmation; the website acknowledgement alone does not disarm rollback.

If Windows security or execution policy blocks setup, stop and ask your administrator about approved, reviewed or signed scripts. Do not bypass protections. This is guided setup, not a promise of safe single-click installation.

If you cannot connect or the deadline passes, check the Windows setup window from the console. Rollback is expected to restore previous permissions, which may allow broader access, but depends on Task Scheduler and successful Windows operations. The website cannot guarantee restoration.

The personal file contains a one-use setup code for exactly one host ID, not a long-term agent credential. A new download replaces older unused codes. An installed agent continues to work until the replacement uses its code and clears the allowed IP. Never share the file or record setup with logging/transcription; delete it after use.

The name, address and port are saved for reference only. This website does not connect to the host, install software remotely or verify the listener.

This website uses HTTP. Downloads are available for local testing, but Windows setup requires HTTPS. Use HTTPS before installing on Windows.