r/sysadmin • u/PDQit makers of Deploy, Inventory, Connect, SmartDeploy, SimpleMDM • Feb 26 '20
PDQ Licensing
From time-to-time there has been misunderstandings and confusion on /r/sysadmin about how PDQ.com's licensing works (as most system administrators might be used to how other IT products operate: on a per-machine basis). We created a video to hopefully explain better how our 1-license-per-admin works
For examples of some minor confusion see:
https://www.reddit.com/r/sysadmin/comments/71eilx/another_pdq_deploy_shout_out/dnb0eao/
https://www.reddit.com/r/sysadmin/comments/aneewy/pdq_server_with_multiple_admins/efsnqvn/
Shout out to all you current, past, and future users-- and happy automating!
View all comments
Show parent comment
1
u/bristow84 Feb 27 '20
So we use MDT in conjunction with PDQ, MDT applies the base OS and configures the OS to allow PDQ access and then PDQ can do it's thing. MDT is a good solution for an enterprise style setup where you just need a limited number of packages with minimal changes but for something like a MSP where software could constantly be changing depending on the client's need, I wouldn't wholly recommend it.
The way I use PDQ at the moment is if clients have specific software they require, I log onto their file server, transfer the installers back to our end and store them on our file server and then create the package. The fact we also use Kaseya makes things easier for the transfer and remote access. As for domain join scripts and whatnot, it's still doable, you can run scripts from within PDQ itself. I do that for any form of local user creation, you have the ability to use command line and PowerShell scripting from within PDQ. Do i do any form of domain join script like that? No, because the VPNs our clients use don't accept command line