vCheck (Daily Report) V3
Initially when I started this script I wanted people to be clear that this was a report that was going to give you a daily summary of any issues which may exist in your Virtual Infrastructure, from the beta testing I did to a select few it was clear that they were expecting this to send them a full inventory of their infrastructure.
That wasn’t the point in this script and I think people now have the idea that this is more of an issue log than an audit script so I will now revert to my original name of…. vCheck.
The key thing to remember is that if an issue does not exist in a particular area then it will not show in the output, when and if issues turn up they will start appearing in the output almost like magic !
I want to thank everyone who is using this script and those who have left a comment, even if its just to say how much you like it !
I especially want to thank Raphaël SCHITZ (http://www.hypervisor.fr/) for all his contributions, he has added some great features to this version and helped me take it to a new level.
The previous version already reported on these areas:
- General Details
- Number of Hosts
- Number of VMs
- Number of Templates
- Number of Clusters
- Number of Datastores
- Number of Active VMs
- Number of Inactive VMs
- Number of DRS Migrations for the last days
- Snapshots over x Days old
- Datastores with less than x% free space
- VMs created over the last x days
- VMs removed over the last x days
- VMs with No Tools
- VMs with CD-Roms connected
- VMs with Floppy Drives Connected
- VMs stored on local datastores
- VMs with CPU ready over x%
- VMs with over x amount of vCPUs
- List of DRS Migrations
- Hosts in Maintenance Mode
- Hosts in disconnected state
- NTP Server check for a given NTP Name
- NTP Service check
- vmkernel warning messages ov the last x days
- VC Error Events over the last x days
- VC Windows Event Log Errors for the last x days with VMware in the details
- VC VMware Service details
So what is added to V3 ?
Well firstly I have fixed some bugs which existed in V2 and made things slightly faster.
The other added features are as below:
- Status report to screen whilst running interactively
- At the top of the script you can now turn off any areas you do not want to report on (this makes it faster to run)
- VMs on Local storage has been changed to report VMs stored on datastores attached to only one host
- VM active alerts
- Cluster Active Alerts
- If HA Cluster is set to use host datastore for swapfile, check the host has a swapfile location set
- Host active Alerts
- Dead SCSI Luns
- VMs with over x amount of vCPUs
- vSphere check: Slot Sizes
- vSphere check: Outdated VM Hardware (Less than V7)
- VMs in Inconsistent folders (the name of the folder is not the same as the name)
- Added the number of issues to each title line
As always please let me know if you have any comments, I already have some great ideas that I could not fit into this version so watch out for V4 !
Also a reminder that this script also checks your Windows vCenter server for services and event logs, it does this via WMI and therefore needs the correct permissions, there is still an area at the top of the script which you can give alternate credentials from the account that is running the script if needed.
If your new to this script and would like more details on how it looks or how to run it please check this post.
The script can be downloaded from here
Brilliant use of correct HTML mark up. Report is just what I needed.
As a blind user of VSphere I find it very difficult to get this kind of information at a glance. This report makes my life a lot easier.
Would you be willing to make a report detailing network and storage configuration?
Well done again!
[...] free and simple way to do this is to run the vCheck PowerShell script created by Alan Renouf (http://www.virtu-al.net/2009/11/04/vcheck-daily-report-v3/). This will give you a great view on these and many other potential issues within your [...]
question on the VM Tools Issues listing…..it is flagging issues on a handfull of VM’s i have, but when i look in vCenter it states the tools are fine and running…..so i’m not sure what the script is checking or what in particular is the issue. any way this can be broken out into more granular issues presented – or an output of the actual issue found? that would be very helpful.
great script. one issue i see is that the VM hardware old query isn’t using the version per host/cluster but the highest hardware version available….for example i have multiple clusters and some are still running esx 3.5 and the correct hardware version for those clusters is v4, but the script flags all of them as old because it wants all the VM’s to be at v7.
This script is magic! A question on setting multiple NTP servers. What is the separator? Is it a semicolon, a comma or a space?
Thanks again!
Is it enough for user which runs this script to have Read-only role permission on vCenter?
and thanks for this great script..