Remote Registry is not started (4308090)

This can be due to the face that the Remote Registry Service is not set to automatic, but is set to Automatic (trigger start). Can also sometimes happen when set to automatic (delayed start).

This can be over come by setting the service to be automatic and started when the RUM console is working with the machine.

These Service commands are offered to assist in this process but are in no way created by Quest or recommended for use in you environment without proper investigation and testing.

Change Service to Automatic and started:
sc config remoteregistry start= auto
sc triggerinfo "remoteregistry" delete
sc start remoteregistry

Change Service to trigger start:

sc config remoteregistry start= delayed-auto
sc triggerinfo "remoteregistry" start/namedpipe/winreg
sc stop remoteregistry