Windows 2022 has RemoteRegistry set to AutoStart -trigger-start.
Therefore after 10 minutes, the service stops and waits for the next trigger to start it.
The issue is SAM is checking for the RemoteRegistry service to be running and on the check to the remote servers, the service says it's down (which it is)
But you can easily start it and it will run. Unfortunately SAM just checks and reports its down and there fore the Counters are reported as down/unreachable as. well.
I can try to set the service to run always (Proving to be more difficult that initially thought)
Or maybe have SAM Start the service and then check, but not sure how that will work when the counters try to use the remote registry service.
I see other people have had this issue, but i have not seen a method to correct it.
There also seems to be a memory leak in RemoteRegistry service a few years back, but that seems to be fixed.
any thoughts?
Kevin
