![]() ![]() Additionally, this can be configured at the package level in the Package Properties window, at the time of deployment in the Deploy Once window, or scheduled in advance in the Auto Deployment edit window as well as Schedules. In PDQ Deploy you can enable the global Scan After Deployment setting in Preferences > Deployments to trigger post-deployment PDQ Inventory scans. Since most deployments involve installing applications, it is a best practice to have PDQ Inventory run scans after deployments to keep its database up-to-date. All other product and company names are the property of their respective owners.Running an Automatic Inventory Scan After Deployment PDQ.com is a trademark of PDQ.com Corporation. IMPORTANT: Debug events should be enabled only as directed by PDQ Support. ![]() Logs events that are used for troubleshooting. ![]() Logs events that indicate a significant, successful operation. Logs events that indicate a potential problem. Logs events that indicate a significant problem the PDQ Deploy administrator should act on usually a loss of functionality or data. For more information on how PDQ.com encrypts passwords, see Credentials. Passwords are not included in any data sent to PDQ.com. ![]() IMPORTANT: Any information that could be used for identification will be anonymous including, but not limited to, IP addresses, MAC addresses, domains, computer names, hostnames, and user names. Prior to submitting a ticket, the diagnostic details being sent are available in that window for review. The only time PDQ.com will receive exception/diagnostic data that is not anonymous is when the Submit a Support Ticket window is used to create a support ticket with us. Allows you to opt-in or opt-out of sending anonymous exception/diagnostic data to PDQ.com to improve the products, identify trends, and ideally fix bugs before they ever reach you. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |