Old Powershell Scanner Results

Follow

Ben Gibb

• May 06, 2020 01:02

Howdy,
First up, thank you for adding this amazing feature!

I just started dabbling in the powershell scanner and accidentally output my data as a plain hashtable not a pscustomobject. This left me with an unwanted garbage entry which is affecting reports.

What is the best way to clear this and go again?

0

• 

  Ben Gibb

  • May 06, 2020 02:25

  Looks like it was as simple as exporting, deleting, and re-importing the scan profile.

  I did have one hiccup however where PDQ Inventory crashed when deleting the scan profile. As the program didn't close, and it seemed to have removed the scan profile and data, I went ahead and re-imported it resulting in no data for the clients ($NULL) and two identical powershell scan data's with the same name under reports.

  I removed it again and did a DB backup and optimise (which also restarted the service) and after a re-import things are going swimmingly.

   

  0

  Comment actions Permalink
• 

  Ben Gibb

  • May 07, 2020 00:12

  Embarrassingly, looking back on my edit history, I also just found I had an empty @{} hiding just before my [pscustomobject] that was causing this.
  PDQ Inventory removes the old data the next time you run the scanner.

   

  0

  Comment actions Permalink

Please sign in to leave a comment.