After a VMware ESXi host reinstall reconnecting your host is not as easy as changing the state of the host by using the Set-VMHost -State command in VMware PowerCLI. The reason is that your host has gotten a new certificate. So to do this scripted you need to retrieve the SSL thumbprint and specify that during the reconnect.Continue reading Reconnect ESXi host after reinstall
I am often working with quite large test environments. Powering on ESXi hosts with nested VMs can be a pain when you need to get it running quickly.
Here are some of my tricks to automating VMware WorkstationContinue reading Automating VMware Workstation LAB
Should you buy dedicated hardware or a OP workstation for you next testing environment. If you are not sharing it with others, this might be useful for you.
For many years now VMware Workstation has been my secret weapon an daily tool for just about everything in regards to customer remote connections, test environments as so on.
Recently I needed to do some advanced testing with NSX-V and NSX-T. This required a lot more power than what I normally use so I needed to upgrade my testing platform.
The consideration is always with these things. How much are you going to invest, and what are the benefits. For a long time I have been considering buying 4 Intel NUC PC’s for doing these tests, but the problem is that to get a real setup that is flexible you need to invest a lot. Also it is not very flexible as you need to maintain them, and reinstall them everytime you need to play with a newer or older version.Continue reading Nested or Native
Recently a adjustment was made to the vCenter Cluster HA Agent timeout Settings.
This calles for at script, because there is no way we are going to do this by hand! Feel free to use or alter the script, just remember. It is all done at your own risk.Continue reading VMware HA Cluster: Set-Advanced HA Settings
Back in 2017 VMware changed their policy on VMKlinux Inbox Drivers. This has now come into effect from vSphere 7.0 and onwards.
Unfortunately this means that some otherwise supported hardware platforms, now are having support issue. And you might see the following error in vCenter Skyline Health:
Devices that are only supported in 6.7 or earlier by a VMKlinux inbox driver. This support has been removed in 7.0
This is the case for many Lenovo SR650 servers if they are booting from a SD card, as many will be configured with the Lewisburg SATA AHCI Controller.Continue reading Devices that are only supported in 6.7
When upgrading to vSphere 7 or any other version, you might choose to create a brand new vCenter instead of migrating the old one. But what about folder structure, tags, distributed switches and so on.
Here I will demonstrate how you can easily migrate your tags from one vCenter to another using VMware PowerCLI.Continue reading Migrate Tags from one vCenter to another
After upgrading a 3 vCenter Enhanced Link Mode environment a customer experienced the following error:
Server is at a higher functional level (1) than partner (<partner vCenter server>)(0) and cannot perform at a lower level.
When checking the domain functional level of each of the three servers, they all state that they are at level 1. The other server are starting like normal.
One server is not starting the vmdir service and it is also that service that is reporting the error. Most of the other services on a vCenter is dependant on this the vmdir.
I do not have a solution as of now. I might have a reason for the issue, and I might have a workaround. VMware is currently trying to figure out how to fix this.Continue reading vCenter services not starting after 6.7 Update 3f upgrade
So VMware released a security advisory (VMSA-2019-0009) about vulnerable VMware Tools.
In short it is recommended to upgrade all VMware Tools to at least version 10.3.10 (Build 10346) which is the newest at the time of writing.
After patching ESXi to the latest build, you might realize that the VMware tools you are left with, after upgrading the tools, in a VM, is 10.3.5 (build 10341) Continue reading How to upgrade to VMware Tools 10.3.10
I have found that, when working with VMware vSphere, there are many benefits of running Linux on your workstation.
Things like tight integration with SSH, ISO files, API’s, Python are all things that make your life easier not only on Linux, but also when working with VMware.
I recently installed Powershell Core om Ubuntu 18.04, and after installing the PowerCLI module. I ran into an error.
The error is not an uncommon one, but on Windows the error message makes a lot more sense, so I just wanted to let you know what this error actually means.
The error you might get when you try to connect to your vCenter server using the connect-viserver is the following:
Connect-VIServer : 9/27/18 10:41:37 AM Connect-VIServer The SSL connection could not be established, see inner exception. At line:1 char:1 + Connect-VIServer <servername> + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [Connect-VIServer], ViError + FullyQualifiedErrorId : Client20_ConnectivityServiceImpl_Reconnect_SoapException,VMware.VimAutomation.ViCore.Cmdlets.Commands.ConnectVIServer
The only hint here is “The SSL connection could not be established…”
This actually means that you do not have a valid certificate. And if you want to connect to vCenter without a valid certificate, you have to allow this.
You can either change you vCenter certificate to a trusted one, which is the correct solutions or you can ignore invalid certificates, which circumvents all security, but makes it work right now.
Please comment if this was helpful.