ACCESS ADMINISTRATION

Enable Remote Desktop.

Silent, multi-layer orchestration of Remote Desktop Protocol dependencies. Instantly restore administrative access to a remote endpoint without walking the user through the Control Panel.

SEE HOW IT WORKS
WinRM Dispatcher ● CONNECTED

[UHDC] ENABLE REMOTE DESKTOP

[i] Connecting to LAPTOP-US-4829 via WinRM...

> [1/3] Enabling RDP in Registry...

> [2/3] Opening Windows Firewall for RDP (Port 3389)...

> [3/3] Ensuring TermService is running...

[UHDC SUCCESS] RDP Enabled, Firewall Opened, and Service Started!

[i] You can try connecting using MSRA or RDP now.

Architectural Overview

This module is a multi-layered configuration engine designed to instantly restore administrative access to a remote endpoint. It utilizes WinRM to systematically reconfigure the three core dependencies required for Remote Desktop Protocol (RDP) connections.

Registry Modification

Establishes a remote PowerShell session over Port 5985 (HTTP). It uses Set-ItemProperty to target the Terminal Server path, flipping the fDenyTSConnections DWORD from 1 to 0.

Firewall Configuration

Re-uses the session to execute Enable-NetFirewallRule, targeting the native Remote Desktop display group to punch a hole in the local Windows Defender Firewall for TCP/UDP Port 3389.

Service Initialization

Executes Set-Service to ensure the TermService is set to Automatic startup, followed by Start-Service to immediately bind the listening port.

INTERACTIVE TRAINING ENGINE
⭐ 150 XP

How Junior Techs Learn This Tool:

Enabling RDP manually requires modifying three separate security layers: the Registry, the Firewall, and the Terminal Service. Typing all of that out in a console is a nightmare. The training engine uses this opportunity to teach the Golden Rule of IT: Don't memorize long commands. Build a script library. It teaches them how to use PsExec to remotely invoke a pre-written script directly from a network share.

psexec \\$Target -s powershell.exe -ExecutionPolicy Bypass -WindowStyle Hidden -File "\\server\IT_Share\Scripts\EnableRDP.ps1"

The In-Person Equivalent

Opening System Properties to allow remote connections, opening Windows Defender Firewall to allow the app through, and opening services.msc to start the Remote Desktop Services service.

Technical Q&A

Q: Why do we need to do all three steps? Isn't changing the registry enough?
No. Windows security is compartmentalized. Changing the registry tells the OS it is allowed to accept connections, but if the Windows Firewall is actively blocking Port 3389, the connection will still drop. Furthermore, if the underlying Terminal Service is stopped, there is no process listening on that port anyway. This workflow provides a holistic fix to ensure all three dependencies are met.
Q: Does this bypass Network Level Authentication (NLA)?
No. This module only enables the listening port and the service. It does not modify the UserAuthentication registry key. If your domain enforces Network Level Authentication for RDP connections via Group Policy, that security standard remains perfectly intact.
Q: Will executing this workflow kick the user off their computer?
No. Enabling the feature happens silently in the background. However, if you subsequently use a standard RDP client (mstsc.exe) to connect to a Windows 10/11 workstation, it will prompt the user to allow you to take over their session, locking their screen. For live support where you want to share the screen with the user, you should use Microsoft Remote Assistance (MSRA) or SCCM Remote Control after enabling this feature.