Knowledge Base
Information about PDQ Deploy
- PDQ Deploy 18 or Later Required to Download New and Updated Packages
- File path too long error when downloading .NET 3.5
- Update does not apply
- Uninstalling software based on the program name
- The user name or password is incorrect (PDQ Deploy Schedule)
- Perform a clean uninstall of PDQ Deploy
- Add a Process condition to a Deploy Package
- PDQ Deploy Performance Best Practices
- Connection from PDQ Inventory not authorized, add user to Console Users
- PDQ Deploy Run Modes
- Windows 10 Adobe Flash Update Packages Now Split by Operating Systems
- Introducing the Scan Step
- Introducing the Logoff Step
- Unable to start scan for COMPUTERNAME: Computer not found in PDQ Inventory
- Introducing the Message Step
- Introducing the Sleep Step
- Introducing the Reboot Step
- Introducing the Command Step
- Introducing the PowerShell Step
- Introducing the Nested Package Step
- Introducing the File Copy Step
- Windows 10 Update Packages Now Split by Architecture
- What You Need to Know Before Building a Package
- Blocking Malware with PolicyPak and PDQ Deploy
- Deploying Apps that Require Admin Rights Using PolicyPak and PDQ Deploy
- PDQ Deploy's Install Step (And Its Many Uses)
- Deploying Multiple Versions of Java to the Same Endpoint Using PolicyPak & PDQ Deploy
- Setting Default File Associations with PolicyPak and PDQ Deploy
- PDQ Live! : Autohotkey... For When There Are No Silent Parameter Options
- Package Names Are Ordered Differently in the Console and the CLI