<\/span>Patching vCenter<\/span><\/h2>\nLogin to VAMI, lets see what I’m on:<\/p>\n
![\"\"](\"https:\/\/i.imgur.com\/xcRJlUK.png\")
<\/a><\/p>\nHere’s the fix Matrix:<\/p>\n
![\"\"](\"https:\/\/i.imgur.com\/9nrA1nu.png\")
<\/a><\/p>\nCan you tell if I’m good, no cause the Matrix uses a different version coding (7.0 u3q) vs the version shown in VAMI (7.0.3.01700). You can either look up, by googling the version, which I did and it’s 7.0 u3o), or clicking the link in the KB and checking the build number<\/a>.<\/p>\n![\"\"](\"https:\/\/i.imgur.com\/owRaEPA.png\")
<\/a><\/p>\nVMware: constructive criticism.. make the Matrix have the same versioning syntax as VAMI so it’s easy to know, and verify.<\/p>\n
Anyway, in VAMI click update. there it is….<\/p>\n
![\"\"](\"https:\/\/i.imgur.com\/DJzwbR5.png\")
<\/a><\/p>\nAccept the EULA, Pass pre-update checks, Installing…<\/p>\n
![\"\"](\"https:\/\/i.imgur.com\/uHZUvDW.png\")
<\/a><\/p>\n![\"\"](\"https:\/\/i.imgur.com\/KSMGEWt.png\")
<\/a><\/p>\n![\"\"](\"https:\/\/i.imgur.com\/GjB9TDP.png\")
<\/a><\/p>\nIt’s chugging along…<\/p>\n
![\"\"](\"https:\/\/i.imgur.com\/uinjwcI.png\")
<\/a><\/p>\nat this point the vCenter regular web interface was unresponsive, and had to use the host that was running the VCSA to get the CPU usage. However, as you can see VAMI appears to be up and showing status just fine.<\/p>\n
45 Minutes later…<\/p>\n
![\"\"](\"https:\/\/i.imgur.com\/ceMjMsQ.png\")
<\/a><\/p>\n![\"\"](\"https:\/\/i.imgur.com\/oDWzE4R.png\")
<\/a><\/p>\nalright… 1% woo, woo, woo! Why does this seem oddly familiar…. mhmm anyway. After about an hour…<\/p>\n
![\"\"](\"https:\/\/i.imgur.com\/RSyhEKq.png\")
<\/a><\/p>\nRe-log into VAMI.<\/p>\n
![\"\"](\"https:\/\/i.imgur.com\/RnISHAh.png\")
<\/a><\/p>\nLooks good, going to the main mgmt page… mhmm shows 404, but by the time I wanted to get a snip, it refreshed to show the FBA page, so I logged in like normal.<\/p>\n
![\"\"](\"https:\/\/i.imgur.com\/Ajd9Zcf.png\")
<\/a><\/p>\nYay it worked.<\/p>\n
<\/span>Patching ESXi<\/span><\/h2>\nIn vCenter, go to the host, pick updates, then baseline, and check compliance.<\/p>\n
![](\"https:\/\/i.imgur.com\/FL5Vo0R.png\")
<\/p>\n
On the two baselines, select them and pick remediate.<\/p>\n
![\"\"](\"https:\/\/i.imgur.com\/5QZoxHf.png\")
<\/a><\/p>\nServer went into maintenance mode, and after about 20 min (I think it rebooted, I didn’t have an active ping on it, not sure will check on the next one).<\/p>\n
![\"\"](\"https:\/\/i.imgur.com\/8b9Glg6.png\")
<\/a><\/p>\nMy PA-ESXi is a special beast, it for some reason needs a helping hand during boot, so we’ll know if it reboots this time…<\/p>\n
![\"\"](\"https:\/\/i.imgur.com\/URFUSSb.png\")
<\/a><\/p>\nyup… it rebooted.<\/p>\n
<\/a><\/p>\nHere’s the fix Matrix:<\/p>\n
Can you tell if I’m good, no cause the Matrix uses a different version coding (7.0 u3q) vs the version shown in VAMI (7.0.3.01700). You can either look up, by googling the version, which I did and it’s 7.0 u3o), or clicking the link in the KB and checking the build number<\/a>.<\/p>\n VMware: constructive criticism.. make the Matrix have the same versioning syntax as VAMI so it’s easy to know, and verify.<\/p>\n Anyway, in VAMI click update. there it is….<\/p>\n Accept the EULA, Pass pre-update checks, Installing…<\/p>\n It’s chugging along…<\/p>\n at this point the vCenter regular web interface was unresponsive, and had to use the host that was running the VCSA to get the CPU usage. However, as you can see VAMI appears to be up and showing status just fine.<\/p>\n 45 Minutes later…<\/p>\n alright… 1% woo, woo, woo! Why does this seem oddly familiar…. mhmm anyway. After about an hour…<\/p>\n Re-log into VAMI.<\/p>\n Looks good, going to the main mgmt page… mhmm shows 404, but by the time I wanted to get a snip, it refreshed to show the FBA page, so I logged in like normal.<\/p>\n Yay it worked.<\/p>\n In vCenter, go to the host, pick updates, then baseline, and check compliance.<\/p>\n On the two baselines, select them and pick remediate.<\/p>\n Server went into maintenance mode, and after about 20 min (I think it rebooted, I didn’t have an active ping on it, not sure will check on the next one).<\/p>\n My PA-ESXi is a special beast, it for some reason needs a helping hand during boot, so we’ll know if it reboots this time…<\/p>\n yup… it rebooted.<\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/span>Patching ESXi<\/span><\/h2>\n
<\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n
![\"\"](\"https:\/\/i.imgur.com\/0VDxUig.png\")
<\/a><\/p>\n