"Update + reboot cycle": having the job step displayed in a column?

[booster]

Hi

Is there anyway to display in a column the step level when using the windows update>”Update + reboot cycle” ?

I setup the job to “download and install updates+reboot always” as step 1, then same thing but with “reboot if required” multiple times. Having the steps displayed can confirms me all processes are done (I’m doing on several servers during the process)

Please be aware I faced a problem when using “wait for the host to go offline and come back online”. This step is inserted between each download and install+reboot, but if the host reboots after the patches installations as part of the patch process itself, BP try the second installation attempt and failed (server is rebooting). I added a “wait 10” after the first “wait for the host to go offline and come back online” steps to avoid it.

Regards

Booster

[doug]

booster –

The actions are all printed in the ‘All Messages’ column as they are executed, so that you can tell what is happening. Is this not sufficient? What more is it that you are looking to see? Please be as detailed as possible in your description. The only way that we can update/improve the app based on your feedback is if you are very clear about what you would like to see that is not currently available/visible in the app.

When you say that you had problems with ‘Wait for host to go offline and come back online’ I’m not sure I understand. You’re saying that if the host reboots as part of the patch process itself, then BP tries the next job step while the host is offline. Under what circumstances does the host reboot without BP being responsible for initiating the reboot? I am not aware of such a thing to exist with Windows Update. When using BP, the row in BatchPatch should either say “Reboot Required” or “No reboot required,” but it sounds like you’re saying that you’re facing a situation where it is reporting “No reboot required” but it’s rebooting on its own without BP initiating the reboot? I have never experienced this behavior. Am I understanding correctly?

Thanks,

Doug

[booster]

Hi Doug

I agree all is displayed in “all messages” but when, as me, you’re applying 3 cycles of update+reboot on 50 servers or more at a time, having the job steps displayed will ease the troubleshooting if necessary. My request was to display dynamically the number of steps in the job and the actual one. this way is something is stucked it’s really easy to focus on.

Example for a job: 1

1/ dL,install, reboot always

2/ wait offline/online

3/ wait 10

4/ dl,install, reboot if required

5/ wait offline/online

6/ wait 5

===> 6 steps, a column dynamically showing 1/6 then 2/6 etc. can confirm all job steps are done for all servers in the grid, and sort on it if stucked helps to troubleshoot servers with erros. I hope it makes my request more easier to understand

Not exactly. I tested this behaviour on a VM multiple time with always the same issue If we take the cycle:

1/ dL,install, reboot always

2/ wait offline/online

3/ dl,install, reboot if required

4/ wait offline/online

The problem appears after the step 2: I monitored the VM console, steps 1 and 2 were successful but after the 1st reboot the VM shows an update screen with a % displayed, applying a post reboot patch part. When 100% is achieved the VM reboot again, but the step 3 already started, creating the error. Adding a wait after point 2 solved the problem. Maybe add a check for pending install/reboot as part of the ‘Wait for host to go offline and come back online’ is the way to go.

I was able to reproduce the problem each time I tried with the same test VM’s. If you need logs/screen or else, I maybe be able to provide it if I still have test VM’s in a prior patches state. (to check).

Regards

Olivier

[doug]

Olivier – Thank you for the detailed explanation. Everything you said makes sense. The idea to show the job steps is very good, and we will plan to add it in a future build.

With regard to the VM reboot issue, I now understand what you are describing, but at the moment I’m not sure what we can do about this. For the time being, your solution of adding a 10 minute wait period is good. Your suggestion to maybe add a check for pending install/reboot makes sense, and we’ll look into it, but the problem is that there isn’t really a formal way to ask Windows if it is in the middle of doing a post reboot patch and if it’s about to reboot itself. In any case, we will look into this issue more to see if we can figure out a good way to address it. However, for now you should stick with your 10 minute wait step.

Thanks again,

Doug

[booster]

Hi Doug,

Thank you for the feedback and effort put in the customer requests

Regards

Booster

[martbasi]

+1 for the step-number display request, that would be helpful info.

Also I have the same scenario with the VM reboot issue. Same solution for me, just added some wait time. Just thought i’d chime in so doug knows booster isn’t alone in this.

[booster]

Hi martbasi,

Thx for sharing it 😉

PS: doug if you can correct the title’s mistake (having”t”). I don’t see how to correct it myself, shame on me

Regards

Booster

[doug]

I corrected the title. 🙂

[booster]

thx doug 😉

[Author]

Posts