Virtual Machine Guest + Host Update and Reboot Sequence Automation

[odv]

Hello,

I have a question regarding the Hyper-V host and clients patching sequence.

The question is that, is this sequence is smart enough to identify that clients have been fully updated (even after restart), in order to start host patching after?

I mean, the client updates and restarts (as usually in Windows up to 30% complete) and then up and running again. Does the BatchPatch just checks if client is finished according to ping or it has other smart option to identify that updates are 100% installed on client and only after that the host can start update? Or it is better to create a queue with delay?

Thank you.

[doug]

You can create your own queue/sequence to accomplish what you want. There is a job queue item “Terminate queue if previous ‘Check for available updates’ finds 0 updates.” This queue item would allow you to check one host to make sure it has 0 available updates before its queue ends and the next host in the sequence starts.

-Doug

[Author]

Posts