Remote Registry Service

• Make sure that appropriate network connectivity is open towards the scanned server, as per the info at the start of this document (TCP ports 135, 445 are required for remote registry access).
• Make sure that the remote registry service is enabled/running. On specific Windows Server editions, you may also need to make the following registry change, to prevent the remote registry service going into idle mode, and not activating as required (this is a known issue on MS Windows side).

Prevent remote registry service from being stopped (in case the service is going into Idle mode)

1. Open Regedit (Run as Administrator).
2. Navigate to the following registry key:
3. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\RemoteRegistry
4. Add/Change a DWORD value: DisableIdleStop, and set it to 1.
5. Restart the Remote registry service.

• Check if the server and workstation services are enabled/running on the scanned server.
• Ensure that File and Printer Sharing and Client for Microsoft Networks are enabled on the network adapter of the scanned server, as well as on the OC Scanner server.
• Check that NetBIOS is enabled on both the OC Scanner server and the scanned machine.
• Make sure the user account running the scan, has the right to access remote registry service on the scanned Windows server, as follows:
  • Open Regedit (Run as Administrator).
  • Navigate to the registry key:
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg
  • Right-click the registry key > Permissions, and see which user accounts/groups have access to the remote registry service on the given server, and add the ‘Read’ permissions, as required.