The Remote Desktop Protocol (RDP) client on Windows stores every connection as a plain-text .rdp file. Each file holds the full session definition: server address and port, user name, display resolution, audio and drive redirection, gateway settings, and optionally saved credentials. For anyone managing more than one Windows VPS instance, a small library of reusable .rdp profiles turns a repetitive login routine into a double-click operation.<\/p>\n\n\n\n
This guide shows how to create, edit, and deploy .rdp files on Windows 10 and Windows 11, including the PowerShell steps that push profiles to several machines at once. If you have not picked a host yet, compare Windows VPS providers on our comparison table<\/a> first so the connection settings below match the provider’s real RDP endpoint and gateway addresses.<\/p>\n\n\n\n An .rdp file is UTF-8 text with one setting per line in A minimal working profile looks like this:<\/p>\n\n\n\n Launch One practical habit is to keep a separate baseline .rdp file per server role \u2014 IIS boxes, SQL Server, jump hosts \u2014 and to include the port in the filename when RDP runs on a non-standard port. Because the files are small and text-based, they version cleanly in Git alongside your server notes.<\/p>\n\n\n\n If the VPS sits behind a Remote Desktop Gateway \u2014 the recommended setup when you do not want to expose TCP 3389 to the internet \u2014 the profile must reference the gateway explicitly:<\/p>\n\n\n\n The redirection settings in an .rdp file decide how much of your local machine the session can touch. For administrative VPS work the safe defaults are clipboard on, drives off, and printers off:<\/p>\n\n\n\n Drive redirection is convenient for copying files, but it also gives any process on the VPS read access to the mapped volumes. On shared or lightly trusted servers, keep When several administrators manage the same fleet of Windows VPS instances, keep the .rdp files on a file share and sync them locally with a short script. The example below copies the profile set into each user’s Documents folder and logs the result:<\/p>\n\n\n\n For larger fleets, push the files with a scheduled task or a logon script applied through Group Policy, and name every profile with the server’s role and environment (for example Adding .rdp files are the most under-used productivity tool in Windows VPS administration: they standardize connection settings, remove typos from manual entry, and make server access reproducible for the whole team. Build a baseline profile, add gateway and redirection rules, version the files with your documentation, and deploy them with the PowerShell snippet above. Before you provision more servers, see the full specs and pricing<\/a> on the Windows VPS comparison table so your connection strategy matches the provider’s network design.<\/p>\n\n\n\nWhat an .rdp File Actually Contains<\/h2>\n\n\n\n
name:value<\/code> format. The most useful settings for a VPS connection are:<\/p>\n\n\n\nfull address:s:<\/code> \u2014 the hostname or IP and port, for example 203.0.113.10:3389<\/code><\/li>username:s:<\/code> \u2014 the account used to sign in<\/li>screen mode id:i:<\/code> \u2014 1<\/code> for full screen, 2<\/code> for windowed<\/li>desktopwidth:i:<\/code> and desktopheight:i:<\/code> \u2014 the session resolution<\/li>redirectclipboard:i:<\/code>, redirectdrives:i:<\/code>, redirectprinters:i:<\/code> \u2014 local resource redirection<\/li>audiomode:i:<\/code> \u2014 0<\/code> play on remote, 1<\/code> play on local, 2<\/code> do not play<\/li>gatewayhostname:s:<\/code> \u2014 the Remote Desktop Gateway used to reach the VPS<\/li>authentication level:i:<\/code> \u2014 0<\/code> always connect, 2<\/code> require Network Level Authentication<\/li><\/ul>\n\n\n\nfull address:s:203.0.113.10:3389\nusername:s:Administrator\nscreen mode id:i:1\ndesktopwidth:i:1920\ndesktopheight:i:1080\nredirectclipboard:i:1\nredirectdrives:i:0\nauthentication level:i:2\nprompt for credentials:i:1<\/code><\/pre>\n\n\n\nCreate a Baseline Profile in Remote Desktop Connection<\/h2>\n\n\n\n
mstsc.exe<\/code>, enter the VPS address in the Computer<\/strong> field, and type the user name. Before connecting, open the Display<\/strong> and Local Resources<\/strong> tabs and set the resolution and redirection options you want to keep as defaults. Then click Save As<\/strong> and give the profile a descriptive name such as web-server-01.rdp<\/code>. The client writes the file to the Documents folder, and you can open it with any text editor to inspect or tweak individual settings.<\/p>\n\n\n\nAdd Remote Desktop Gateway and Authentication Settings<\/h2>\n\n\n\n
gatewayhostname:s:rdg.example.com\ngatewayusagemethod:i:1\ngatewaycredentialssource:i:0\npromptcredentialonce:i:1\nauthentication level:i:2<\/code><\/pre>\n\n\n\ngatewayusagemethod:i:1<\/code> forces the connection through the gateway for all traffic, while gatewaycredentialssource:i:0<\/code> asks for gateway credentials separately from the session credentials. With promptcredentialonce:i:1<\/code>, the client reuses the credentials it collected for the gateway instead of prompting twice. When the gateway requires smart cards or a second factor, keep gatewaycredentialssource:i:1<\/code> (use the same credentials) and let the gateway handle the challenge.<\/p>\n\n\n\nControl Display, Audio, and Drive Redirection<\/h2>\n\n\n\n
Setting<\/th> Value<\/th> Effect<\/th><\/tr><\/thead> screen mode id:i:<\/code><\/td>1<\/td> Full-screen session<\/td><\/tr> redirectclipboard:i:<\/code><\/td>1<\/td> Share the clipboard both ways<\/td><\/tr> redirectdrives:i:<\/code><\/td>0<\/td> Do not map local disks into the session<\/td><\/tr> redirectprinters:i:<\/code><\/td>0<\/td> Do not map local printers<\/td><\/tr> audiomode:i:<\/code><\/td>2<\/td> No audio redirection<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n redirectdrives:i:0<\/code> and transfer files through a secure channel such as SMB or SFTP instead. If a specific machine genuinely needs disk mapping, create a separate profile with redirectdrives:i:1<\/code> and use it only for that machine.<\/p>\n\n\n\nDeploy Profiles to a Team with PowerShell<\/h2>\n\n\n\n
$share = \"\\files01\rdp-profiles\"\n$dest = Join-Path $env:USERPROFILE \"Documents\"\nrobocopy $share $dest *.rdp \/NJH \/NJS \/NP\nif ($LASTEXITCODE -lt 8) { Write-Host \"Profiles synced to $dest\" }<\/code><\/pre>\n\n\n\niis-prod.rdp<\/code> or sql-staging.rdp<\/code>). Because the client remembers the last-used profile per server, keeping the filenames stable also prevents confusing duplicate entries in the saved-connections list.<\/p>\n\n\n\nSecurity Considerations for Saved Credentials<\/h2>\n\n\n\n
savedcredentials:i:1<\/code> to a profile stores the password in Windows Credential Manager, encrypted with DPAPI and tied to the user account. That is convenient for a personal workstation, but do not distribute profiles that contain credentials \u2014 the encrypted blob does not travel with the file, and a shared profile with embedded credentials is a password leak waiting to happen. Keep shared profiles at savedcredentials:i:0<\/code>, enforce Network Level Authentication with authentication level:i:2<\/code>, and use an RD Gateway with MFA when the VPS holds anything sensitive. For short, high-risk sessions, mstsc.exe \/restrictedAdmin<\/code> launches a session without delegating your credentials to the remote host at all.<\/p>\n\n\n\nSummary<\/h2>\n\n\n\n