Hi Chris,
We're facing the same situation, and so far, we haven’t found a way to automate the update process for VEM and VBR.
At the moment, we use VSPC to download the ISO to all tenant servers as a pre-step. After that, we perform the updates manually.
If anyone has found a better approach, I’d be very happy to try it out—especially with the new update that just came out.
Yeah I am running the VEM upgrade manually on my homelab server and then will test the VBR upgrade from VSPC. I want to have this automated even somewhat for my team to do the upgrades.
Hopefully someone though has found some janky workaround. 🤣
@Chris.Childerhose Not tested with VEM patching yet but we used to patch tenant VBR servers from VSPC console and it works well all the time. You can select multiple VBR servers and patch them all at once.
@Chris.Childerhose Not tested with VEM patching yet but we used to patch tenant VBR servers from VSPC console and it works well all the time. You can select multiple VBR servers and patch them all at once.
Thanks for the input. Yeah my goal is to patch most of them in one go once we have our change process ticket submitted.
Hey, Nice topic I was looking for the same. It could be interresting to have an indication when a VBR is linked to a VEM in the VSPC.
Hey, Nice topic I was looking for the same. It could be interresting to have an indication when a VBR is linked to a VEM in the VSPC.
There is an indication when trying to update and also you can filter by VEM servers as well to see. 😉
Found that the silent installation with XML file works well to get VEM installed then use VSPC for VBR.