top of page

FlashArray: VM Topology Requirements Checker PowerShell script

[ NOTE: machine translation with the help of DeepL translator without additional proofreading and spell checking ]

How can I make sure that my VMs meet all the requirements to use the latest features of VM Topology? It's simple: use the script below. It's always annoying - in the worst case scenario - when you want to use features of individual tools and find that they don't work due to dependencies on other systems.

As mentioned in my recently published post (UPDATED VM Topology: Pure Storage VM Collector Setup - deep VMware storage analyzes and monitoring) the latest version of Pure1 VM Topology provides additional functionality to analyze your virtual environment. This assumes that the VMware tools are not older than version 10.1, which from experience is not always the case in large infrastructures.

There are ways and means to have the installed versions of the VMware tools reported (many customers do this as well) and also to simply update the VMware tools during the recurring patchday. If you don't have this possibility and still want to make sure that your VMs meet the requirements to use all features of VM Topology or want to proactively identify "outdated" machines, then you've come to the right place.

The "VM Topology Requirements Checker" PowerShell script does it for you based on a few parameter requests:

  • Installation of the VMware PowerCLI module

  • Checking your VMs for their VMware tools installed or running on versions older than 10.1

By running the script, you ensure that all metrics are provided for optimal processing within VM Topologies.


To use the PowerShell script, the following system requirements must be met.

To the client:

  • Windows PowerShell Version

  • VMware PowerCLI Module

  • Connection over port 443/HTTPS between client and the vCenter

The following system requirements can be created with the help of the script (option 1):

  • Installation VMware PowerCLI-Modul

How To: Use VM Topology Requirements Checker script

The script can be downloaded free of charge in the member area. The registration is done quickly, it is non-binding and revocable at any time. Beside the script there are already several other contents available for download. So it is worth to register: to the protected area.

I have packed the script together with the release notes into a ZIP file, which is 243 KB in size due to screenshots. After successful unpacking you have to run the Windows PowerShell as administrator. This is mandatory to install the corresponding PowerShell modules.


HINT: Please read the release notes included in the ZIP!


Run script with administrator privileges

The script is executed as administrator. The VMware PowerCLI is necessary as interface module. The menu then takes you to the individual script options.

With option 1 you can install the VMware PowerCLI module without further ado. If this is already on your client, this step can be skipped. Of course, a temporary user with sufficient privileges is required here for the module installation.


HINWEIS: If you are using the module for the first time, VMware would offer you a participation in the "Customer Experience Improvement Program" (CEIP) at this point (in the course of using the PowerCLI). I thankfully decline here and ignore this message.

If this message bothers you, you can also disable it (as noted) via the corresponding PowerShell command:

Set-PowerCLIConfiguration -Scope User -ParticipateCEIP $false

Now that you have created the prerequisites, you can proceed to the actual thing. As soon as you have executed option 2 of the script, the vCenter to be connected is queried immediately. A prompt will then ask for the appropriate credentials.


HINT: In the case of an unencrypted connection (e.g., a connection via IP), certificate errors may occur, resulting in a failed connection setup. If the FQDN and a suitable certificate are available, there will be no problems at this point.

For connections via IP addresses I recommend to ignore all invalid certificate messages via PowerShell command before:

Set-PowerCLIConfiguration -InvalidCertificateAction ignore -confirm:$false

The script now checks whether all VM tools within the vCenter meet the requirements for using the features of VM Topology and outputs corresponding violations of the requirements.

Feedback on the script is welcome via the comment function.

In case of problems it is worth to have a look at the release notes.

Otherwise I wish you a lot of fun using the script.

More info - Links

All officially published setting options in the GUI but also CLI can be read via the "on-board" user guides of the Pure Storage systems.

Click on "Help" in the Purity main menu.

The User Guide is structured like the main menu and can be opened downwards. A search function is also integrated - within here you can also search for keywords.

WEB: Pure Storage (Pure1) support portal - Ticket system and support *(requires registered FlashSystems)

PHONE: Pure Storage phone support: GER - (+49) (0)800 7239467; INTERNATIONAL - (+1) 650 7294088

WEB: Pure Storage community

WEB: Pure Storage OFFICIAL blog

The blog lives from your questions, wishes and suggestions...every comment is welcome. I am very grateful for feedback.

188 views0 comments
bottom of page