Skip to content
New issue

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

As Built Report Does Not Capture Local Users and Groups #36

Closed
3 tasks done
Mark-githb opened this issue Nov 19, 2024 · 8 comments · Fixed by #37
Closed
3 tasks done

As Built Report Does Not Capture Local Users and Groups #36

Mark-githb opened this issue Nov 19, 2024 · 8 comments · Fixed by #37
Assignees
Labels
bug Something isn't working

Comments

@Mark-githb
Copy link

Bug description

When running an asbuilt report against a Windows 2022 server using version 0.5.5, the report does not capture the Local Users and Groups. When using 0.5.1 with the same parameters, this information is captured.

Command-line input

New-AsBuiltReport -Report Microsoft.Windows -Target 'xxxxx' -Credential $Cred -Format Word -OutputFolderPath 'C:\temp' -timestamp -filename xxxxxx

Steps to reproduce

  1. Execute the line above.

Expected behaviour

The asbuilt report to be produced with the Local Users and Groups reported as in previous versions.

Screenshots

No response

Operating System

Using Windows 11 to execute the script against a Windows 2022 server.

PowerShell Version

Name Value


PSVersion 5.1.22621.4391
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.22621.4391
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

PowerShell Modules

Name Version


AsBuiltReport.Core 1.4.0
AsBuiltReport.Microsoft.Windows 0.5.5
PScribo 0.10.0
AsBuiltReport.Core 1.4.0
AsBuiltReport.Core 1.3.0
AsBuiltReport.Microsoft.Windows 0.5.5
AsBuiltReport.Microsoft.Windows 0.5.3
AsBuiltReport.Microsoft.Windows 0.5.2
AsBuiltReport.Microsoft.Windows 0.5.1
AsBuiltReport.Microsoft.Windows 0.4.0
PScribo 0.10.0

Additional Context

No response

Before submitting

@Mark-githb Mark-githb added the bug Something isn't working label Nov 19, 2024
@rebelinux
Copy link
Collaborator

Could you run these cmdlet and send me the logs?

Enable powershell debugging:

$global:VerbosePreference = 'Continue'
$global:DebugPreference = 'Continue'
Start-Transcript -Path .\Output.log
New-AsBuiltReport   <-- change this part with your parameters-->
Stop-Transcript

The commands generate the Output.log file which you can send to me at:

jcolonf@zenprsolutions.com

After saving the log, reset powershell to default settings:

$global:VerbosePreference = 'SilentlyContinue'
$global:DebugPreference = 'SilentlyContinue'

@Mark-githb
Copy link
Author

Mark-githb commented Nov 19, 2024 via email

@rebelinux
Copy link
Collaborator

Where is the output.log file?

@Mark-githb
Copy link
Author

Mark-githb commented Nov 20, 2024 via email

@Mark-githb
Copy link
Author

Mark-githb commented Nov 20, 2024 via email

@Mark-githb
Copy link
Author

Output.log

In case the email attachment did not make it through. Thank you.

@rebelinux rebelinux mentioned this issue Nov 20, 2024
7 tasks
@rebelinux rebelinux mentioned this issue Nov 20, 2024
7 tasks
@rebelinux
Copy link
Collaborator

Please try v0.5.6 and let me know if the problem is fixed!

Update-Module AsBuiltReport.Microsoft.Windows -Force

@Mark-githb
Copy link
Author

Mark-githb commented Nov 20, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants