You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Run "Get-SecFileIntegrity", rename the output to $Copmputername-Integrity-Baseline.xml, then re-run "Get-SecFileIntegrity". Manually edit the newer file's text and save. Then create 2 objects ($new & $base), by using the Import-Clixml cmdlet. Then run...
... but the
8000
resulting formatting is garbage. I'm going to look at a friendly way to get what you're looking for. Will post back with revisions, once I have them ironed out. Really like your module though! :)
Since (I'm pretty sure) you're using this for other comparisons, take a look at this. It gets all provided properties, from the imported XML's, and runs a comparison on each...
Run "Get-SecFileIntegrity", rename the output to $Copmputername-Integrity-Baseline.xml, then re-run "Get-SecFileIntegrity". Manually edit the newer file's text and save. Then create 2 objects ($new & $base), by using the Import-Clixml cmdlet. Then run...
Compare-Object -DifferenceObject $new -ReferenceObject $base -CaseSensitive
... it doesn't come back as having any difference, but if you change the Import-Clixml, to Get-Content, and recreate the two objects, and run this...
Compare-Object $new $base
... you can see the changes.
The text was updated successfully, but these errors were encountered: