This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

With RUM, Getting warning 'Remote Registry not started' error, Service is set to auto with 'trigger start'

With RUM, Getting warning 'Remote Registry not started' error, Service is set to auto with 'trigger start'

 

How can

a, Get RUM to send a 'trigger' to remote registry service on remote desktop (so it triggers / starts the remote registry service.)

b, on desktop remove the "Automatic (Trigger start)" requirement, so it just starts as a 'regular auto service.

 

NOTE, i want this solution to be GPO able please.

 

I just want RUM to 'discover' PC without the warning.

Thanks in advance

Parents
  • As this is a purchased tool that is meant to automate and made things simpler (otherwise script the lot and save $) surely there is an solution to this. Triggered services have been around for a while and RUM still doesn't trigger the trigger for the service that is needed for processing and moving the machine.

    in the meantime, in the pre field, i was thinking netstart remote registry, does it know the machine or does that have to be stipulated?

    Any recommendations on using the 'pre' field?

    Thanks

Reply
  • As this is a purchased tool that is meant to automate and made things simpler (otherwise script the lot and save $) surely there is an solution to this. Triggered services have been around for a while and RUM still doesn't trigger the trigger for the service that is needed for processing and moving the machine.

    in the meantime, in the pre field, i was thinking netstart remote registry, does it know the machine or does that have to be stipulated?

    Any recommendations on using the 'pre' field?

    Thanks

Children
No Data