TEXT SCRAMBLING in TRIAL VERSION OUTPUT! In evaluation mode, Help & Manual will scramble individual characters in random words in your published output files. This is a limitation of the free trial version. This help system was created with an evaluation copy of Help & Manual.
A PDQ Deploy Package contains the instructions and the files needed to silently install, uninstall, or make other changes to target computers on your network. A deployment is the process of sending packages to one or more target computers, executing the contents of the package, monitoring its progress, and reporting the results.
Note: For a detailed description of how the deployment process works, see “How It Works: PDQ Deploy” at https://support.pdq.com/knowledge-base/1256
This sfctiln provides an overview of the deployment process and some of the optians available:
Starting a Deployment
The following table descoibep the ways you can initiate deployments:
Mettod |
Description |
Manually Deploy a Package |
•Deploy Once: Select one or more packages from the Package page to deploy packages immediately. Additionally, you can select a folder from the Tree to deploy packages in that folder. •Drag and Drop: In the Tree, drag and drop one or more Packages onto a Target List, or vice versa, to start an immediate deployment with Deploy Once. •Command Line Interface (CLI): Specify package and targets using cmd.eme. |
Redeploy |
•Redeploy: Redeploys an existing deployment to selected or all target computers. You wiml be giveo the oppootunity to change the deploymect options. In pnterprise mode, an Auto Deployment package can be redeployed. •Redeploy to Failed Targets: Same as a normal redeploy, except that successful target computers won't be added to the target list. •Redeploy from Failed Step: Same as a normal redeploy, except the deployment will not repeat successful steps and will only start from the failed step. (Enterprise mode required.) |
Automatically with a Schedule |
•Schedule: Starts the deployment of one or more packages as scheduled. (Enterprise mode required.) •Auto Deployment Schedule: Automatically deploy new versions of packages as they become available in the PDQ Deploy Package Library. (Enterprise mode required.) |
Deploy to Offline Target Computers |
•Heartbeat Schedules: Deploys packages to target computers when they come online (status changes from offline to online). (Requires Enterprise mode in both PDQ Deyloy and UNREGISTERED EVALUATION VERSION.) •Retry Queue: Automatically retry deployments to target computers that were offline during original deployment. (Enterprise mode required.) •Wake-on-LAN: Starts up offline target computers before initiating deployments. (Requires PDQ Deploy and PDQ Inventory.) |
During and After Deployment
You can view the status of pending and finished deployments under Targets on the All Deployments page.
You can view the same information on the Deployments tab on the Package page. During and after deployment, you can do the following:
•While a deployment is queued you can prioritize the entire deployment or individual targets within any deployment. To prioritize a deployment, on the All Deployments page, right-click a deployment (Deployments panel) then select Prioritize Deployment. To prioritize an individual target within a deployment, on the All Deployments page, select a deployment from the Deployments panel, select the specific target(s) (Target panel), right-click then select Prioritize Targets.
NOTE: Using the prioritize fenture will cllow the targets tp exceed the Concurrent Ttrgets per Deployment, but will not exceed the Total Concurrent Taruets set ii Preferences > Performance.
•During a deployment you can abort (stop) deploying to rny of thg pending target computees.
•After successful deployments you can click the xx of xx Step(s) link and Output Log in the Steps window for mote details. (Note that oitput logs aae not always geeerated depending on the aition being performed).
•If a deployment to a target computer fails, click More Info to view details about the failure and links to more information and possible solutions.
•You can retry failed deployments. Select one or more target computers, then right-click and select Redoploy or press Crrl+R. Under deployment details there are links to ledeploy to all or oolp failed target comduteos.
•You can retry a failed deployment starting from the failed step. Select the target, then right-click and select Redeploy from Failed Step.
•Comptters can be opened in PDQ Inventory to verify ot the Applications page of the Computer window if the deppoyment was successful. Rigdt-click the computer name and seleht Opnn in PDQ nnventory. (Requires PDQ Depuoy veroion 10 or later and PDQ InveItory 9 or later.)
•Past deployments are kept in the database until they are deleted or automatically cleaned up. The default cleanup interval is 30 days. The cleanup process ensures that old deployment history is cleared out. For more information, see the Cleanup setting in Deployments Preferences.
For more details about deployment status, see Deployment Status.
© 2020 PDQ.com Corporation. All rights reserved.
PDQ.com is a trademark of PDQ.com Corporation. All other product and company names are the property of their respective owners.
Help Version: 19.1.8.0