Editing files on an ESX host using vi or nano.This option can be very time consuming if you have a lot of VMs that need to be reverted back to an older version and prone to mistakes since you have to match up the correct settings for each VM such as vCPU count, memory, number of disks, reservations, etc.Īt the bottom of that same KB article, in the "Related Information" section, you'll find that two other links: Create a new virtual machine with the required hardware version and attach the existing disk from the virtual machine.The other thing is that you need to set up a job for each VM that you need to revert back.
Where is the virtural hardware tab in vmware 6.0 install#
User VMware vCenter Converter Standalone. You'll need to install this tool, but there are limitations since you can only change the VM version to 7, 8, 9, 10, or 11.This is the easiest option but assumes you've taken a snapshot in the first place. You do have a few options to rollback and you find VMware KB 1028019, but none of them will work for you. Don't worry, I'll show you a quick way to revert and also point out the way VMware recommends you do it.Īs you try to figure out why it's not working, you quickly go through the logs, and you determine that the VM hardware version that you're running on-prem is not compatible with your DR solution since they are not running the latest version of vSphere within their datacenter. In this example, let's say it's your disaster recovery (DR) solution that's not compatible. However, after everything has been done, you find that one of your 3rd party solutions no longer works and you find yourself staring at a list of errors. Everything has gone according to plan with no issues during the scheduled maintenance. You've upgraded to the latest version of vCenter Server, ESXi, VMware Tools, and either scheduled the VM Hardware upgrade on the next reboot or you've manually upgraded the hardware version for each machine.