This article explains the reason for Could not connect to remote registry error and how to resolve it.
When launching a scan to a remote machine from a Terminal Server, the following error is displayed:
Could not connect to remote registry
This issue will occur when scanning the machine for anything that requires remote registry access. For example, application scanning, missing patch scanning, and remote registry scanning.
- GFI LanGuard
- All supported environments
Root Cause Analysis
When a client connects to a Windows Server via Terminal Services, and the user wants to run a scan from GFI LanGuard, then the user needs enough privileges to connect remotely to other machines. If the GFI LanGuard machine is a workstation, this change is not required.
To resolve this issue, it is necessary to elevate the rights of the account that is used to connect via Terminal Services.
To do this, please follow the steps described in Agent Install or Remediation Job Status Stuck at Pending article.
Once the account/user has the necessary rights to launch scans via Terminal Services, this error will stop occurring.