Redgate Monitor Does Not Start After Windows Patching And Restart

TUellnerTUellner Posts: 59 Bronze 5
in Redgate Monitor
Whenever our servers have Windows Updates applied and restarted, Redgate Monitor services fail to start. I've changed the services from "Automatic" to "Automatic (delayed start)" but whenever this happens and I check the services, they have been reset to "Automatic".

I have usually had an update to Redgate Monitor that I've applied since the last Windows Update patching. So I don't know if the Redgate Monitor updater resets the services to "Automatic" or that is something that might happen from the security software on our network that might possibly reset changes in service settings.

Does the Redgate Monitor updater change this setting?

-Tom
Tagged:
· Share on Twitter

Best Answers

Answers

  • Alex BAlex B Posts: 1,157 Diamond 4
    Exactly what @ThomasBE said, when you install RGM, it is effectively a re-install of the product, so it will change the startup from Automatic (Delayed) to Automatic.
    Product Support Engineer | Redgate Software

    Have you visited our Help Center?
    · Share on Twitter
  • TUellnerTUellner Posts: 59 Bronze 5
    Thanks Thomas and thanks for the confirmation Alex. This is disappointing that it does not check that the service is already present and wipes out the settings.This means every time I update RGM I will need to go into services and change it back to "Automatic (delayed start). Every time Windows patches are applied to the server and it's rebooted, RGM fails to start if it's not set to delayed start.
    · Share on Twitter
  • ThomasBEThomasBE Posts: 24 Bronze 3
    TUellner said:
    Thanks Thomas and thanks for the confirmation Alex. This is disappointing that it does not check that the service is already present and wipes out the settings.This means every time I update RGM I will need to go into services and change it back to "Automatic (delayed start). Every time Windows patches are applied to the server and it's rebooted, RGM fails to start if it's not set to delayed start.
    Why not create a one-line powershell script and schedule it on reboot (or daily for that matter) that checks and sets the service to delayed start if needed?
    · Share on Twitter
  • TUellnerTUellner Posts: 59 Bronze 5
    ThomasBE said:
    TUellner said:
    Thanks Thomas and thanks for the confirmation Alex. This is disappointing that it does not check that the service is already present and wipes out the settings.This means every time I update RGM I will need to go into services and change it back to "Automatic (delayed start). Every time Windows patches are applied to the server and it's rebooted, RGM fails to start if it's not set to delayed start.
    Why not create a one-line powershell script and schedule it on reboot (or daily for that matter) that checks and sets the service to delayed start if needed?

    That's exactly what I just finished doing but I really do wish the setup would check and if the service already existed and was Automatic or Automatic (Delayed Start) it would leave it alone.
    · Share on Twitter
Sign In or Register to comment.