How can we help you today? How can we help you today?

Redgate Monitor Does Not Start After Windows Patching And Restart

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
TUellner
0

Comments

6 comments

Sort by
  • ThomasBE
    I can assume it would as every update is actually a reinstall of the product.

    You can check it easily yourself by checking the setting before and after an update.
    ThomasBE
    0
  • Alex B
    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.
    Alex B
    0
  • TUellner
    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.
    TUellner
    0
  • ThomasBE
    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?
    ThomasBE
    0
  • TUellner
    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.
    TUellner
    0
  • Alex B
    I'll feed it back to the team!
    Alex B
    0

Add comment

Please sign in to leave a comment.