If you want, you can set a limit (timeout) on the duration of RDP sessions using GPO.

Now you can remotely connect to this computer using an RDP client. Windows has a built-in RDP client – mstsc.exe. It keeps the history of RDP connections and supports copying files between local and remote computers via the RDP clipboard.

You can also use RDP connection managers, like RDCMan or mRemoteNG, as well as alternative clients.

To make it easier for the users, you can save your RDP connection password in Windows Credential Manager.

Enabling RDP on Windows Using PowerShell

You can quickly enable RDP access on Windows using a couple of PowerShell commands.

1. Run PowerShell.exe as administrator;
2. Enable RDP access through the registry using the Set-ItemProperty cmdlet: Set-ItemProperty -Path 'HKLM:\System\CurrentControlSet\Control\Terminal Server' -name "fDenyTSConnections" -value 0
   In order to disable RDP, change the fDenyTSConnections value to 1.
3. Allow RDP connections to the computer in Windows Defender Firewall. To do it, enable the following firewall rule: Enable-NetFirewallRule -DisplayGroup "Remote Desktop"
4. If you want to add a user to the local RDP access group, run this command: Add-LocalGroupMember -Group "Remote Desktop Users" -Member a.williams

To make sure that the RDP port is open on the computer, use the Test-NetConnection cmdlet:

Test-NetConnection -ComputerName wksde133 -CommonTCPPort RDP

Enable Remote Desktop Connections on Windows Server 2022/2019

Unlike desktop Windows 10 (11) versions, Windows Server supports two concurrent RDP connections by default. These connections are used by administrators to manage the server.

RDP is enabled on Windows Server in the same way: using the SystemPropertiesRemote, Server Manager, or PowerShell commands described above.

You can use Windows Server as a terminal server. In this case, multiple users can simultaneously connect to their own desktops on the server. To do it, install and configure the Remote Desktop Session Host (RDSH) role on the server. To use it, you must purchase and activate special RDS licenses (CALs). Learn more about RDS licensing.

Also, you can use SSL/TLS certificates to secure your RDP connections.

How to Enable RDP via Group Policy (GPO) in an Active Directory Domain?

If you need to enable Remote Desktop on multiple computers at once, you can use Group Policy (GPO). We assume that all computers are joined to an Active Directory domain.

1. Run the Group Policy Management console (gpmc.msc);
2. Create a new Group Policy Object (or edit an existing one) and link it to a target OU containing computers or servers;
3. Switch to the policy edit mode and go to the GPO section Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Connections;
4. Find and enable the Allow Users to connect remotely by using Remote Desktop Services parameter;
5. Update GPO settings on the clients;
6. After applying the policy, you will be able to connect to all computers via RDP (the policy will be applied both to desktop clients running Windows 10/11 and Windows Server). If needed, you can target the RDP policy to specific computers using the WMI GPO filters;
7. If Windows Defender Firewall is enabled on computers, you need to allow RDP traffic for the domain profile in the same GPO. To do it, activate the Windows Firewall: Allow inbound Remote Desktop Exceptions rule (located in Computer Configuration -> Administrative Templates -> Network -> Network Connections -> Windows Firewall -> Domain Profile).

Enabling Remote Desktop (RDP) Remotely on Windows

Also, you can enable RDP remotely on any computer running Windows. To do it, you must have remote access to the computer (via PowerShell or WMI) and your account must be a member of the local Administrators group on the remote computer.

You can enable RDP remotely via the registry. To do it, the Remote Registry service must be enabled on the remote computer (it is disabled by default). To run the service:

1. Open the service management console (services.msc);
2. Select Connect to another computer and specify the name of the remote computer;
3. Find the Remote Registry service in the list, change the startup type to Manual, and start the service.

The same can be done remotely from the command prompt using the built-in sc tool (it allows to create, manage, and remove Windows services):

sc \\wksde133 config RemoteRegistry start= demand
sc \\wksde133 start RemoteRegistry

Then on the local computer:

1. Run the Registry Editor (regedit.exe);
2. Select Connect Network Registry in the File menu;
3. Specify the name or IP address of the remote computer you want to enable RDP on;
4. Go to the reg key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server;
5. Find the fDenyTSConnections parameter (REG_DWORD). If you cannot find it, create it. Change its value to 0 to enable RDP.

Then the remote computer becomes accessible over RDP immediately without a restart.

But it is much faster to enable RDP in the registry of the remote computer via the command prompt:

REG ADD "\\wksde133\HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server" /v fDenyTSConnections /t REG_DWORD /d 0 /f

If PowerShell remoting is configured on a remote computer, you can run a remote command on it via Invoke-Command:

Invoke-Command -Computername wksde133 -ScriptBlock {Set-ItemProperty -Path "HKLM:\System\CurrentControlSet\Control\Terminal Server" -Name "fDenyTSConnections" –Value 0}

Also, you can connect to a remote computer and enable RDP via WMI:

$computername = “wksde133”
(Get-WmiObject -Class Win32_TerminalServiceSetting -Namespace root\CIMV2\TerminalServices -Computer $computername -Authentication 6).SetAllowTSConnections(1,1)