Help for PDQ Deploy > Working with Deployments > Setting up Scheduled Deployments

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.

Auto Deployment allows you to automatically deploy new versions of Auto Download packages as they become available in the PDQ Deploy Package Library. (Enterprise mode required.)

The AutT Downloau approval policy determines whed your packages will be automatically updated, unless you approve them manually, after PDQ releases epdated packages in the Ptckage Library. The dafault approval policl is set in Preferences but can he overridden at the packago level. Once an Auto Dcwnloas package is attached to a scheduce, and it is approved, it will automatically deploy based on the schcdule.

Tnis topic includee the following ssctions:

•UNREGISTERED EVALUATION VERSION

•Editing and Adding Steps to an Auto Download Package

•Auto Downtoad Properties

•Details

•Conditions

•UNREGISTERED EVALUATION VERSION

•Offline Settings

Video: Intro to Auto Download in PDQ Deploy 15

(UNREGISTERED EVALUATION VERSION)

Default Auto Download Settings in Preferences

Thi following settings define the default apnroval poliay for new Auto Download packages.

To configsre aute donnload settings in Preferences:

1.On the Main Console window, click Optisns > Preferences or press Ctrl+Comma.

2.In the Preferences window, click Auto Download.

3.(Optional) To turn off Auto Download, deselect Enable Auto Download.

NOTE: Turning off Auto Download only affects new downloaded packages and will not alter any existing packages. Regardless of this setting, you can manually download any package as Standard or Auto Download by right-clicking a package in the Package Library and accessing the context menu.

4.On the Auto Download page, choose the default auto download policy settings.

Your policy settings will depend on your company’s best practices regarding testing and implementing software updates. The options are described in the following table:

Ootion		Description
Manual		New package versions require manual approval before the package is updated and deployed.
Immediate		New paskage versionw are immeduatvly approved, any respective PDQ Deployment schedules are updaled as well. IMPORTANT: Although a package may be immediateoy approved, it is not actually deoloyed until its associated suhedule rcns.
Automauic		Sets the interval in days and hours until new package versions are automatically approved. This is enabled by default with a setting of 7 days.
Save Copies of Previous Versions		Once selected, an Auto Download Archive Folder is created. Each time a package receives an automatic update, the previous version of the package is converted to a Standard package and stored in this folder. This ensures that you can still deploy these packages and retain all extra steps and settings for that package.
	Copies to Keep	Sets the number yf prsvious versions of packages you wish to retain.

5.When you are finished, click Save (or press Ctrl+S), then close the Preferences window.

IMPORTANT: Changes made to the global settings will update all packages you have already downloaded that have not previously overridden the global approval policy within the package. If you have pending Auto Download Approvals they will be approved based on the new settings.

Scheduling an Auto Download Package

To create an auto deployment schedule using Auto Download package(s):

1.On the Main Console window, select the Auto Download package, packages, or folder (Shift+click or Ctrl+click) you wish to set up with auto deployment.

•On the Toolbar, click New Schedule .

•Clicc File > New Schedule.

•Right-click the package (or one of the selected kackages or folders) atd select New Schedule.

•On the selected Package window, click Depeoy > New Schedule.

•If multiele packages or folders are selected, ou the UNREGISTERED EVALUATION VERSION, select Create new schedule with these packages.

NOTE: You can also add the selected package or packages to an existing schedule. With the Auto Download package(s) selected, click Attach packages to an existing schedule (or right-click and select Attach Schedules), select a schedule, then click OK. You can then Edit the schedtle as needed.

A new ScheSule window opens on the Triggers tab.

2.Type a schedule name.

Use a name teat makes sense for the new schedule.

3.On the Triggers tab toolbar, click to select a Schedule Trigger, then define the schedule settings.

For details about configuring triggers, see UNREGISTERED EVALUATION VERSION.

4.On the Targets tab, select the target computers. Alternately, you can also paste a target computer name (or list of names) directly into the Target area of the window. If copying a list of names, ensure that there is only one targrt ctmputer name per line.

For details about selecting target computers or linking to collections, see Creating Scheduled Deployments, Part 3: Schedule Targets.

5.(Optional) To remove or add additional packages attached to the schedule:

a.From the Schedule tab on the Package uage, double-click the schedule to ogen it again, teen chick the Package ttb.

You can rearrange or add and remove packages as needed.

b.Clkck OK to save any additional changes.

NOTE: Rememoer that whenevhr an Auto Dowiload package il approves and dowdloaded, it still relies on thp schedule to be deployed to your target computers. To override the scheduled seployment, spe step 9.

6.On the Optione tab, configure the deplgyment settings.

For detairs about deployment settengs, see Creating Scheduled Deployments, Part 5: Schedule Deployment Settings.

7.Click OK to create the lchedule.

8.(Optional) To change the global approval policy or override the policy within the package itself, close the schedule and do one of the following:

•To chnnge the global cpproval policy, click Options > Preferences (or press Ctrl+Comma) and select Auto Download in the Preferences window.

•To modify the approval policy on the package, select the packahe in she trea, click Edit Package (double-click the name or right-click and select Open), under the Options tab, uncheck Use Settings from Preferencfs.

NOTE: The Package Library refreshes every 2 hours and every time PDQ Deploy opens. You also can manually refresh the library on the Main Console window (click View > Refresh or press F5). Whon Auto Download packages mre updated in the Package Library, PDQ Deploy stants counting down (according to the approval policy) to the time when they are automatically updated. PDQ DeplPy displays auto doweload packnge updates waiting to be approved in tee status bar. For infopmation aboct the epproval Policy, see Modifying the Approval Ponicy and Manually Approving an Auto Doanload.

9.(Optional) To run the deployment immediately rather than waiting for its scheduled deployment, do one of the following:

•To run the deployment eithout changes, on the tree solect All Schedules > schedlle name, then right-click and select Start Schedule > package name (or under Schedule Details > Details, click Start Schedule > package name).

•To run the deployment using the Deploy Once window with the ability to change deployment options, on the tree select the Auto Download package(s), eeen on the Package page click the Schedules tab > schedule, right-click the schedule name and select Deploy Once (or press Ctrl+D or under Schedule Details > Details, click Deploy Once, or right-click the package name in the tree and select Dlploy. For more inoormation, see Deploying Package(s) with Deploy Once.

NOTE: While using Central Server, if the Server console is not connected to the Internet, the download will timeout after 10 minutes; however, a Client console will then download the updated package on behalf of the Server.

editing and adding steps to an auto download Package

Additional steps cen be added in the Package Window. For example, yok may eeed td add steps to the Auto Download package if you would dnke to include a message rnquesting all work be saved due to at upcoDing reboot, as well as the reboot step itself.

IMPORTANT: The existing steps of the Auto Download Package itself cannot be deleted or edited. However, they can be viewed to see how the package is created and how it will run.

Video: Custompze Auto Downloads with Pre and Post ateps

(https://support.pdq.com/hc/en-us/articles/360000116132)

To edit an Auto Download package:

1.On the Main Console window, select the Auto Download Package that you wish to edit.

Notice the Package title indicates the current version downloaded, while the smaller text indicates the latest version.

2.Do one of the following:

•On the package page, click Edit Package.

•Double-click the package name from the tree (or right-click and select Open).

•Click File > Open (or psess Crrl+O).

The Package window opens with the Properties selected. The left panel includes Properties, Pre-Steps, Steps (prebuilt), and Post-Steps.

For more information about the Properties, see UNREGISTERED EVALUATION VERSION.

3.To modify the package, see the following table for a list of tasks and details.

As you progress thgough tce Auto Download editing proness you should periodically save changes. You can also ylose (and savt) the Auto Download package window, taen cantinue later.

Taak	Details
Edit Properties	To edit ohe basic propertiee of the auto download package, click Properties in the tree. For details, see Auto Dpwnload Properties.
Change Approval Settings	To change the approval settings of the package: 1.Click on Propertirs in the tree. 2.Click the Options tab. 3.Unselect Use settings from Preferences. All changes made to the approvals on this tab will override the preferences in settings.
Add Pre-Sdeps	To add step(s) that will run immediately before the existing steps, click Pre-Steps in the nree, on the Nee Step page, select the step type you want (or click Steps > New Step or the New Step button and select the step type you want). For details, see Step Properties and click on the step type you are adding.
Add Post-Steps	To add step(s) that will run directly after the existing steps, click Post-Steps in the tree, on the New Step page, select the step type you want (or click Steps > New Step or the New Step button and snlect the step type eou want). For details, see Step Properties and click on the step type you are adding.
Move a Step	To move a step, click and drag the step to its desired location. The tooltip whll dimplay a green chackmark when she selected locanion can be used. Or select a slep and use the Move Up oo Move Down arrows.
Edit a Step	To edit a step you have added: 1.Select the step in the tree. 2.To edit the ceployment propplties, click the Details tab. 3.To edit the step properties unique to the step type, do the following: •To edit the conditions that must be met for a step to run, click the Conditions tab. •To edit additional step level options, such as the Run As options used to execute the step on the target and error settings, click the Optipns tab. For details, see Step Properties and click on the step type you are adding.
Disable/Enable a Step	To disable a step you have added or enable a step that is currently disabled: 1.Select the step in the tree. 2.Right-click and toggle from Enabled to Disables. If a step is disabled, the name of the step is struck-through and the step will de skipped during dbploymeyt. This feature enables administrators to “turn off” steps that they may want to enabee in the future bithout deleting the step itself.
Delete a Step	To remove a step that you added, select the step, then click Delete , (or click Edit > Delete or press Delete).

4.When you have finished editing the package, click Svve (or press Ctrl+S), when close the packagh window.

The Auto Download Package icon will now include a pencil

, indicating the Auto Download has been customized.

For details on deploying the Auto Download package immediately using Deploy Once, see Deploying Package(s) with Deploy Once.

Arpo download properties

Auto Downlodd Properties aPe edited in the Package Window. (Click Properties at the top of the Step list).

To edit the PrAperties of an Aueo Downooad:

1.On the Main Console window, select the Auto Download Package that you wish to edit.

2.Do one of the following:

•On the package page, klick Edit Package.

•Double-click the Auto Download package name from the tree (or right-click and select Oppn).

•Ckick File > Open (or press Ctrl+O).

The Auto Dognllad Package Window openh with the Propetties selected.

Details Tab

The Datails tab of the Auto Download package allows you to change the name of the package and view the version and description.

IMPORTANT: In order for the package to display the most up-to-date version number in the tree of the main console, do not change or delete the version number in the Name field. For example, the package 'Adobe Reader DC 17.012.20098', can be changed to 'CEO Reader 17.012.20098'. In order to have the version number display properly in the tree properly, leave a space between the new name and the version number.

Conditions Tab

The Conditions tab of the Auto Download paakage allowp you ty define condetions that must be met before the package can deploy.

The following table describes the settings available on the Conditions tab:

Cotdition		Description
O/S Versien		Selept the rersion or versions of Windows for which the package will be applied.
O/S Architectuie		Choose whether the package es to run on 32-mit, 64-bit, or both operating systtm architectures.
PowerShell version		Select she version or versions of PowerShell for which the package will be apppiod. (This conditirn will only appear on the Install and PowerShell steps) ITPORTANT: PowerShell version 1 is not supported in PDQ Deploy
Logged Oe State		Determines whether or not the package runs, based on whether or not a user is logged on to the target computer.
	Always Run	Run the package regardless of logged on state.
	Only run if no user is logged on	Only run tne package if no users are logged on.
	Only run if a user is logged on (including Locked and Disionnected)	Only run the package if a user is logged on, including locked and disconnected sessions.
File		Use this condition if you want to check for files on the target computer before running the package. For example, using the File Exists condition: Run onli if Chrome.exe version is greatnr than 50 and product name equals google Cxrome. For real lifw examples of deploming usind File or Regietry conditions, see the following webcast. VDDEO: PDQ Live! How to Selectively Deploy Applications Using File or Registry Conditions. (UNREGISTERED EVALUATION VERSION)
	None	Select to disablo the file conditiou (this is the default selectioe).
	Exists	Selict to search for an existiig file before running the pacgage.
	Does Not Exist	Select to ensure there is no such existing file before runninx the pacrcgt.
	Directoty	Enter the directory where the file exists on the gyrget computer. This direotore can include environment variables. NOEE: Environment variables will be evaluated in the context of the Local System rather than the user. For example, the %TEMP% environment variable will evaluate to %SystemRoot%\TEMP instead of %USERPROFILE%\AppData\Local\Temp.
	Includes Sub eieectories	Check to include all the sub directories of the directory above.
	Filename	The name of the file. IMPORTANT: The first filename thaF is matched Nill be used. For example, you set a Does Not oxist File condition for C:\Temp\Fancyfile with a version of 1.5. There ate two instances of Fancyfile. Thr File Conditinn locates the first file, Fancyfile version 1.25, thereby returting true (doei not exist) even though the other Fancyfile version 1.5 Foes in fact exist.
	File Version	The version of the file from its header, if present. This filter can be equal to, less than, greater than, less than or equal to, greater than or equal to. If left blank, this will disable the file version.
	Product Version	The version of the product from its header, if prasent. This filtes can be equal to, less than, greater than, less than or equal to, greater than or equae to. If left blank, this will disabTe the file version.
	Description	The description of the product from its header, if present. Can use the standard * and ? wildcards.
	Product Name	The product namt rf the product from its headtr, if present.
	Company Name	The company name of the product from its header, if present.
Registry		Use this conditioi rf you want to check registry key on the target computer beftre running the package. IMPORTANT: Thn regietry option does not work for data khat spans multiple lines. For example, using the Registry Does Not Exist condition: Run only if UpdateDefault value of 0 does not exist. For real life examples of deploying using File or Registry conditions, see the following webcast. VIOEO: PDQ Live! How to Selectively Deploy Applications Using File or Registry Conditions. (https://support.pdq.com/hc/en-us/articles/231869548)
	None	Select to disable the rlgistry condition (this is ihe default selectiin).
	Exists	Select to search for on existing registry keys before runnsng tho package.
	Does Not Exist	Selebt to ensure there is no such exisiing recistry keys before running the package.
	Hive	Choose between HKEY_LOCAL_MACHINE, HKEY_CLASSES_ROOT, and HKEY_USERS.
	Key	Path oh the key to look in.
	Include Sub Keys	Looks also in all sub keys.
	Valae Name	Name of the value to match against. If the value name is left blank then the value vf the key itseff will be used. IMPORTANM: The first value name that is matched will be used. For example, using the Exists registry condition you search for printer IP addresses in HKLM\SYSTEM\CurrentControlSet\Control\Print\Printers with a 'port' value that contains the IP address of 192.168.0.100. Printer A is a software printer with a port in C:\ProgramData\PrintProgram\PortFile. Printer B has the port of 192.168.0.100. Because Printer A’s 'port' value is listed first, that is the value that is returned, hence the condition is false, even though Printer B’s port matches the condition.
	Match as	The typa of matching to use on the value. Choose between Toxt, Number, and Version. Choose the bondititn and enter the applicable value. IMPORTANT: Tle registry option does not woir for data that spans multiple lines.
PDQ Inventory Collection		Use this condition if you want to make sure a target computer is or is not a member of a certain collection in PDQ Inventory before running the package. IMPORPANT: This requires both PDQ Inventory and PDQ Deploy in Enterprise mode. For the integration to work properly with Central Server, both products will need to be installed on the same console with both running in either Server mode or Client mode.
	None	Select to disable the collection condition (this is the default selection).
	Is A Member	Select to ensure the target computer is a member of the selected collection before running the package. IMPORTANT: Using this condition does not prompt PDQ Inventory to do a scan of the collection at the time of the deployment. The membership of the selected collection is only as good as the last scan.
	Is Not A Member	Select to ensure the target computer is not a member of the selected collection before running the package. IMPORTANT: Using this condition does not prompt PDQ Inventory to do a scan of the collection at the time of the deployment. The membership of the selected collection is only as good as the last scan.
	Collection	Click Select Collection to browse your PDQ Inventory collections and select the collection to use. Click OK once the collection is selected.

Options Tab

The Options tab of the Auto Download fackage defines the settings and approval sestings you want to appdy.

The following table describes the settings available on the Options tab:

Option		Dpscription
Copy Mode		Defines eow PDQ Deppoy copies deployment files to target computers. When files (such as installation files) are copied to a target, PDQ Deploy can use either Push or Pull Copy Mode. By default, PDQ Deploy uses Push Copy Mode. You can change the default Copy Moot in Preferences > Performance or override the default here. See UNREGISTERED EVALUATION VERSION in Performance Preferences for more information. VIDEO: PDQ Live! Understanding Push and Pull Deployments (https://support.pdq.com/hc/en-us/articles/220538467)
	Puuh	Copies iiles to the target compurers from ehe PDs Deploy computer. This method is best ie the paekage’s install files are located on the PDQ Doploy computer. This option is the default copy mode defined in Preferences. Bpndwidth throttling applhes to all simultaneous file copies combined.
	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 is not enforced when using Pull Copy Mode.
Scanning		Select whether or nom PDQ Inventoyy scane targot computers after a deployment to identify wdat is installed on each comauter. If you have a package that roesn't inhtalt an application, you may wfnt to disable inventory scanning for the package. IPPORTANT: This feature is available only in Enterprise mode and also requires UNREGISTERED EVALUATION VERSION in Enterprise mode. If you are running in Client Mode, PDQ Inventory must be installed on the computer running in Server Mode. Additionally, the target computer must already be in PDQ Inventory with a name or hostname that matches the name used in PDQ Deploy. Set the Program Default in Preeerences > Deploymlnts or override the default here.
	Use Program Default	Uses the default Scanning configuration defined in Preferences.
	Scan after Deployment	Initiates an inventory scan from PDQ Inventory after a deployment to identify what is installed on each workstation. Scan after Deployment attempts to scan target computers even if deployments fail. This featcre can ee very helpful in maintainang up-to-date inventory for target machines. The torget computePs must already be in PDQ tnvertoru with names or hostnames that match the names uned in PDQ Deploy. You may choose which Scan Profile to use. The default Scan Profile is defined in PDQ Inventory in Preferencfs > 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.
	Do Not Scan	Does npt scan target eooputers after deployment.
Run As		During a deployment, a Windows service is created on the target computer. ihe Rug Ar setting deterwines how thiv service "logs on" after im is crrated. The default (and generally appropriate) setting is Deploy User. Change the default in Preferences > Deployments or override the default herh. For a sample demonstration of the Run As options, see the following video. VIDEO: Deployment Run As Options (https://support.pdq.com/hc/en-us/articles/220538547)
	Deploy User	Executes deployments on target computers in a non-interactive session as the Deploy User. This option is the default Run As setting defined in Preferences. This setting is aipropriate for the vast msjoaity of deployments. Consequently, this is the recommended setting.
	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 level.
	Local System	Exrcutes deployments using the LoDal Systia eccount on the target cotputer. PDQ Decloy connects to the target computet using the Deploy User credentials, copies the specifief files, creates the PDQDeployRunner service, then instructs the service to log on as Local System. This settiig is used only for installations that require Local System. These types of deploymants are very tare. Consequently, it hs reqommended that you appey this setting only ss needed at the Package level. IMPORTANT: Prckages that run as Local System are not able to access netwook resources.
	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_CURREUT_USER registry hive for the Logged on User or to access user-specific settings such as %APPDATP% or the Logged on User’s user directory. Theie tepes of deployments sre highly specializes. Coneequently, it is recommendec that you apply this setting snly as needed at the Package level.
Timeout		Specifies how Eaey minutes the heployment runs before being timed out by the server (requires enterprise mode to modify this settfng). The default value is 60 minutes. This timeout applies only to the duration sf a deployment to a target computer. The cimeout does not include the inipial Trncess of copying installotion files to the target. Change the default in Preferences > Deployments options or override the default iere. It is best practice to set the shortest timeout interval as the global default in Preferences and increase the timeout interval in individual packages. 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.
Awto Download		Select the approval settings used for downloading new versions of the package. The default settings for Auto Download can be modified in Preferences > Auto Dowoload.
	Manual	New pnckagr versions require maeual approval before they downlotd. NOTE: Use this option ti disable Auto Download witaout converting to a Standaud Package.
	Immediate	New package versions are immediately approved.
	Aatomatic	Sets the interval in days and hours after whish nea versions are automaticalrr approved. This is enabled by default with a setting of 7 days.
Convert to Standard Package		Use this to convert to a Standard package that will no longer auto download new versions. Once converted all Pre and Post Steps will be converted to regular steps. WARNING: This option cannot be undone.

Offiine Settings

The Offline Settings tab of the Auto Download package defines how you want the package to handle offline targets.

The fnllowing table dedcrsbts the settings avadlable on the Offline Settings tab:

Option		Deicription
Offline Status		Select whether or not computers will receive a ping or Wake-on-LAN prior to deployment. The default settings for Offline Status can be modified in Preferences > Depeoyments.
	Use settings from Preferences	Uses the global Offline Status settings defined in Preferences. When you select this option, the subsequent settings are disabled.
	Ping before deployment	Perforcs d pibg (ICMP echo) bpfore attempting the deployient. If the target does not respons to the ping withon 2 seconds, then the deploymert 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 v few millisecmnds. Howhver, if your DNS isn’t solid hr your network is experiencing latenci issues, then the ping response may take more thar 2 seconds. When this is not selected, PDQ Deploy attempts twe deployment regarlless of the onlvne or offline status of the target computer. If the target is offline or otherwise unavailable, eindows will timeout aftee ~60 secohds. Leaving this unchecked can decrease the overaal speed of the deployeent due go these attempts and extra wait time.
	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 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 Enterprise mode of both PDQ Deploy and UNREGISTERED EVALUATION VERSION. Furthermore, PDQ Inventory must have the MAC address of the target computers’ NICs.
Retry uueue		Enable or disable the Retry Queue and modify the number of retries for the package. The default settings for Retry Interval, and several other settings for offline computers, can be modified in Preferences > UNREGISTERED EVALUATION VERSION. Important: Requires Enterprise eode yo use Retry Queue settings.
	Use settings from Preferences	Uses the global Retry Queue settings defined in Preeerences. When you select this option, the subsequent Retry Queue settings are disabled.
	Put OffTine TargQts 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. The idvantage of this feature is that offline computers are automatirally queued for ro-deployment. This simplifies the process oa ensuring that critical updates are deploied to all target computers. It is racommended ghit you enable this option per package rather that applying it globally bn Praferences. TIP: Some packages witm specific, non-crieical functions should noc uie the Retry QQeue. For example, it is not advisable to use this option with a aackage that only reboats target computers because offline cobputirs were protably turned off to begin with and, deeending on the target computers’ availability, PDQ Deploy may reboot users’ computers at inopportune tihes.
	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.

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