manually restart windows service on remote probe

Hi JohnD

Have you tried to use that manual: https://kb.paessler.com/en/topic/40713-can-i-automatically-restart-a-windows-service-with-prtg

But pause the sensor, then when you want to start the service, you have to manually un-pause it, wait until the service is up again, then pause the sensor again.

I now, quite a hack but the only thing I can think of when it has to be integrated in PRTG.

regards Thomas

Hi Thomas,

Thanks for the suggestion.

Sorry i was not clear earlier. I want to keep monitoring the service and auto-restart when it shuts down. Along with it, i want to manually force-restart as and when required.

But i guess this can be achieved using two sensors - one with default auto-restart setting and another to pause-unpause.

This becomes messy if i want to monitor many services at a time...

Any other ideas...

Regards, John

Well, the sensor only restarts it once, every further attempts of restarting have to be done within the service setting. That's the easiest option :)

Hi Stephan,

Can you please elaborate on "every further attempts of restarting have to be done within the service setting"

I didn't get this....which service setting are you talking about??

Regards, John

I was talking about the services properties:

1. Launch services.msc
2. Right click the service
3. Click properties
4. Open the "Recovery" tab

You can set the recovery behavior of the service there very granular :)

oh ok.

The service that i want to monitor is of a third party program.

So, when the program freezes, i have to remotely restart the service. Here, the service will still be in "Running" state, so failure is not detected at the service level but at the program level.

The local services.msc recovery tab will not help here.

That's the reason i want an option to remotely restart the service even if it's in running state.

Regards,

Hm that won't work with the default sensor. You'll need a PowerShell script that checks if the service is responding and then take the appropriate action depending on the result. One approach would be to check if the service is responding:

Get-Process | Select Name,Responding | Where-Object {$_.Name -contains "<your-process-name>"}