Although the focus in my career right now is certainly more cloud focused in Amazon Web Services and Azure, I still use my home lab a lot.
For the last 5+ years my home lab had consisted of using 3x Intel NUC’s (i5 DC53427HYE), a Synology NAS for shared storage and an HP ProCurve switch. This setup served me well for most of those years. It has allowed me to get many of the certifications I have, progress in my career and have fun as well.
At the start of this year I decided it was time to give the home lab an overhaul. At first I looked at the newest generation of Intel NUC’s but really wasn’t looking forward to dropping over $1,300 on just partial compute (I’d still need to be RAM for each of the 3 NUC’s). I also wanted something that just worked, no more fooling around with network adapter drivers or doing this tweak or that tweak.
I also no longer needed to be concerned about something that had a tiny footprint. I also questioned if I really needed multiple physical ESXi hosts. My home lab isn’t running anything mission critical and if I really wanted I could always build additional nested VMware ESXi hosts on one powerful machine if I needed.
So in the end, the below is what I settled on. Replacing all of my compute, most of my networking and adding more storage!
VMware has released vCenter Server 6.7 Update 1 and with comes with a number changes.
One most notable change is the feature complete HTML5 vSphere client. The vSphere client in vCenter 6.7 Update 1 now includes the ability to manage:
- Host profiles
- Auto deploy
- Full vSphere Update Manager (VUM)
- A new dark theme
- and vCenter High Availability.
That’s no where near all of the changes though, there are many more changes and updates in the 6.7 Update 1 update. Be sure to read the full release notes here.
In this post we’ll see just how easy it is to upgrade from VCSA 6.7 to VCSA 6.7 Update 1 in just a couple steps!
VMware released ESXi 6.7 a little while ago, but it’s only been here recently have I started deploying it in my home and work lab environments. Below are two ways to easily upgrade your ESXi 6.5 hosts to ESXi 6.7 using the command line or by using the VMware ESXi offline bundle.
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.
Just recently we have some hardware issues in our primary datacenter and during that time had a few VM’s that became unresponsive and needed to get them back online. The VM’s had stopped responding to the normal vSphere commands to reboot, shutdown or even restart. I didn’t want to power cycle the entire ESXi host and instead just power off an unresponsive VM.
Here is a quick and easy way to do just that using ESXTOP.
Just a quick heads up! Over the last week I’ve been upgrading our vCenter servers from version 5.5 to the most recent 5.5 Update 3b version and have ran into a small hiccup.
The upgrade of SSO, Web Client, Inventory Service and even vCenter server all went as expected without any issues. Then I rebooted the vCenter server and after the reboot noticed that the vCenter server service hadn’t started and when I tried to start it manually I then received the following error:
Error 1053: The service did not respond to the start or control request in a timely fashion.