We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AsBuiltReport.VMware.vSphere/Src/Public/Invoke-AsBuiltReport.VMware.vSphere.ps1
Line 466 in b4f5483
If the report is generated using the vcenter ip address as -Target the $_.Entity.Name is equal as the IP instead of the vcenter FQDN
PS /home/rebelinux> $VIMachineCertificates = Get-VIMachineCertificate -Server 192.168.5.2 PS /home/rebelinux> $VIMachineCertificates Entity Subject Issuer NotValidAfter ------ ------- ------ ------------- 192.168.5.2 vcenter-01v.pharmax.local pharmax-SERVER-DC-01V-CA 1/25/2024 8:33:… esxsvr-00f.pharmax.local esxsvr-00f.pharmax.local vcenter-01v 5/21/2025 11:50… comp-02a.pharmax.local comp-02a.pharmax.local vcenter-01v 5/28/2026 8:35:… comp-01a.pharmax.local comp-01a.pharmax.local vcenter-01v 5/31/2026 11:45… PS /home/rebelinux> $VIMachineCertificates.Entity.Name 192.168.5.2 esxsvr-00f.pharmax.local comp-02a.pharmax.local comp-01a.pharmax.local PS /home/rebelinux>
Target as IP:
Target as FQDN:
Target as FQDN Report:
If a fix is not possible, it would be a good idea to update the documentation to state that the FQDN of the vcenter should be used.
The text was updated successfully, but these errors were encountered:
v1.4.0 updates
94cc424
- Add vCenter Resource Summary ([Fix #97](#97)) - Add vCenter Machine SSL Certificate information ([Fix #98](#98))
tpcarman
No branches or pull requests
AsBuiltReport.VMware.vSphere/Src/Public/Invoke-AsBuiltReport.VMware.vSphere.ps1
Line 466 in b4f5483
If the report is generated using the vcenter ip address as -Target the $_.Entity.Name is equal as the IP instead of the vcenter FQDN
Target as IP:
Target as FQDN:
Target as FQDN Report:
If a fix is not possible, it would be a good idea to update the documentation to state that the FQDN of the vcenter should be used.
The text was updated successfully, but these errors were encountered: