This is probably a stupid question, but I’m going to ask anyway.
With the “from source” XO, when you do a rolling pool update, can you close the browser and just let it go through and do its thing?
I’m guessing yes, but thought it was worth asking.
As far as I know none of the actions that start jobs once executed are dependent on the browser staying open.
I’ll have to try and close it next time there is an update. This last update went through all three servers fast.
Closed the browser windows after starting the pool update, everything seemed to work fine. It’s also a small pool with only 2 VM’s right now, and one of them is off (should be deleted). Haven’t had time to experiment lately so things are still pretty sparse.