VMware vSphere 6.5 has been released as general available and earlier this week I posted about Installing VMware vCenter Server Appliance 6.5 as a new install, this post will walk through upgrading an existing vCenter Server Appliance 6.0 to 6.5!
Similar to a fresh VCSA 6.5 install, the VCSA 6.5 upgrade is also broken up into two stages. The first stage is deploying a new vCenter Server Appliance and the second stage is copying data from the 6.0 VCSA to the newly deployed 6.5 VCSA.
VMware has announced that VMware vSphere 6.5 has gone general available this week. Now installing VMware vCenter Server Appliance 6.5 (VCSA) is even easier as the requirement for the client integration plugin has been removed and now the VCSA appliance is delivered via an ISO image with an installation wizard that’s been broken up into two stages.
The VCSA 6.5 ISO offers two types of installation methods, CLI and GUI install – both availalbe for Windows, Mac and Linux machines. In this guide I’ll walk through the steps of installing VCSA 6.5 using the Windows GUI install.
VMware announced VMware Workstation 12.5 and Fusion 8.5 during VMworld 2016 in Las Vegas. Well VMware Workstation 12.5 and Fusion 8.5 is now available for download!
Both Workstation 12.5 and Fusion 8.5 include a large number of fixes, security and performance improvements, but most noticibly both have added support for Windows 10 Anniversary Update as well as Server 2016 operating systems.
I was recently upgrading a VMware environment from vCenter Server Update 3b to Update 3e and during the scheduled change I had also planned on upgrading VMware Update Manager to Update 3e and ran into the following error:
VMware Workstation unrecoverable error: (vthread-3)
GetProcAddress: Failed to resolve ENGINE)load_aesni: 127
You can request support.
Looking for a possible solution at the VMware Knowledge Base came back with no results and to error message wasn’t overly useful either with “VMware Workstation unrecoverable error: (vthread-3)” as Workstation wasn’t installed on this server.
Microsoft recently pushed out a “Convenience Update“, a sort of rollup of rollups for Windows Server 2008 R2 SP1 and Windows 7 machines. This “Convenience Update” however comes with an incompatibility issue with VMware virtual machines that are using VMXNet3 network adapters, which causes the network to become unresponsive.