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
Agent Backup Job schedule section show an empty table on a Linux type job
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
Show information in the schedule section
windows 10
Name Value ---- ----- PSVersion 5.1.19041.3693 PSEdition Desktop PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...} BuildVersion 10.0.19041.3693 CLRVersion 4.0.30319.42000 WSManStackVersion 3.0 PSRemotingProtocolVersion 2.3 SerializationVersion 1.1.0.1
Name Version ---- ------- AsBuiltReport.Veeam.VBR 0.8.4 AsBuiltReport.Core 1.3.0 PScribo 0.10.0
No response
The text was updated successfully, but these errors were encountered:
Agent Backup Job schedule section empty table AsBuiltReport#134
c4a0666
rebelinux
Successfully merging a pull request may close this issue.
Bug description
Agent Backup Job schedule section show an empty table on a Linux type job
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
Expected behaviour
Show information in the schedule section
Screenshots
Operating System
windows 10
PowerShell Version
PowerShell Modules
Additional Context
No response
Before submitting
The text was updated successfully, but these errors were encountered: