Reference > Preferences

Specify how many minutes deployments should run before being timed out by the server.

This timeout applies only to the duration of a deployment to a computer. The timeout does not include the initial process of copying installation files to the target. Default value is 60 minutes. For individual packages that may take longer than an hour (such as a Windows Service Pack or a package containing many Nested Packages) it is recommended to increase this value at the Package Properties level.

Cleanup

You can set this value higher or lower depending on how many deployments you create and for how long you wish to see the results of finished deployments.

Setting the cleanup to 0 days will disable automatic cleanup and all deployments will need to be deleted manually.

Note keeping this value high (or unlimited) could cause the PDQ Deploy database to get very large which could slow down PDQ Deploy.

Scanning

Initiate a scan with PDQ Inventory after a deployment. This can be very helpful in maintaining up-to-date inventory for target machines. The target computer must already be in PDQ Inventory with a name or host name that matches the name used in PDQ Deploy.

Since the vast majority of deployments involve installing applications it is a Best Practice have the Scan After Deployment set to scan computers using the Applications Scan Profile.

This can also be set in individual packages which will override the default setting here. For example, if you have a package that doesn't install an application then you may want to disable this feature in the Package Properties.

Pro Mode is required to use scanning.

Note Requires PDQ Inventory version 3.1 or later in Pro Mode.

Offline Settings

Setting	Description
Use Ping for Offline Testing	When checked, only deploy to targets that respond to a ping. The ping timeout is 2 seconds (2000 ms). When unchecked no ping is sent and the deployment is simply attempted.
Send Wake-on-LAN to Offline Computers	If a target computer does not respond to a ping then a WOL (Wake-on-LAN) packet is sent to the target computer. The deployment will wait for the target to come online and then deploy. If the computer does not come online within 5 minutes the deployment will be attempted.

Pro Mode or higher is required to use the Wake-on-LAN option.

Note Wake-on-LAN option requires PDQ Inventory to be installed and the target computer to have been scanned to get its MAC address.

Offline Retry Queue

Setting	Description
Put Offline Computers in Retry Queue	When enabled, target computers that are unreachable or offline during a deployment will be placed in a Retry Queue. This setting can overwritten at the Package and Deploy/Schedule levels.
Retry Queue Interval	Specifies the amount of time between deployment retry attempts. The default setting is 1 hour. The minimum interval setting is 15 minutes. This is a global setting and applies to targets in the Retry Queue.
Allowed Retries	Sets the number of retry attempts for an offline computer. This applies per target per deployment. The default setting is 72. To set unlimited retries set this value to 0. This value can be overwritten at the Package and Deploy/Schedule levels.

Deployments

Timeout

Cleanup

Scanning

Initiate a scan with PDQ Inventory after a deployment. This can be very helpful in maintaining up-to-date inventory for target machines. The target computer must already be in PDQ Inventory with a name or host name that matches the name used in PDQ Deploy.

Since the vast majority of deployments involve installing applications it is a Best Practice have the Scan After Deployment set to scan computers using the Applications Scan Profile.

This can also be set in individual packages which will override the default setting here. For example, if you have a package that doesn't install an application then you may want to disable this feature in the Package Properties.

Pro Mode is required to use scanning.

Note Requires PDQ Inventory version 3.1 or later in Pro Mode.

Offline Settings

Setting

Description

Pro Mode or higher is required to use the Wake-on-LAN option.

Offline Retry Queue

Setting

Description

Put Offline Computers in Retry Queue

When enabled, target computers that are unreachable or offline during a deployment will be placed in a Retry Queue. This setting can overwritten at the Package and Deploy/Schedule levels.

Retry Queue Interval

Specifies the amount of time between deployment retry attempts. The default setting is 1 hour. The minimum interval setting is 15 minutes. This is a global setting and applies to targets in the Retry Queue.

Allowed Retries

Sets the number of retry attempts for an offline computer. This applies per target per deployment. The default setting is 72. To set unlimited retries set this value to 0. This value can be overwritten at the Package and Deploy/Schedule levels.