Newer versions of Windows introduced the concept of Trigger Start services.
The idea being that a specific event “triggers” the startup of a service. In the past the service would have been running, using up resources waiting for that moment when it was needed. Using this newer method means services a dormant until they are actually needed.
I had a problem with some backup software recently (Veeam). It needs the remote registry service to be running on virtual machine that needs to be backed up.
For some reason there was one particular server that refuse to backup. I was able to confirm the trigger wasn’t kicking in when attempting to remotely edit the registry. It worked on other servers and I was able to confirm it wasn’t the firewall or anything like that.
Working with service triggers is a bit of a pain normally though
You have to do it via the command line using the SC command
sc qtriggerinfo remoteregistry
The title for this post should be a massive clue as to where I’m going with this.
There is a very useful tool called Service Trigger Editor which you can download for free
It lets you work with trigger services in a nice and simple gui. You can edit existing triggers as well as add your own.
I used the tool on a server that was working ok and replicated that on the server that was having a problem. All worked fine after that.
Triggers services were introduced with Windows 7 and Windows 2008 R2.
Latest posts by Andy Parkes (see all)
- My Year In Running – 2017 - January 1, 2018
- Run For Your Life – A Magazine About Everyday Runners - December 9, 2017
- DNS Server Can’t Resolve Against Itself - December 6, 2017