Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

Powershell Module PDQStuff

Patrick Garber

March 06, 2023 18:51

Hi guys. I had been using the PSPDQ Powershell module up until I updated my console to 19.3.365.0 it was working great. But it looks like that module doesn't work with this current version. Since that modules no longer being updated, I was looking at Colby's PDQStuff. While great, I was hoping to see if there's a way to grab all collection members from a specified collection. I used that feature in PSPDQ to grab all collection members and run a script to check certain services and restart down services.

Comments

4 comments

Colby Bouma
March 06, 2023 19:12
I haven't added anything that PDQ's CLI can already do. I believe the following command does what you want:
```
PDQInventory.exe GetCollectionComputers
```
0
Patrick Garber
March 06, 2023 19:23

Thanks. I tried that too but it didn't return anything, which I found odd. Maybe I'm just doing it wrong. Doing GetCollection -Collection <name> works to return the collection data (name, path, etc) but GetCollectionComputers -Collection <name> returns an empty line.

0
Colby Bouma
March 06, 2023 23:33
Huh, that's strange. The following works correctly for me. "Odd" is a collection with 3 members, and it returns all 3 computer names.
```
PDQInventory.exe GetCollectionComputers -Collection "Odd"
```
0
Patrick Garber
March 07, 2023 14:30

I figured it out. I had an OU named the same as the collection I was going for. Oddly enough, PDQ wasn't pulling anything out of the AD OU so that's an issue but that's my issue. I renamed the other collection to something unique and re-ran that command and it worked as expected. All set. Thank you!

0