Virtual Machine Compute Optimizer

In order to run the Virtual Machine Compute Optimizer, you will need the following:

• Windows 7/Server 2008 or above
• Powershell v5 or higher
• Access to the internet. The VMCO will attempt to install or update the modules needed (PowerCLI and VMCO)
• A user account with Read-Only rights assigned at the vCenter level with ‘Propogate to children’enabled. These rights will be needed on each vCenter that will be analyzed.

There are a few ways you can launch a Powershell script.

Please see the PDF for full instructions in the download box.

Version 3.0.0

• Correcting the files included with the Fling

Version 3.0.0.5

• Minor updates/fixes
• 2-5-2021 v3.0.0.2 Added escape for parentheses in VM Names (ie, Tanzu VMs) so they will show up in Get-View Filters by VMName
• 2-5-2021 v3.0.0.3 Removed requirement for VMware.PowerCLI due to error re: HorizonView module not supported in Powershell Core
• 2-5-2021 v3.0.0.4 Modified Get-vSphereInfo so it checks the VMName type and if Object or UniversalVirtualMachineImpl it selects just the name
• 4-30-2021 v3.0.0.5 Minor grammar corrections

Version 3.0.0

• Script will install or update the required modules (VMCO and PowerCLI). The script is now a single script that acts as the easy button to walk through the module installs, connecting to a vCenter, and exporting the results.

Version 2.1.0

• Fixed errors in reporting for some VMs that are on hosts with 4 sockets
• Fixed “memory” missing from Details when VM memory spans pNUMA nodes
• Added ability to call function with “-simple” which only reports VM info (leaves out vCenter, Cluster, and Host)

Version 2.0.4

• Fixed errors with reporting on VMs with odd number of vCPUs
• Fixed reporting on VMs that have CPU Hot Add enabled

Version 2.0.3

• Fixed issues with odd number of vCPUs
• Fixed issue with reporting on VMs with CPU Hot Add enabled
• Updated documentation

Version 2.0.2

• Modified Get-OptimalvCPU.ps1 to account for vCenters with no clusters
• Modified Error Catches so they display the line number of the error

Version 2.0.1

• Corrected Get-OptimalvCPU.ps1 where sometimes cluster information would show as System.Object[].

Version 2.0.0

• Priority of the findings are captured
• Details on the findings are included
• Cluster information is captured to determine if Host HW is not consistent across the cluster
• Report if a VM spanning pNUMA nodes actually has the pNUMA exposed to the guest OS
• Report if advanced settings have been changed on the VM or host level to expose pNUMA to the guest OS
• Reports if the number of vCPUs for a VM exceeds the physical cores of the host (using hyperthreads as vCPUs)
• Ability to use the stand alone “Get-OptimalvCPU” function for more flexibility

Version 1.0.4

• Added a -Property filter to the Get-View commands for hosts and VMs to reduce time and amount of returned data
• Removed if statement in Get_Optimal_CPU function that included $hostCPUs as it was not yet being used

Version 1.0.3

• Fixed calculation of # of vm cores which was incorrectly reporting on some vms