Deploying Packages

To create a new one-time deployment, click the Deploy button at the top right of the Devices or Deployments pages.

Create a new deployment

The Create deployment popup allows you to select the packages you wish to deploy and the targets to deploy to. 

  • Type the name of a package in the left search field and select the package to be added to the deployment. 
  • The latest version of the chosen package will be selected by default. Select the dropdown in the Version column to choose a different version of that package. 
  • To add multiple packages to a deployment, search for another package and select it to add it to the deployment. 
  • To remove a package from the deployment, click the trash can icon for that package in the list.
  • To specify a target for the package deployment, type the name of the device or group in the right search field. 
  • Multiple targets may be added by searching for additional groups and devices. 
Create deployment dialog with Uninstall Google Chrome Enterprise, Mozilla Firefox, Slack, and Greenshot 32bit added, each set to Latest available version, and Windows Workstations added as the target. Cancel and Deploy buttons are at the bottom right.

Deployment status

To view the results of any deployment, select Deployments from the left navigation bar. The Deployments page will display a list of all deployments created in the last 90 days across your entire organization. 

Deployments page with summary tiles for total deployments, success rate, failed deployments, and packages with the highest failure rate, above a table with the columns Last deployment, Deployment, Deployment type, Deployed to, Deployment statuses, Avg. elapsed time, and Deployed by. The Deploy button is at the top right.
  • The Last deployment column displays the time and date the deployment last run.
  • The Deployment column displays the name of the package that was deployed and the version of the package. Historical version numbers are retained for PDQ-provided packages. For custom packages, updating the version number will update it on all past deployments. 
  • The Deployment type column specifies whether the package is a Custom package or a PDQ-provided package.
  • The Deployed to column shows the total number of devices. If only one device is deployed, its name is displayed, and selecting it directs you to the device information page. Selecting the total number directs you to the deployment instance page, showing all devices under that deployment.
  • In the Deployment statuses column, status icons are displayed in the following order: Queued, In progress, Complete, Failed, and Canceled. Each icon shows the total number of devices in that status. Selecting an icon opens the deployment instance page, filtered to show the device(s) associated with that status. Queued deployments are waiting to run, In progress deployments are running, Complete deployments succeeded, Failed deployments did not succeed, and Canceled deployments were stopped before finishing.
  • The Avg. elapsed time column shows the average time it took for the package to finish deploying.
  • The Deployed by column displays the name of the user or Automation that initiated the deployment. Select the name of the Automation to open that Automation's page.

If a custom package is edited while queued for deployment to an offline device, the device will still receive the original version of the package when it comes back online.

Deployment instance page

On the deployment instance page, you can view all devices in a deployment along with their status and logs, and perform actions such as redeploy and cancel.

Deployment instance page with the Actions menu open, showing Redeploy and Cancel. The table lists one device with a Complete status, a View output link in the Output log column, and Return code: 0 in the Details column.
  • Select the status in the Deployment status column, or select View output in the Output log column, to display the output log for that deployment. The output log shows each step of the package.

    Output log for device PDQ-DOC showing four steps, each marked Success: Step 1 Stop Windows Update Service (Script step), Step 2 KB5043080 (64-bit) - Prerequisite (Install step), Step 3 Windows 11 (24H2/25H2) (Install step), and Step 4 Revert Windows Update Service (Script step). An Exit status section below shows Return code: 0.
  • Return codes will be displayed in the Details column. 0 is the default code for a successful deployment. 
  • In the Actions button, select Cancel to stop a running deployment, or Redeploy to retry a failed deployment.
    • You can optionally Redeploy from last failed step when redeploying failed deployments. This will start the redeployment from the step that failed, skipping steps that already successfully completed.  
    • If you edit a package, you can no longer select Redeploy from last failed step for that package's prior deployments, as the step order may have changed.

Redeploy to device dialog asking "Are you sure you want to redeploy?" and explaining that the same package will be redeployed on selected devices with completed, failed, or canceled deployments. A "Start redeployment from last failed step" checkbox is unchecked, with Cancel and Confirm buttons at the bottom right.

You can only redeploy from the last failed step on the deployment instance page. This option is not available from a device's Deployments tab.

Was this article helpful?