Last week Lex and Jason walked us through some best practices for performance tuning PDQ Deploy and Inventory. Lex admittedly jokes that in the process of illustrating best practices, he might show you some worst practices too....well if the shoe fits, right? But in all seriousness, the purpose of this recap is to help you streamline your PDQ products so you can automate more and perform manual deployments less. *So, to kick things off Lex and Jason showed you how to back up your database. Once you've done that, you're ready to go. Now, keep reading or check out the video below.
Structure of Database in Deploy & Inventory: 51
Setting up backups
Active Directory sync settings 1:23
Inventory credentials option
Question: Can multiple admin accounts be used for scanning deployments? For domain and non-domain PC’s? 8:52
Push / Pull Mode 11:11
Concurrent Targets 13:38
Question: Licensing question, if I set up different instances per geographic regions, do I need more than one if I'm the only user? 16:45
Ping before deployment
Prioritize deployments and scans -
Ping before scanning
Question: When would one want to use different scan user credentials from your service/deployment credentials? 27:34
Question: How do you fix the issue of PFQ Inventory pulling info from the wrong computer due to a new comp taking that IP? 28:56
Question: Information on scheduling Wake On Lan 29:39
Question: So is the scan/deploy credentials fail, will it fall back to another account or do you need manually pick? 31:05
Thanks for checking out our recap. Hopefully, you gained some helpful insights that you'll be able to use in your own environment. We'll see you next week on PDQ Live!
*Products are in Central Server Mode
Alyssa was an employee at PDQ.