VMware vExpert 2020

Congratulations on your vExpert Award!

I received particularly good news during my vacation. VMware has awarded me the title vExpert for another year.

This award is an honor and motivation to continue my work for the vCommunity. For example by sharing knowledge in blog articles here at ElasticSky.de, or by giving talks at VMUG Meetings or the German VMUG UserCon.

vExpert Badge 2020

VMware vExpert Program

VMware annually awards the title vExpert to members of the community who have distinguished themselves in the past year through their special commitment. The award is aimed at people who have shared their knowledge and passion for VMware technology far beyond the demands of their daily work.


vExpert Tweets on Twitter: #vExpert

VMTN Blog – vExpert 2020 Award Announcement

VMware – vExpert Directory

PowerCLI offline installation

Strict security policies are in place in many corporate environments. This means that it is only possible to access internet resources to a limited extent, if at all. This becomes apparent, for example, when trying to install PowerCLI on a management system. While the availability of PowerCLI modules in the PowerShell Gallery provides an easy way to install or update PowerCLI, this is only possible if access to this external resource is allowed by Powershell. Using the Powershell Gallery requires the NuGet Packet Management Provider. This must also be obtained online.

 Install-Module -Name VMware.PowerCLI -Scope CurrentUser 

If the Internet connection is restricted or blocked, the above command fails. But you can also transfer the modules offline. For this you need a PC with free internet access. Here you use a different command, which does not install the modules, but only downloads them to a defined path.

 Save-Module -Name VMware.PowerCLI -Path C:\temp\PSModules

Copy the entire contents of the PSModules folder to a storage medium of your choice (e.g. USB flash drive) and transfer the files to the desired offline system where PowerCLI is needed.

If you have admin rights on the target system, you can copy files to the loaction below.

 C:\Program Files\WindowsPowerShell\Modules 

Now the PowerCLI modules are also available on the offline system. For a version update the procedure must be repeated. It is advisable to remove the VMware modules before transferring the current ones.

Get-Module VMware.* -ListAvailable | Uninstall-Module -Force

Further customization

Customer Experience Improvement Program (CEIP)

The VMware Customer Experience Improvement Program collects data about the use of VMware products. You can either agree (true) or disagree (false). For offline systems, only the rejection (false) makes sense. The command shown below suppresses future notifications within PowerCLI.

Set-PowerCLIConfiguration -Scope AllUsers -ParticipateInCeip $false -confirm:$false

Ignore invalid SSL certificates

Bei Verwendung selbstsignierter Zertifikate im vCenter verweigert PowerCLI die Verbindung. Dieses Verhalten kann unterdrückt werden mit dem Befehl:

When using self-signed certificates in vCenter, PowerCLI will deny the connection. This behavior can be suppressed with the command:

Set-PowerCLIConfiguration -Scope AllUsers -InvalidCertificateAction Ignore -confirm:$false

Basic Setup vRNI 5.0

VMware vRealize Network Insight (vRNI) – a.k.a “Verni” – version 5.0 was released in late 2019 and can be obtained from the VMware vRNI download page.

I will briefly describe the setup process here. First of all, the approx. 6 GB image file of the appliance must be loaded from VMware Downloads (login required). The appliance needs to be deployed into an existing cluster via the “Deploy OVF Template” wizard of vSphere-Client.

Deployment of the Platform Appliance (Collector)

There’s some naming confusion. The collector appliance is now called “platform” appliance. This makes it a bit difficult to find if you search for the collector in the download portal. 😉

Continue reading “Basic Setup vRNI 5.0”

HA dynamic admission control – bug or feature?

Admission control is part of vSphere High Availability (HA). It enforces and ensures availability in case of host failures. It guarantees that there is enough cluster capacity (memory or CPU) left for a HA failover by preventing VM power on actions that would violate that guarantee.

Since vSphere 6.5 there’s a dynamic calculation of minimum required resources, depending on your host number and host failures you want to tolerate.

Let’s start with an example: A cluster got two equal hosts and should tolerate one host failure. Admission control will make sure that neither CPU, nor memory load will exceed 50% of your total resources. If you lose one host there will be enough resources to restart VMs on the remaining host.

Let’s imagine you’re adding another two hosts to the cluster. The number of host failures to tolerate is still 1, but now dynamic resource calculation kicks in. With now four hosts, admission control will allow you to fill up the cluster to 75% before it will prevent VM power on.

That’s great. Because you just have to define your desired number of host failures to tolerate and HA admission control will dynamically calculate the allowed percentage of cluster resources to use. It works for adding and removing hosts likewise.

Continue reading “HA dynamic admission control – bug or feature?”