Jeff Longley
Comments
-
Oooo Share that script! I've tried to work out a "pull" method for PDQ for a while
-
You could change the collection to ignore your wireless IP range; However, when the server deploys, it's going to use DNS to locate the machine, NOT the record it has in the database.
-
That's more a DNS issue than a PDQ issue - have a read of this:http://blogs.technet.com/b/askpfe/archive/2011/06/03/how-dns-scavenging-and-the-dhcp-lease-duration-relate.aspx
-
Its actually one of my favourite features! I usually create a collection for machines that are online and without the specific application. I then schedule a deployment of the app to that collectio...
-
Could you not just use group policy to set your update window to be 1 hour after your deployment time? Then it's just a generic shut down task to put all the machines back down.
-
Run the Application count report, then edit it to add a value filter of "Application publisher contains Microsoft" They're typically interested in overall counts, rather than what's on each machine.
-
I'm also looking at psadt, but would love the functionality in PDQ.
-
Be very interested to hear how you've done this. I'm currently looking at how I can use PDQ with my MDT2013 deployment.
-
File / Preferences / Active Directory.
-
I'm testing PDQ inventory, and have set up a collection that covers machines on the VPN IP address range; I've then got a scheduled deployment task running (currently every 15 minutes) that's targe...