Deploying Multiple Packages with Deploy Once

<< Click to Display Table of Contents >>

Deploying Multiple Packages with Deploy Once

Use Deploy Once when you want to quickly and easily deploy multiple packages. For instructions on using Deploy Once for a single imported package, see Deploying a Single Package with Deploy Once. For instructions on how to use Deploy One for an Auto Deployment Package (Enterprise mode required), see Deploying an Auto Deployment Package with Deploy Once. For an introduction to the Deploy Once window, see Deploy Once Window.

To create a manual deployment for multiple packages using Deploy Once:

1.On the Main Console window, select the packages you want to deploy (Shift+click or Ctrl+click). Auto Deployment packages can also be included in a multiple package deployment (Enterprise mode required).

IMPORTANT: The packages will deploy in the order in which they are selected.

The Multiple Packages page opens.

2.Do one of the following:

On the Multiple Packages page, click Start a deployment with these packages.

On the Toolbar, click Deploy Once .

Click File > Deploy Once (or press Ctrl+D or right-click one of the selected packages and select Deploy Once).

A new blank Deploy Once window opens with the selected packages listed on the top left.

3.(Optional) To manually add a target computer to the list, type a computer name in the Enter Computer Name field, then click Add Computer. Alternately, you can also paste a target computer name (or list of names) directly into the Targets area of the window. If copying a list of names, ensure that there is only one target computer name per line.

When you add a target computer manually, the name appears in the Target(s) list and the system (DNS) checks to be sure it exists on the network. Targets resolved by DNS appear with a green checkmark .

4.(Optional) To add target computers using external sources, click Choose Targets, then select a source:



Active Directory

Select target computers from Active Directory containers or groups.

PDQ Inventory

Select target computers from PDQ Inventory Collections.


Select target computers from Spiceworks Groups.

Target List

Select target computers using other PDQ Deploy Target Lists.

Text File

Select a text file containing a list of target computer names.

When you build a target list with Choose Targets using external sources, you select specific target computers, no matter how you browse for them. For details, see Creating a Target List, Part 2: Choose Targets.

5.Click the Options tab and define the settings you want to apply to the deployments.

The following table provides information on the Deployment settings available in the Options tab of the Deploy Once window:




The credentials used by all deployments from the current deployment. For more information see Credentials in Preferences.

This is the username and password used to connect to the target computer and copy over the necessary files and start the target service. This user must have administrative rights on the target computer, which are needed to copy files to the ADMIN$ share and create and start the remote service. It can be a user account local to the target computer or a domain user if using Active Directory.

Use PDQ Inventory Scan User credentials first, where available

Allows PDQ Inventory's Scan User credentials to be used during the deployment. If selected, the PDQ Inventory Scan Users credentials will be used first. If no Inventory Scan User credentials exist for that target computer, the selected PDQ Deploy credentials will be used.

IMPORTANT: Enterprise mode is required in both PDQ Deploy and PDQ Inventory.

Run As

Determines how the current deployment is executed on target computers.

Note: The Run As settings at the Package level may be superseded by any explicit Run As settings at each Step level.

For a sample demonstration of the Run As options, see the following video.

VIDEO: Deployment Run As Options



Deploy User

Silently executes deployments on target computers.

This setting is appropriate for the vast majority of deployments.

Deploy User (Interactive)

Executes deployments that include both silent and interactive steps. This setting is the same as Deploy User with one important exception—the Windows process running the deployment is run in interactive mode.

This setting is most appropriately used for individual deployments that require user input, but the overall process still requires Administrator rights that logged on users may not have.

This type of deployment requires more processing resources.

IMPORTANT: This feature is available only in Pro or Enterprise mode.

Local System

Executes deployments using the local System account on the target computer. PDQ Deploy connects to the target computer, copies the specified files, then runs the actual deployment service using the Local System credentials.

This setting is used only for installations that require Local System. These types of deployments are very rare.

Logged on User

Attempts to run packages in Interactive mode as the Logged On User of the target machine.

This setting is used to deploy applications that are installed per user or when the logged on user needs to provide information for the deployment to succeed such as a license key. It can also be used to modify the HKEY-CURRENT-USER registry hive for the logged on user or to access user-specific settings such as %APPDATA% or the logged on user’s User directory.

IMPORTANT: This feature is available only in Pro or Enterprise mode.


Sends an email notification when the deployment finishes. (Pro or Enterprise mode required.)

Select one of the two default deployment notifications, Full Details or Summary, or create a custom notification by clicking Edit Notifications. For more information about post deployment emails, see Receiving a Status Email After Deployment and Mail Server Preferences.

IMPORTANT: You must configure the Mail Server settings in Preferences as well as designate at least one email recipient in the selected Post Deployment Notification before you can enable this option.

Remember these targets for next time

Saves the list of targets to use the next time you start a deployment with Deploy Once.

6.Click the Offline Settings tab and define the settings you want to apply to the deployments.

The following table provides information on the Deployment settings available in the Offline Settings tab of the Deploy Once window:



Offline Status

Offline Status settings determines whether target computers will receive a ping or Wake-on-LAN prior to deployment.

Use settings from Package

Uses the Offline Status settings defined at the Package level. For more information, see Creating a New Package, Step 1: Package Properties.

If you select this option but the Offline Status settings are not defined at the Package level, then PDQ Deploy uses the global Offline Status settings settings defined in Preferences.

When you select this option, the subsequent settings are disabled.

Ping before deployment

Performs a ping (ICMP echo) before attempting the deployment. If the target does not respond to the ping within 2 seconds, then the deployment is not attempted on that target. 

Enabling this option can increase the overall speed of the deployment because PDQ Deploy doesn’t waste time with offline target computers.

NOTE: Typically, the ping should take only a few milliseconds. However, if your DNS isn�t solid or your network is experiencing latency issues, then the ping response may take more than 2 seconds. 

When this is not selected, PDQ Deploy attempts the deployment regardless of the online or offline status of the target computer. Leaving this unchecked can increase the overall speed of the deployment because time isn't wasted with offline target computers. If the target is offline or otherwise unavailable, then Windows will timeout after ~60 seconds.

Send Wake-on-LAN and attempt deployment

Attempts the deployment then sends a Wake-on-LAN to offline target computers. The deployment is attempted again if it comes online. After 5 minutes if the target computer is still offline, the deployment will be attempted again. 

The advantage of this feature is that offline target computers can immediately be made available for deployment. However, it can increase deployment time.

IMPORTANT: This feature is available only in Pro or Enterprise mode of both PDQ Deploy and PDQ Inventory. Furthermore, PDQ Inventory must have the MAC address of the target computers’ NICs.

Retry Queue

Retry Queue settings determine how PDQ Deploy handles deployments when the target computers are offline.

Use settings from Package

Uses the Retry Queue settings defined at the Package level. For more information, see Creating a New Package, Step 1: Package Properties.

If you select this option but Retry Queue settings are not defined at the Package level, then PDQ Deploy uses the global Retry Queue settings defined in Preferences.

When you select this option, the subsequent Retry Queue settings are disabled.

Put Offline Targets in Retry Queue

Enables the Retry Queue.

By default, target computers that are unreachable or offline during a deployment are held in the Retry Queue and deployment is retried.

Allowed Retries

Sets the number of retry attempts for an offline target computer. This applies per target per deployment.

The default setting is 72. To set unlimited retries, set this value to 0.

7.(Optional) If you decide to schedule the deployments rather than run it immediately, click Schedule.

For information about scheduling deployments, see Creating Scheduled Deployments.

8.When you are ready to execute the deployments, click Deploy Now.

9.View the progress and the status of each deployment in Deployment Status in the Main Console Window.

During a deployment you can stop deploying to one or more of the pending target computers by right-clicking on the target(s) and clicking Abort. To retry deployments to target computers that fail, right-click the target, and click Redeploy or press Ctrl+R. If a deployment to a target computer fails, you can view details about the failure and possible solutions by clicking the More Info link or the Steps link.

For more information about what happens during and after a deployment, see Verifying Deployment Status.




© 2016 Admin Arsenal, Inc. All rights reserved.

Admin Arsenal is a trademark of Admin Arsenal, Inc. All other product and company names are the property of their respective owners.

Help Version: