The Virtual Machine Computer Optimizer (VMCO) is a Powershell script and module that uses the PowerCLI module to capture information about the Hosts and VMS running in your vSphere environment, and reports back on whether the VMs are configured optimally based on the Host CPU and memory. It will flag a VM as “TRUE” if it is optimized and “FALSE” if it is not. For non-optimized VMs, a recommendation is made that will keep the same number of vCPUs currently configured, with the optimal number of virtual cores and sockets.
Note that the VMCO will not analyze whether your VMs are configured with the correct number of vCPUs based on the VM’s workload. A more in-depth analysis tool such as VMware vRealize Operations Manager can make right-sizing determinations based on workload and actual performance.
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.
- Correcting the files included with the Fling
- Minor updates/fixes
- 2-5-2021 v126.96.36.199 Added escape for parentheses in VM Names (ie, Tanzu VMs) so they will show up in Get-View Filters by VMName
- 2-5-2021 v188.8.131.52 Removed requirement for VMware.PowerCLI due to error re: HorizonView module not supported in Powershell Core
- 2-5-2021 v184.108.40.206 Modified Get-vSphereInfo so it checks the VMName type and if Object or UniversalVirtualMachineImpl it selects just the name
- 4-30-2021 v220.127.116.11 Minor grammar corrections
- 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.
- 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)
- Fixed errors with reporting on VMs with odd number of vCPUs
- Fixed reporting on VMs that have CPU Hot Add enabled
- Fixed issues with odd number of vCPUs
- Fixed issue with reporting on VMs with CPU Hot Add enabled
- Updated documentation
- Modified Get-OptimalvCPU.ps1 to account for vCenters with no clusters
- Modified Error Catches so they display the line number of the error
- Corrected Get-OptimalvCPU.ps1 where sometimes cluster information would show as System.Object.
- 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
- 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
- Fixed calculation of # of vm cores which was incorrectly reporting on some vms
No similar flings found. Check these out instead...
Imager takes care of creating the VM, silently installing and updating the OS, installing applications and agents, sysprepping and finalizing the image for distribution. There is also a powerful "Continue" feature that allows you to stop the flow at a particular stage, do some manual operations or optimizations on the VM, before running the remaining stages
vSAN is highly dynamic HCI system that needs constant monitoring. The VMware vSAN Live Fling is application for iOS and Android for monitoring of vSAN clusters on the go.
The VSAN Hardware Compatibility List Checker is a tool that verifies all installed storage adapters against the VSAN supported storage controller list.
This Fling generates and collects DCT/SVI logs on multiple Horizon View components, remotely, batchly, and in parallel.
The Virtual Machine Computer Optimizer (VMCO) is a Powershell script that captures information about the hosts and VMS running in your vSphere environment, and reports back on whether the VMs are configured optimally based on the Host CPU and memory.