Having said that, the process today is still pretty manual since you need to manually retrieve the build numbers for either a VC, ESXi or vSAN Host (can be automated using vSphere APIs) and then comparing that to the KBs to get the correct versions. These are definitely a great set of resources that I know many customers including myself have been using since its release. Build numbers and versions of VMware vSAN (2150753).Build numbers and versions of VMware vCenter Server (2143838).Build numbers and versions of VMware ESXi/ESX (2143832).Recently, VMware had released a series of VMware KBs which provides a mapping between the build numbers for vCenter Server, ESXi and vSAN to their respective versions which can be found in the links below: Historically, most customers including myself would retrieve the respective build numbers and then manually comparing them to either the release notes and/or download website which was very tedious.Īlthough VMware has exposed the version number within our vSphere products since day 1 which can also be retrieved programmatically using the vSphere API ( here), it unfortunately does not provide more details than simply the major/minor version (e.g. This especially gets challenging when there are multiple patch releases (a, b, c or 01, 02, 03) in between major releases (5.5, 6.0, 6.0u1, 6.0u2, 6.5, etc.). I can still remember when I was a VI Admin and how annoying it was to try to correlate the build numbers for my ESX(i) hosts and vCenter Servers that I have deployed with the versions listed on VMware's website.
0 kommentar(er)
