vDocumentation provides a community-created set of PowerCLI scripts that produce infrastructure documentation of vSphere environments in CSV or Excel file format.
First - Great job! Second on to my issue. I am running the 2.4.7 version of your script and continue to see an error at line 314 char 9, which appears to be this line:
$pciDevices = $esxcli.hardware.pci.list.Invoke() | Where-Object {$.VMKernelName -like "vmhba*" -or $.VMKernelName -like "vmnic" -or $_.VMKernelName -like "vmgfx"} | Sort-Object -Property VMKernelName
Example:
Gathering information from usndcesx.us.deloitte.com ...
Object of type 'InternalVimApi_50.ManagedObjectReference' cannot be converted to type 'System.String'.
At C:\Users\xxx\Documents\WindowsPowerShell\Modules\vDocumentation\2.4.7\Public\Get-ESXIODevice.ps1:314 char:9
First - Great job! Second on to my issue. I am running the 2.4.7 version of your script and continue to see an error at line 314 char 9, which appears to be this line: $pciDevices = $esxcli.hardware.pci.list.Invoke() | Where-Object {$.VMKernelName -like "vmhba*" -or $.VMKernelName -like "vmnic" -or $_.VMKernelName -like "vmgfx"} | Sort-Object -Property VMKernelName
Example: Gathering information from usndcesx.us.deloitte.com ... Object of type 'InternalVimApi_50.ManagedObjectReference' cannot be converted to type 'System.String'. At C:\Users\xxx\Documents\WindowsPowerShell\Modules\vDocumentation\2.4.7\Public\Get-ESXIODevice.ps1:314 char:9
Errors repeats for all hosts in this vCenter. Seen this issue?