Normally after running Windows updates there are a few servers in our infrastructure that our monitoring software (SolarWinds) shows as having problems. Normally this is flagged as being the netman service not having started. to rectify I normally log in to the server and restart the Netman service (and if that hasnt shifted the error the winmgmt and snmp services as well). I absolutely know there must be a bertter way to do this.
I have looked at powershell but running the following yields no change in the service:
Get-Service -ComputerName XFILES -Name netman | Restart-Service -Verbose
Even if I add "-Force" to the command all I get is the repsonse of it performing the restart but the service never actually restarts.
I have also looked at psservice but this seems to struggle again with dependancies though it works very well for lone wolf services. Am I destined to have to write full on script that will enumerate dependent services or am I missing a super simple way of achieving this?