A user asked if there was a graceful way to cycle monitor services with PowerShell. It was suggested to use a combination of stop and start the service with a 30 second delay to allow for memory to clear up, instead of a regular service restart.
Read the entire ‘Cycling Monitor Services with PowerShell’ thread below:
Is there a graceful way to cycle our monitor services with powershell? I am under the impression that performing the point and click Stop\Start of the monitor service out of the console is doing a bit more behind the scenes compared to just restarting the monitor service directly from Windows.
stop service, wait 30 seconds until the process is completely gone and start it. A service restart is too fast since it consumes a lot of memory and isn’t fast enough cleaning that out.
Perfect, thank you!
Continue reading and comment on the thread ‘How to Gracefully Cycle ControlUp Monitor Services with PowerShell’. Not a member? Join Here!
Categories: All Archives