#Vcenter 6.5 pulled patch update

IвЂ™m sure some of you are wondering, why not just remove the VUM Baseline I created for the Dell iSM and OMSA VIBs and re-scan? So diving through the VUM logs on the Windows guest the agent was installed on at:

#Vcenter 6.5 pulled patch update

Made sure VUM was using the latest patches with a вЂњDownload NowвЂќ and hit the vCenter root object, navigated to Manage -> Update Manager and scanned all objects against the attached baselines, all seemed to be going well then it bombed out at the end with Could not scan host and a little more digging (scanned an individual host) yielded Error code: 99.

So, this is all well and good, but why am I talking about Runecast? It is the thing that prompted my to look at the vSphere 6.0 U2 bug that relates to VMXNET3 adapters in this KB в†— - I had vSphere Update Manager installed so decided to update as it is trivial.

ItвЂ™s really very cool, syslogging is also built in, if you add it as a syslog target to your hosts (RCA can do this automatically too) it will monitor the syslogs incoming and search the KB database for any matching problems - I actually found that some of my iSCSI paths werenвЂ™t coming up after failover due to this! I have been testing out Runecast Analyzer в†— in my lab recently - itвЂ™s pretty badass, you can set it up to scan your virtual infrastructure at a vCenter level and will scan your vC, VMs and hosts looking for KBs that may apply, security compliance and best practises.ДЄs you can see my lab isnвЂ™t exactly a model config when it comes to any of these things: