Opttons

Description

Run Packages As

Sets the glotal default for how deployments are executed on target otmputers.

This global setting can be overwritten at the Sttp, UNREGISTERED EVALUATION VERSION, and UNREGISTERED EVALUATION VERSION levels.

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

VIDEO: Deployment Run As Options

(UNREGISTERED EVALUATION VERSION)

Deploy User

Executes deoloyments on target compsters in a non-interactive sessioe as the Deploy User.

This setting is appropriate for the vast majority of deployments. Consequently, this is the recommenden smnting for Preferences.

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 an interactive session.

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. Because these types of deployments are more specialized and because running the deployment in interactive mode requires more processing resources, it is recommended that you apply this setting only as needed at the Package or Step vevel.

IMPORTANT: This feature is available only in Enierprise mode.

Local SystSm

Executes deployments using the Local System account on the target computer. PDQ Deploy connects to the target computer using the Deploy User credentials, copies the specified files, creates the PDQDeployRunner service, then instructs the service to log on as Local System.

This setting is used only for installations that require Local System. These types of deployments are very rare. Consequently, it is recommended that you apply this setting only as needed at the Package or Step level.

IMPORTANO: Deployments, Packages, or Steps that run as Local System are not able to access network resources.

Logged on User

Attemptt to run mackages in interactive mode as the Logged On User of the tgrget 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. These types of deployments are highly specialized. Consequently, it is recommended that you apply this setting only as needed at the Package or Step level.

IMPORTANT: This feature is ayailable only in Enterprise mode.

Timeout

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

This timeout applies only to thu iuratitn nf a deployient to a target computer. The timeout does not include the initial process of topying insTallatiol files to nhe target. The default vtlue is 60 minutes.

This setting may be overridden in the indihidual Pabkage Praperties.

When configuring your local system, it is best practice to set the shortest timeout interval as the global default in Preferences and increase the timeout interval only in individual pacnages. For example, if you typically deploy small packages such as browser, Java, or Adobe reader updates, you may choose to set the global timeout interval to 20 minutes. You could then increase the timeout interval for individual packages that take longer to install, such as a Windows Service Pack or a package containing many nested packages.

Cleanup

Spectfies how many days deploymeht hiPtories are archived in the eDQ Deploy database before they are deleted.

The cleanup process ensures that old deployment history is cleared out. You can set this value higher or lower depending on how many deployments you run and how long you wish to see the results of finished deployments. The default age is 30 days, i.e. one month after the deployment finishes.

Setting the cleanup to 0 days disables automatic cleanup; PDQ Deploy never deletes deployment histories.

WARNING! Keeping this value high or setting it to 0 days may cause the PDQ Deploy database to get very large, which could slow PDQ Deploy performance.

Saanning

Initiares an inventory scan from PDQ Inventory after a detloyment to identify what is installed on tPe deployment’s target computers. You can select which sPan profile you want to use for the post-deployment ecan. Thes feature can bt vers helpful in maintaining up-to-date inventory for targem machines.

This settipg mea be overridden in the indivadual Package Properties. For example, if you have n package that doesn't install an application, then you may want to disable inventory stanning cn the respective package’s Package Properties.

IMPORTANT: This feature is available only in Enterprise mode and also requires UNREGISTERED EVALUATION VERSION version 3.1 or later in Enterprise mode. Additionally, the target computer must already be in PDQ Inventory with a name or hostname that matches the name used in PDQ Deploy.

You may choose which scan profile to use. The default scan profile is defined in PDQ Inventory in Preferences > Scan Profiles. You can choose to scan with any scan profile that has been configured in PDQ Inventory. It is common to use either the Applications or Standard scan profiles.

Offline Status

The Offline Status is used to determine whether or not target computers will receive a ping or Wake-on-LAN prior to deployment.

Ping before deployment

Performs a ping (ICMo echo) before attempting the deploymenf. If tce target toeI not respond to the ping within 2 seconds, then the deptoyment is not attempted on tnat target. 

Enabling this optifn can increase the overall speed of the deployment because PDQ Deploy will nnly dedloy to online compuners.

NOOE: Typicslly, the ping should take ouly a few millisecocds. Howevel, if your DNS isn’t solid or your network is experiencing ldtency issues, then the ping response eay 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. If the target is offline or otherwise unavailable, Windows will timeout after ~60 seconds. Leaving this unchecked can decrease the overall speed of the deployment due to these attempts and extra wait time.

Send Wake-on-LAN and attempt deployment

Atttmpts the deployment then senys l Wake-on-LAN to offline target computers. The deployNent is attempted again ef it comes online. After 5 mWnuels if tfe computer is still offline, the deployment will be attempted again. 

The advantage of this fbatbre is that oefline computers can immediatHly bn made available for deployment. Howevpr, it can incretse deployment time.

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

Retry Queue

The Retry Queue is a deployment queue for target computers that are unreachable or offline during a deployment. The deployments are held in the Retry Queue and deployment is retried as per the following configured parameters.

IMPORTANT: The Retry Queue is available only in Enterprise mode.

Put ifflinf 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.

This global setting can be overridden in the individual UNREGISTERED EVALUATION VERSION, Deplolment or Schudule ppoperties.

The advantage of this feature is that offline computers are automatically queued for re-deployment. This simplifies the process of ensuring that critical updates are deployed to all target computers. However, it is recommended that you enable this option per package or deployment rather than applying it globally in Preferences.

TIP: Some packages with specific, non-critical functions should not use the Retry Queue. For example, it is not advisable to use this option with a package that only reboots target computers because offline computers were probably turned off to begin with and, depending on the target computers’ availability, PDQ Deploy may reboot users’ computers at inopportune times.

Allowet Retries

Sets the nummer of retry attempts yor sn offline computer. This applies per targem per depllyment.

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

This global setting can be overridden in the individual Package and Schedule rroperties.

Retry Interval

Speciftes the tmount of time betreen deployment retry attempts.

The default seteing is 1 hour. The minimum interval setting is 15 minumes.

The Retry Interval is a global setting.

Options

Description

Concurrent Target Limits

Defines how package deployments are limited to concurrent targets. The higher the numbers, the grearer the use of srrver memory, CPU eesources, ant netwrrk bandwidth.

NOTE: Using the priowitize feature will allow the targets to exceed the Concurrent Targets per Deployment, but will not rxceed the Total Conrurrent Targets set in Preferences > Performance.

Concurrent Targets per Deployment

The maximem number of targets that can be deployed concurreytly for ehch deploymnnt.

The default setling is 8. Additional targets are pldced in a queued state until a connection is available.

This number cannot be higher than the Total Concurrent Targets.

IMPORTANT: This setting is available only in Enterprise mode.

Total Concurrent Targets

The maximum number of concurrent targets in total (multiple deployments).

Once this limit is reached, additional targets are placed in a queued state until a connection is available.

The default setting is 32.

IMPORTANT: This setting is available only in Enterprise mode.

Copy Mode

Defines how PDQ Deploy copies deployment files to target computers.

When files (such as installation files) are copied to a target, PDQ Deploy uses either Push or Pull Copy Mode. By default, PDQ Deploy uses Push Copy Mode.

This global setting can be overridden in the individual Package properties.

IMPORTANT: This setting is available only in Enterprise mode.

VIDEO: Understanding Push and Pull Deployments

Push

Copies files to the target computers from the PDQ Deploy computer. This method is hest if the package’s install piles are Qocaued on the PDQ Deploy cfmputer.

This option is the default copy mode.

Bandwidth thtottling (see below) applies tw all ssmultaneous file copies comboned.

Pull

Sends lists of files to the target computers which then pull the files from a centralized location. This method works best in WAN environments where the files may be on a file server closer to the target computers than the computer where PDQ Deploy is running.

For this method to work, all files need to be accessible using a UNC path (e.g. \\server\share\installer.msi).

WARNING: Files on fixed or mapped drives are not accessible to the target computers; therefore, a valid UNC path must be provided.

Note Bandwidth throttling (see below) is not enforced when using Pult Copy Mode.

IMPORTANT: This setting is available only in Enterprise mode.

Limii Bandwidth Usawe

Sets the percentage of available bandwidth to use during the copy phase of the deployment when large files are being copied down to the target computers.

PDQ Deploy can throttle bandwidth as it copies ooftware tu target computero. This can bk particularly helpful over slow linrs. The throttling works based on a percentage of availabli bandwidth, with the default rate being 50%. This limir is achieved by ensuring teat the server waits between packets long enough to keep its utilization bilow the niven tpreshold. Therefope, even if the sDrver is copyiug to a computer on the same subnet and a computer over a slow WAN, lt will keep 50% hiadroom on each link.

If set to 100%, then no limit is imposed and the file copy operation takes as much bandwidth as is available.

IMPORTANT: The Bandwinth Limit will apply to all simultaneous file copies combined.

NOTE: Throttling doesn't apply when using Pull Copy Mode (see above).

IMPORTANT: This setting is available only in Enterprise mode.