🤘 7 reputation

BrianGreen

Standard

Joined: 6/18/2018

Last seen: 4/17/2019

Activity
  • Yup, I'm for this. I have script tasks that I don't care WHEN they get there, just that they do. I'd rather them take a back seat to more pressing packages. In SCCM, we were able to make a deployment as Low, Medium, High. I'd be fine with something like that too.

  • I would kill for something like this. I'm using Applocker to track launches, and then filtering them out, poorly, using a badly written powershell script.

  • You can create a package that has a command step in it and call it like:

    DISM /Online /Cleanup-Image /RestoreHealth /Source:ESD:c:\installtemp\Sources\Install.esd:1

    For us, we're storing the 1803 image on the root of the drive so it doesn't have to pull it across the network to run a health check.

  • While I'd rather have a built-in step, this will work also, thanks!

  • Works for me. I was concerned that Inventory would spend a lot of time enumerating query collections under a header that it didn't need to. If it's static, hopefully it won't slow down adding machines to collections

  • Feature Request: Run if User Has Locked Machine
  • cscript.exe c:\windows\system32\slmgr.vbs /ipk [key]

    cscript.exe c:\windows\system32\slmgr.vbs /ato

  • Creating folders in Inventory?
  • Worked with the guys, cleaned up the database which should help. But also came across another possible fix:

    Saw that it failed most often when selected "NOT a member of collection x". It seems it times out when enumerating if it's NOT part of a collection. So instead, I build a dynamic collection that held this query - if it DOESN'T have a certain application, add to this dynamic collection. Then instead of selecting "NOT a member of collection", I pointed it to this collection and said "if it IS part of this collection"...

    We'll find out on our next rollout if it fixes it.

  • Package should fail based on PDQ error...
  • We ran into the same problem. You can create a PDQ job to disable by modifying a key in the registry. reg add "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Power" /v HiberbootEnabled /t reg_dword /d 0 /f

  • Like this idea.

  • Ack, I just reread your question and I didn't see the 'external' piece. You could just monitor the ones that show up and do what I mentioned, or you could run the linked method through psexec when they come online.

  • Nope.. you should be able to find them automagically in PDQ:

    enter image description here

    Highlight the ones under the "PDQ Agent (Not Installed)" collection, select Install Agent.

  • I've got ours setup as a command-prompt task, running like such:

    c:\windows\system32\cscript //B c:\windows\system32\slmgr.vbs

    Which seems to work fine.

  • Another +1. SCCM has "Low, Medium, High" options for deployments. I'd like to see something like this as well so low sends can go when nothing else critical is in front.

  • You can also use Spiceworks Inventory for this - it's free and integrates into PDQ as well.

  • enter image description here

    This is how I'm doing it.

  • We have a share setup in namespaces, and have it replicated through DFS to all of our outlying locations.

    Under Repository in Deploy, we have it pointing to this share. From that point, we use the $(Repository) variable to pull from the local DFS share so it doesn't pull across the WAN.

    For the sites that do not have a local DFS share (we have a couple of outliers), I installed chocolatey on the remote workstations and have it pulling packages across the internet using a PDQ job.

  • Did this get resolved? I seem to be having the same issue.