Enable Remote Desktop PowerShell: Turning On RDP Without the GUI

Enabling Remote Desktop on Windows Server Core via PowerShell

Server Core has no GUI, so there’s no Control Panel toggle to click for Remote Desktop — PowerShell is the way to configure it. Once you’re at the command prompt on a fresh Server Core install, type powershell and press Enter to drop into a PowerShell session. Then run these two commands in order:

Set-ItemProperty -Path 'HKLM:\System\CurrentControlSet\Control\Terminal Server' -Name "fDenyTSConnections" -Value 0

Enable-NetFirewallRule -DisplayGroup "Remote Desktop"

The first enables Remote Desktop connections at the OS level; the second opens the Windows Firewall rules needed for RDP traffic to actually reach the machine. Both take effect immediately without a reboot. If you’d rather require Network Level Authentication for the connection (recommended, especially for anything not on a fully trusted internal network), also set:

Set-ItemProperty -Path 'HKLM:\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' -Name "UserAuthentication" -Value 1

You should then be able to connect to the Server Core box from any standard Remote Desktop Connection client.

A Safer Way to Expose This (Updated for 2026)

Enabling RDP directly is fine for a lab or a machine already sitting behind a properly firewalled internal network, but it’s worth thinking twice before opening port 3389 straight to the internet — that combination is a well-known scanning/brute-force target. If the Server Core box needs to be reachable from outside a trusted network, put an RD Gateway or VPN in front of it rather than exposing RDP directly, and keep NLA enabled regardless. It’s also worth knowing that Windows Admin Center can manage a Server Core machine’s day-to-day settings entirely over the network without RDP at all, which is worth considering if RDP access is only needed occasionally rather than as a standing connection method.

Resources

• Remote Desktop