I have a cluster I patched with a consiatent build #. I added a new host and patched the critical & non-critical patches, then is was at a higher 6.7 build #.
How can I build a baseline and go back to the older build number I had before? I'm having a little trouble figuring this out in Update Manager.
you can create a baseline with the option to manually select patches. but the you have to choose which patches you want to include. a good overview you can find here: https://esxi-patches.v-front.de/vm-6.7.0.html
for a rollback of patches see here: VMware Knowledge Base
Thanks for the suggestion. I will check this out when I get back to work.
It would be cool if there was an online repository where you could just download the patches for each build #, and then import them into Update Manager and have it as a baseline to choose from / Add to your clusters.
What if someone started a GIT repository of this, would this violate any kind of terms or anything, or would it be shut down? It would sure be nice if for example I added hosts to a cluster because I needed more resources and instead of patching the entire cluster to the latest build, I could quickly grab the baseline for Critical & Non-Critical Patches, and patch that host to match the other hosts build numbers. Always have to be careful that when upgradeing it doesn't break a third party tool/software that isn't compatible, same with VMware Tools.
Or is there a way that Host Profiles would automatically do this? <-- Not an expert on Host Profiles.
We have hundreds of ESXi hosts, and want to keep them all at the same build and keep everything uniform. So I'm just thinking of good ways to make options available to achieve that.
If anyone knows of any pre-existing repositories for Critical and Non-Critical Patches that have been exported based on Build # please let me know. That would help me out considerably.
I have a huge upgrade project for a customer the week after next going from 6.5 to 6.7, and I have no idea what build # they are going to request. I sent a lot of information their way, with links to VMware's build numbers for patching and so forth.
Additionally, I would like to have a repository kept so we can maintain the same build across our infrastructure as well. Then I could just tell the customer they can't go any higher than X build number. I imagine other people have baselines for each build # kept as a choice to attach to a cluster for remediation.