Closed kennyparsons closed 1 year ago
Also, when i re-run with "ShowCoverPageImage": false,
The report finishes in about 30 minutes, having skipped a lot of content and all healthchecks, bestpractices, etc
New-AsBuiltReport : The variable '$Images' cannot be retrieved because it has not been set.
At line:1 char:1
+ New-AsBuiltReport -Report [Microsoft.AD](http://microsoft.ad/) -Target 'server.domain ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,New-AsBuiltReport
This is a bug in pscribo 0.10.0. As you mention the solution is to disable the "ShowCoverPageImage" option.
Update: This error is displayed only with the Word format enabled
The report finishes in about 30 minutes, having skipped a lot of content and all healthchecks, bestpractices, etc
I did not understand this part. Do you mean that the report ended incomplete or that you manually disabled the healthcheck and the report ended faster?
I did not understand this part. Do you mean that the report ended incomplete or that you manually disabled the healthcheck and the report ended faster?
I did not disable anything, left everything on, including healthchecks and best practices. The output simply did not include them any more, even though i know there are section that should have hundreds of these best practices and health checks.
Can you open a new powershell console and rerun the report with the verbose option enabled and send the output to my email?
jcolonf@zenprsolutions.com
Also remember to obfuscate any private data!
@rebelinux I ran with -Verbose and set the whole command to a variable but the only output was
$verbose = New-AsBuiltReport -Report Microsoft.AD -Target ... -Verbose
PS C:\Users\myuser\Documents> $verbose
Microsoft AD As Built Report 'Microsoft AD As Built Report' has been saved to 'C:\Users\myusers\Documents\AB'.
The screen does show a lot of output, but it gets truncated
I just ran again on level 3 with all healthchecks, best practices turned on (html only to avoid the image issue) and no healthchecks are done. Consequently, GPOs is missing a lot of sections:
old run from a couple months ago:
New run just now:
You can save the content to a output file like this: *> output.txt:
New-AsBuiltReport -Report Microsoft.AD -Target server -Verbose *> output.txt
log incoming.
no matter what I do, it will not output healthchecks/best practices in any section, other than Privileged Groups.
Furthermore, it's not generating the wmi filters section, unlinked GPO, Empty GPO, Enforced GPO, or Orphaned GPO sections. So I suppose I should rename this issue to Incomplete output (since the original issue of the image is a known bug, worked around by generating html only.
Did you use the -EnableHealthCheck option?
New-AsBuiltReport -Report Microsoft.AD -Target 'fqdn' -Format Word,HTML -OutputFolderPath 'C:\Users\myuser\Documents\finalrun' -ReportConfigFilePath 'C:\Users\myuser\Documents\AsBuilt\asbuilt1.json' -Verbose
I reviewed the log you sent me and only found access denial errors in some sections but other than that I don't see anything wrong.
So the runtime argument is still required, even if the config file explicitly says true for all the healthcheck options?
The answer is yes, the EnableHealthCheck option is required.
The next version will have a more detailed logging
Were you able to generate the report with the heatlcheck, any progress on this?
Yes, the cli flag was the issue.
Bug description
I've installed this module manually by cloning the repo in my windows powershell in Documents. The config file:
Everything is stock, no modifications. The huge problem is that due to this error, the report was not saved.
So there are two problems:
Command-line input
New-AsBuiltReport -Report Microsoft.AD -Target 'fqdn' -Format Word,HTML -OutputFolderPath 'C:\Users\myuser\Documents\finalrun' -ReportConfigFilePath 'C:\Users\myuser\Documents\AsBuilt\asbuilt1.json' -Verbose
Steps to reproduce
Run the report, wait 65 hours, cry. :(
Expected behaviour
So there are two problems:
Screenshots
No response
Operating System
Windows Server 2019
PowerShell Version
PowerShell Modules
Additional Context
No response
Before submitting