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
After updating report to v0.8.4 no Virtual Labs is displayed
New-AsBuiltReport -Report Veeam.VBR -Target veeam.domain.local -AsBuiltConfigFilePath C:\Users\jocolon\AsBuiltReport\AsBuiltReport.json -OutputFolderPath C:\Users\jocolon\AsBuiltReport\ -Credential $cred -Format HTML -ReportConfigFilePath C:\Users\jocolon\AsBuiltReport\AsBuiltReport.Veeam.VBR.json -EnableHealthCheck
Run report
Virtual Labs content
No response
Windows 10
Name Value ---- ----- PSVersion 5.1.19041.3803 PSEdition Desktop PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...} BuildVersion 10.0.19041.3803 CLRVersion 4.0.30319.42000 WSManStackVersion 3.0 PSRemotingProtocolVersion 2.3 SerializationVersion 1.1.0.1
Name Version ---- ------- AsBuiltReport.Veeam.VBR 0.8.5 AsBuiltReport.Core 1.3.0 PScribo 0.10.0
The text was updated successfully, but these errors were encountered:
Fix No Virtual Labs after v0.8.4 AsBuiltReport#142
5489b2c
cba69cf
rebelinux
Successfully merging a pull request may close this issue.
Bug description
After updating report to v0.8.4 no Virtual Labs is displayed
Command-line input
New-AsBuiltReport -Report Veeam.VBR -Target veeam.domain.local -AsBuiltConfigFilePath C:\Users\jocolon\AsBuiltReport\AsBuiltReport.json -OutputFolderPath C:\Users\jocolon\AsBuiltReport\ -Credential $cred -Format HTML -ReportConfigFilePath C:\Users\jocolon\AsBuiltReport\AsBuiltReport.Veeam.VBR.json -EnableHealthCheck
Steps to reproduce
Run report
Expected behaviour
Virtual Labs content
Screenshots
No response
Operating System
Windows 10
PowerShell Version
PowerShell Modules
Additional Context
No response
Before submitting
The text was updated successfully, but these errors were encountered: