-
Notifications
You must be signed in to change notification settings - Fork 12
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
Comments
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: After saving the log, reset powershell to default settings: $global:VerbosePreference = 'SilentlyContinue'
$global:DebugPreference = 'SilentlyContinue' |
Jonathan,
Please find attached the output.log file. I see now the teminating error "ScriptContent" which I thought was corrected already.
Thank you for taking the time to check it out,
Mark
…________________________________
From: Jonathan Colon ***@***.***>
Sent: Tuesday, November 19, 2024 12:45 PM
To: AsBuiltReport/AsBuiltReport.Microsoft.Windows ***@***.***>
Cc: Leopard, Mark A. ***@***.***>; Author ***@***.***>
Subject: Re: [AsBuiltReport/AsBuiltReport.Microsoft.Windows] As Built Report Does Not Capture Local Users and Groups (Issue #36)
You don't often get email from ***@***.*** Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
This message came from an external source. Please exercise caution when opening any attachments or clicking on links.
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:
***@***.******@***.***>
After saving the log, reset powershell to default settings:
$global:VerbosePreference = 'SilentlyContinue'
$global:DebugPreference = 'SilentlyContinue'
—
Reply to this email directly, view it on GitHub<#36 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BNCA23GJ5S3WU6QLID7TO2L2BN2K7AVCNFSM6AAAAABSCM5GJWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBWGM3DGMZYGI>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
This message and any attachments may contain information that is confidential, privileged and/or protected from disclosure under state and federal laws. If you received this message in error or through inappropriate means, please reply to this message to notify the Sender that the message was received by you in error, and then permanently delete this message from all storage media, without forwarding or retaining a copy.
|
Where is the output.log file? |
It was attached to my reply to your email.
It must have been stripped off. I'll try an upload to GitHub instead.
Mark
…________________________________
From: Jonathan Colon ***@***.***>
Sent: Tuesday, November 19, 2024 6:50 PM
To: AsBuiltReport/AsBuiltReport.Microsoft.Windows ***@***.***>
Cc: Leopard, Mark A. ***@***.***>; Author ***@***.***>
Subject: Re: [AsBuiltReport/AsBuiltReport.Microsoft.Windows] As Built Report Does Not Capture Local Users and Groups (Issue #36)
You don't often get email from ***@***.*** Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
This message came from an external source. Please exercise caution when opening any attachments or clicking on links.
Where is the output.log file?
—
Reply to this email directly, view it on GitHub<#36 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BNCA23FNN5KZ7PXJEN2FDPD2BPFEVAVCNFSM6AAAAABSCM5GJWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBWHE4TSNJYGM>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
This message and any attachments may contain information that is confidential, privileged and/or protected from disclosure under state and federal laws. If you received this message in error or through inappropriate means, please reply to this message to notify the Sender that the message was received by you in error, and then permanently delete this message from all storage media, without forwarding or retaining a copy.
|
Did the attachment come through this time?
Mark
…________________________________
From: Jonathan Colon ***@***.***>
Sent: Tuesday, November 19, 2024 6:50 PM
To: AsBuiltReport/AsBuiltReport.Microsoft.Windows ***@***.***>
Cc: Leopard, Mark A. ***@***.***>; Author ***@***.***>
Subject: Re: [AsBuiltReport/AsBuiltReport.Microsoft.Windows] As Built Report Does Not Capture Local Users and Groups (Issue #36)
You don't often get email from ***@***.*** Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
This message came from an external source. Please exercise caution when opening any attachments or clicking on links.
Where is the output.log file?
—
Reply to this email directly, view it on GitHub<#36 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BNCA23FNN5KZ7PXJEN2FDPD2BPFEVAVCNFSM6AAAAABSCM5GJWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBWHE4TSNJYGM>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
This message and any attachments may contain information that is confidential, privileged and/or protected from disclosure under state and federal laws. If you received this message in error or through inappropriate means, please reply to this message to notify the Sender that the message was received by you in error, and then permanently delete this message from all storage media, without forwarding or retaining a copy.
|
In case the email attachment did not make it through. Thank you. |
Please try v0.5.6 and let me know if the problem is fixed!
|
Yes, it appears to be fixed now.
Thank you,
Mark
…________________________________
From: Jonathan Colon ***@***.***>
Sent: Wednesday, November 20, 2024 12:57 PM
To: AsBuiltReport/AsBuiltReport.Microsoft.Windows ***@***.***>
Cc: Leopard, Mark A. ***@***.***>; Author ***@***.***>
Subject: Re: [AsBuiltReport/AsBuiltReport.Microsoft.Windows] As Built Report Does Not Capture Local Users and Groups (Issue #36)
You don't often get email from ***@***.*** Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
This message came from an external source. Please exercise caution when opening any attachments or clicking on links.
Please try v0.5.6 and let me know if the problem is fixed!
Update-Module AsBuiltReport.Microsoft.Windows -Force
—
Reply to this email directly, view it on GitHub<#36 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BNCA23AEEFW2C2OQ7LACMSD2BTEQFAVCNFSM6AAAAABSCM5GJWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBZGIZDONBYG4>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
This message and any attachments may contain information that is confidential, privileged and/or protected from disclosure under state and federal laws. If you received this message in error or through inappropriate means, please reply to this message to notify the Sender that the message was received by you in error, and then permanently delete this message from all storage media, without forwarding or retaining a copy.
|
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
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
The text was updated successfully, but these errors were encountered: