In a post earlier in the week, I provided a solution to make ‘vCheck as a vSphere Client “Solutions and Application”‘. This post attempted to resolve feature request items #16 and #17. If you are interested, that post is available here: http://enterpriseadmins.org/blog/?p=258. It is not really a change to vCheck, but some steps that need to happen to make vCheck appear in vCenter.
Today, I’m am posting more updates to vCheck. This updated version includes feature requests #2, #11 and #51.
# Version 5.31- bwuch: Bug fix for LockdownMode # Version 5.30- bwuch: Add check for VMtools installer connected # Version 5.29- bwuch: Add check for VM capacity forecasting # Version 5.28- bwuch: Change to Get-HTMLTable function for possible performance improvements
I’m sure update 5.28 was suggested in the Virtu-Al.net comments, but for some reason I couldn’t find it on the feature request list.
Update 5.29 isn’t perfect and I wanted to let everyone know. There are comments in the code, but I wanted to add them to this post for reference. Instead of looping through all of the virtual machines and adding up the amount of space used, I simply subtract the data store free space from the capacity and assume that is how much is being used. We also make the assumption that no more than 85% of a datastores capacity will be used (to reserve room for thin-provisioned growth, snapshots, changed block tracking and log files). These assumptions make the code run pretty fast, but I’ve seen some oddities in my test environment. (Like -41 virtual machines remaining in a data center I’m sure has enough free space for 1 or 2 more VMs 🙂 ) Here is what I’ve added to the comments of the script for reference:
# The disk forecast will be per datacenter instead of per cluster since # Get-Datastore -Entity only supports VirtualMachine, VMHost, and Datacenter objects. # To improve performance in code, we are going to make the following assumptions # Assumption 1.) Disk capacity - Free Space = space used by VMs # Assumption 2.) used space / count of VMs = Avg Space used per VM # Assumption 3.) we will reserve 15% of capacity for overhead
If anyone else has a better solution (fast and accurate) please let me know.
Here is version 5.31 for those interested: Download vCheck5.31.ps1.txt