MDT and PDQInventory

Comments

4 comments

  • Brad McClave

    There are a lot of different ways to do this. You can do this on a heartbeat or on membership of a domain OU. It's up to you to decide what works best. I have mine setup to start deploying when the computer has been in PDQ Inventory for less than a day. That indicates a new PC and tells PDQ Deploy to start installing applications.

    0
    Comment actions Permalink
  • Gareth Edmondson

    Hi - thanks for the reply.

    Can it be set earlier than this? Pressure is often on to get a machine done on the day.

    Cheers

    Gar

    0
    Comment actions Permalink
  • Brad McClave

    Again, that depends on your settings. For example, how often is your AD environment scanned? If it's every hour and you have deployments set against membership of an OU, the deployments will happen within an hour, once PDQ Inventory scans AD and sees that computer in the specific OU.

    0
    Comment actions Permalink
  • Gareth Edmondson

    Hi @Brodiemac

    Thanks for this. Sounds good. Whilst experimenting I think I will set PDQInv to scan every hour to see how it goes. Does it put much overhead on the network?

    Our machines are already in the AD as they join into the correct place via MDT and when re-deployed they just take the same name based on mac address. So I assume once the scan has taken place then PDQInv will see them there and deploy.

    Gareth

    0
    Comment actions Permalink

Please sign in to leave a comment.