Solutions for the management and administration of Windows Active Directory

How to use the RustDesk remote control tool in IDEAL REMOTE?

Prerequisites for optimal RustDesk management in IDEAL REMOTE

I would like to use the RustDesk remote control tool to manage client computers within my organization. What are the prerequisites for using RustDesk in IDEAL REMOTE?

To ensure optimal performance and avoid delays (notably the 20-second delays related to RPC), the following prerequisites must be met on remote computers.

Why are these prerequisites necessary?

IDEAL REMOTE operates agentless and relies on:

• WMI
• RPC
• Remote Registry
• Service Control Manager

If certain Windows components are disabled or misconfigured, significant slowdowns or connection failures may occur.

1. WMI enabled remotely

Why?

WMI is used to:

• Check the status of the RustDesk service
• Retrieve system information
• Execute certain remote actions

If WMI is blocked, remote management becomes unstable or impossible.

In a Workgroup environment

On each machine:

1. Open services.msc
2. Verify that the service:

Windows Management Instrumentation (WMI)
Service name: winmgmt

• Status: Running
• Startup type: Automatic
• Ensure the firewall allows:
• WMI
• RPC (port 135)
• Dynamic RPC ports

Quick command:

netsh advfirewall firewall set rule group="Windows Management Instrumentation (WMI)" new enable=yes

In an Active Directory environment (GPO)

Create or modify a GPO:

Path:

Computer Configuration
 \ Policies
   \ Windows Settings
     \ Security Settings
       \ System Services

Configure:

• Windows Management Instrumentation
  • Startup mode: Automatic
  • Start the service

Also configure the firewall:

Computer Configuration
 \ Policies
   \ Windows Settings
     \ Windows Defender Firewall
       \ Inbound Rules

Enable the predefined WMI rules.

2. RemoteRegistry service started (Automatic)

Why?

IDEAL REMOTE uses the Remote Registry to:

• Modify DisableRPCOverTCP
• Read / write system settings
• Apply certain RustDesk optimizations

In a Workgroup

On each machine:

1. Open services.msc
2. Service:

Remote Registry
Service name: RemoteRegistry

Configure:

• Startup type: Automatic
• Status: Running

In GPO

Path:

Computer Configuration
 \ Policies
   \ Windows Settings
     \ Security Settings
       \ System Services

Configure:

• Remote Registry
  • Startup mode: Automatic
  • Start the service

3. DisableRPCOverTCP = 1

Why?

When this value is not enabled:

Windows attempts to use RPC over TCP (port 135 + dynamic ports).

If these ports are filtered:

each service management action may experience a delay of approximately 20 seconds.

With:

DisableRPCOverTCP = 1

Windows uses Named Pipes directly, making operations nearly instantaneous.

Registry location

HKLM\SOFTWARE\Microsoft\Rpc
DWORD value:
DisableRPCOverTCP = 1

A restart is required after modification.

In a Workgroup

On each machine:

reg add HKLM\SOFTWARE\Microsoft\Rpc /v DisableRPCOverTCP /t REG_DWORD /d 1 /f

Then restart the machine.

In GPO

Create a GPO:

Computer Configuration
 \ Preferences
   \ Windows Settings
     \ Registry

Add:

• Action: Update
• Hive: HKLM
• Key: SOFTWARE\Microsoft\Rpc
• Name: DisableRPCOverTCP
• Type: REG_DWORD
• Value: 1

Then restart the computers.

Prerequisites Summary

Network Recommendation

In a professional environment:

• Deploy these settings via GPO
• Force a controlled restart
• Verify via IDEAL REMOTE that RPC delays have disappeared