Greg Harms

This may need to be solved in concert with your mail server administrator to understand why the mail server is rejecting the message. From the error, it would seem that...

I'm successfully executing the same vCheck code (version 6.25) against four vCenter 6.0 servers (Windows) and four vCenter 6.5 servers. Per [VMware Product Interoperability Matrices](https://www.vmware.com/resources/compatibility/sim/interop_matrix.php#interop&299=&2=&hideEmpty=false&hideUnsupported=false), PowerCLI 6.5.1 doesn't support vCenter...

Looks like both your originating error and the current error reside in the calls to the Get-VIEventPlus function, according to the line numbers in the error. In the `00 Connection...

Some talk about this being a bug in the 6.5 API - https://communities.vmware.com/message/2764714#2764714 - with talk about downgrading to PowerCLI 6.3 (to force 6.0 API connection) or exclude certain events...

`-noe` as an argument to PowerShell.exe means noexit. Remove it from your task arguments so you don't have to forcibly stop the task. Other suggestions for vCheck as a scheduled...

Sometimes, PowerCLI API uses cached data and reports different sensor values than vCenter. There's a KB with more information. [vSphere ESX/ESXi hardware status sensors return different cached values in API...

Commenting to say I experienced the same issue where the order of property names in Select-Object is not reflected in ConvertTo-Markdown output.