PDQ Inventory - Next Step

[garethEds]

Afternoon All,

 

Having successfully sorted out W10 and deploying with MDT and PDQDeploy, there is now some funding for PDQInventory. So - I've bought it :-)

 

How much change to I need now - am I right in thinking I can create groups of computers that only need certain apps? At the moment our PDQDeploy/MDT solution installs everything to machines - but they quite often don't need every piece of software.

 

So will PDQInv let me split the packages into groups - and then use MDT to deploy with the 'base set' of applications via PDQ Deploy and then when they have built and joined the domain let PDQInv kick in with the packages that need to go to certain groups.

 

For example the 4 ICT Suites need VB - but nobody else does.

 

One of the ICT Suites and our media suit need Adobe Creative Suite

 

But they all need the base apps deployed at build time. They also all need SIMS but this cannot be deployed until the machines have joined the domain so cannot happen during deployment time.

 

Does this simplified description sound like it's right?

 

Edit: After reading this page again: https://www.pdq.com/blog/mdt-imaging-in-pdq-deploy/ - I'm thinking the first option is right - using the hearbeat trigger to kick off once Windows 10 has been deployed.

 

Gareth

Edited September 4, 2019 by garethedmondson