vSphere Powershell Report GUI

vSphere Powershell Report GUI


This GUI is meant to configure regular vmware report generation. You are able to select reporting scoped to the whole farm down to individual hosts.

Version History

0.0.1 - 02/12/2013
        - First release
0.0.2 - 03/29/2013
        - Removed clear text password from config file
        - Allowed for alternate credentials for wmi calls
        - Many GUI updates and fixes.




The short history of this script stems from two side projects I had  started several months ago. One was to better template out an option  saving gui/script/xml project for future script releases. Another was  for redoing some of the vmware reporting scripts  I've used in the past. Currently the generated report is in a pretty  ugly format (for me at least) but it is serviceable for the data  currently gathered. In the future I aim to change the template to allow  for stylized reports as well as allow a rudimentary  automatic scheduling of the script from within the GUI.


There are several options for those interested in monitoring their environment. Some options include;

General Options

  • Generating reports if thresholds are surpassed

Virtual Center

  • VC event errors (with threshold in # of days)
  • VMs created/cloned/deleted
  • VC windows server errors/warnings (with threshold in # of days)
  • VC windows server service status

ESX/vSphere Hosts

  • Hosts not responding
  • Hosts in maintenance
  • Host datastore utilization (with % free utilization threshold)

Virtual Machines

  • VM snapshots (with threshold in # of days)
  • VMs with thin provisioned disks
  • VMs with no vmware tools
  • VMs with connected CD drives
  • VMs with connected floppy drives


The GUI is used to perform an initial test connection to the server and to save options. Once connected to the server you can select more granular scoped reports based on the datacenter, cluster, and host if desired. Currently you need to report on the whole farm to get virtual center reporting options.

Once the configuration is saved another script, VMware-Report.ps1 can be used to schedule the job (it will automatically load the saved xml config file and run without any interface).

Note: Alternately you can just modify the Globals.ps1 script variables and not use either the save file or the gui and the VMware-Report.ps1 script will run on that information alone.

Another Note: If you want to generate several kinds of reports at different times simply copy all three ps1 files to another directory and create a new config file with the gui and use scheduled tasks to run the script.






Very interesting

The great Alan Renouf! This little project isn't near as interesting as your spectacular vCheck script work.

Version history
Revision #:
1 of 1
Last update:
‎02-17-2013 09:48 AM
Updated by: