PowerCLI vCheck 5.45 – Updated export options

I started working on this update in the airport the Sunday before VMworld 2011. It is only a minor update to exporting the reports and sending email notifications. In this update, all of the code to send emails and/or export reports has been moved to a function near the top of the code and at the very end of the script (where the export code used to be) I added a call to this function. I think it is now easier to see/edit/understand your output options.

# Version 5.45- bwuch: Updated export options

5.45 – Minor update to the Out-File and Send-MailMessage code; moved into a function in the “config” part of the script and then called from the end.

You can download the updated version here: vcheck5.45.ps1

This entry was posted in Scripting, Virtualization. Bookmark the permalink.

2 Responses to PowerCLI vCheck 5.45 – Updated export options

  1. Ed says:

    I ran into a bug with the number of VMs created or deleted. The script limits the number of event entries to 10,000. If we go back say 14 days, we’re well beyond 10,000 entries so the list of VMs is incomplete.

    Additionally, I posted some code in a comment to 5.40 (I think) that added details on overallocating memory and CPUs. Is this going to be incorporated into a future release or do I need to fork the code and keep my own version merged with your updates?


  2. @Ed,

    Sorry for the delays, I hadn’t had a chance to look at the code you had provided. When addressing the amount of RAM, I also wanted to add a check to look at the vRAM (licensing) stuff. I just posted an updated version of vCheck which includes both the code you provided and @LucD’s vRAM function. You can get the new version here: http://enterpriseadmins.org/blog/scripting/powercli-vcheck-5-47-additional-ram-checks/

    I’ll have to take a look at the VM creation/deletion code. I’m afraid that increasing the number of records parsed might impact performance/execution time of the script.


Leave a Reply

Your email address will not be published. Required fields are marked *


Notify me of followup comments via e-mail. You can also subscribe without commenting.