4 Replies Latest reply on Nov 21, 2017 9:15 AM by lynettemoley

    Start patching server B only after server A has finished?


      Is there a way to do this with a Custom Action, or some other method rather than just separating their start times?

      I am pretty sure I could do a pre-deploy script for server B that checks to see if server A is up, but that's not going to work any time a patching cycle has multiple reboots.  Ideally I'd like to have a post-patch action on server A that kicks off B to start patching, or to even scan and patch.


      If not a custom action is there any other way to do it, either agent or non-agent?


      Currently on Protect 9.2.5046.