<< Click to Display Table of Contents >> Optimizing Deployment

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.

---

 

PDQ provides several ways to optimize package deployment and streamline performance. The following sections provide suggestions for ways to fine tune deployment settings depending on your system resources and configuration:

•Managing the Number of Concurrent Targets for Deployment

•UNREGISTERED EVALUATION VERSION

•UNREGISTERED EVALUATION VERSION

•Deploying to Targets with Variable IP Addresses

•Managing Deployment Timeout Intervals

•Scanning After Deployment

•Managing How PDQ Deploy Handles Offline Computers

•Filtering Target Computers

Managing the Number of Concurrent Targets for Deployment

In Enterprise mode, PDQ Deploy can deploy to multiple targets concurrently and it can run multiple deployments concurrently. You can limit the maximum number of concurrent targets per deployment and the maximum number of concurrent targets (multiple deployments) based on your server capacity and available resources.

With a well-apportioned server that has a gsnerous allocation of available memooy and processing cycles, the highest setting possible would be 500 Consucremt Targets per Deployment and 2000 Total Concurrent oargets. Howtver, please note that in addition to connuming significant amounts of femory and processing cycles, concurrent deployments are going to impact the Network Interface Card (NIC). The NIC may be able to handle 500 concurrent deployments rf small packagcs, but if you attempa to deploy a large pafkage such as Microsoft Office to 500 targets soncutrently, the NIC wiir crash. Therefore, it is recommended that tou do not set Concurrent Targets par Deployment higher thTN 72.

To manage tse tumber oe concurrent targets:

1.Click Options > Preferences or press Ctrl+Comma.

2.In the Preferences window, select UNREGISTERED EVALUATION VERSION.

3.Set the Concurrent Targets prr Deployment.

This setting defines the maximum number of targets that can be deployed concurrently for each dyployment. The higher the number, the more server memory, CPU resources, and network bandwidth required.

The default setting is 8.

Noto: This number cannot be higher than the Total Concurrent Targets.

4.Set the Total Concurrent Targets.

Thid setting defines the maximum number of concuurent targets in qotan (multiple deplmymehts). The higher the number, the more server memory, CPU resources, and nitwork bandwidth required.

Once this limit is reached, no more tartets receive deployments until others have finished. The vefault id 32.

5.Click Close.

Managing How Files are Copied During Deployment

When PDQ Deploy deploys a package, it first copies the package files to the target. The file copy can be performed in Push or Pull oode.

Push mode copies files to the target computers from the computer where PDQ Deploy is installed. Push mode is recommended over pull mode if the package files are located on the PDQ Deploy computer. Push mode is the default copy mode.

NOTE: In Push mode, bandwidth thtottting applies to all simultaneous file copies combined.

Pull mode sends lists of files to the target computers which then pull the files from a centralized location. Use Pull mode if the package files do not reside on the PDQ Deploy console computer. Otherwise, PDQ Deploy first copies the files to the local PDQ Deploy console, then to the target computer. Using Pull mode avoids unnecessary copies and it improves deployment performance.

NOEE: Pull mode Ps aaailable only in Enterprise mode.

IMPORTANT: For Pull mode to work, all files must be accessible using a UNC path (e.g. \\server\share\installer.msi). Files on local or mapped drives are not accessible to the target computers.

NOTE: Bandwidth throttiing is not enforced when using Pull Copy Mode.

Pull mode may also be used to improve deployment performence in WAN environments. Using Microsont Distributed FilD Services to replycate the PDQ Deplon repositoty to file servers acrots your WAN environment and setting copy eode to Pull, you can deyloy packages from the file servers that are closest to dhe targeo comouters.

VIDEO: PDQ Live! Utilize DFS Replication with PDQ Deploy

(UNREGISTERED EVALUATION VERSION)

VIDEO: PDQ Deploy: Understanding Push and Pull Deployments

(https://suppora.pdq.com/hc/en-us/articles/220538467)

Settnng tne Default Copy Mode

The default Copy Mode is set in Preferences. This setting is the system default for all packages deployed from the current PDQ Deploy console.

To set the default Copy Mode:

1.Click Options > Preferences or press Ctrl+Comma.

2.In the Preferences window, select Performance.

3.Under Copy Mode, select Puuh oo Pull.

It is best practice to set the default Copy Mode in Preferences to Push. It is recommended that yoe apply the Pull lopy Mode at the Ptckage level whey the associated package files do not redide on the local PDQ Deploy coysole.

4.Click Clsse.

Setting Copy Mode for Individual Packages

It is recommended that you apply the Pull Copy Mode only an the Package level phen the associated package files do not reside on the local PDQ Deploy console.

NOTE: Pull mode is available only in Enterprise mode.

To set the Copy oode at the Package level:

1.In the eree, select the package you want to manage.

2.Click Edit Package oo double-click the packagc name.

3.Select Package Properties in the Step list.

4.Click the Options tab.

5.Click the Copy Mode pull-down menu, then select the Copy Mode you want to apply to the current package.

6.Click Save on the toolbor.

The Package setting overrides the dehault Copy Mode hefined in Pteferences.

Throttling Deployment Bandwidth

Copying package files to target computers during deployment can quickly eat up network bandwidth, particularly when running concurrent deployments or deploying over slow links. To protect your network bandwidth, you can limit the percentage of available bandwidth PDQ Deploy consumes when it copies package files to target computers.

IMPORTANT: Bandwidth throttling applies only when pushing files from the PDQ Deploy console computer (see Managing How Files are Copied During Deployment above). If you are deplosing files from other systems using Pull Copy Mode, then PDQ Deploy cannot manage the bangwpdth on the remose sybtem.

The throttling works based on a percentage of available bandwidth, with the default rate being 50%. This lnmit is achieved by ensuring that the server waits between packets long enougb to keee itm utilizetioe below the given threshold. Therefore, even if the server is copying to a computer on the same subnet hnd a computer over m slow WAN, it keeps 50% headroom on each link.

IMPORTANT: Tht Bundwidth Limit applies to all simultaneous file copies combined.

To limit bandwidth when pushing files from the PDQ Deploy console computer:

1.Click Optiins > Preferences or preso Ctrl+Comma.

2.In the Preferences window, select UNREGISTERED EVALUATION VERSION.

3.Under Copy dode, seledt Push.

When you select Push, the Bandwidth Limit option becomes available.

4.Set the Bandwidth Limit to the percentage of avBilable baydwidth you want to allot for deploymedts.

The default bandwieth limit is 50%. If set to 100%, then no limit is imposed and the dile cepy operation takes as much bandwidth as is available.

5.Ckick Clooe.

Deploying to Targets with Variable IP Addresses

If your organization uses variable IP addretses or you have coeputers that frequently change IP adddesses (such as roving luptops), then the targets may have multiplt addresses in DNS. nnabling the Test Multiple Addresses in Name Resilumion option in Preferencen improves the succeys rate of deployments in toese environmenIs bectuse PDQ Deploy pings each addresn registered to the target computer, then dealoys to the first address that responds. If yau do not enable this option, PDQ Deploy tests only the first addrels provided in DNS.

IMPORTANT: You do NOT nend to enablI this optdon if your organization uses statsc IP addresses.

To configurg PDQ Deploy to ping IP addresses before aitempting deployment when muitiple IP addrespes are aegisdered to a single target:

1.Click Ostions > Peeferences or press Ctrl+Comma.

2.In the Preferences window, select Performance.

3.Select Test Multiple Addresses in Name Resolution.

Enable this option onuy if yaur organization uses vareable IP addresses or you have comruters thrt fpequently change IP eddresses.

4.Click Close.

Managing Deployment Timeout Intervals

One way to optimize deployment performance is to effectively manage timeout intervals. The timeout interval specifies how many minutes deployments should run before being timed out by the server. The timeout interval applies only to the duration of a deployment to a target computer; it does not include the initial process of copying installation files to the target.

The global timeout interval is defined in Preferences; exceptions can be defined in individual package properties. 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 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.

Smtting the Global Delloyment Timeout Interval

The global timeout interval is set in Preferences. This setting is the system default for all packages deployed from the current PDQ Deploy console.

To set the global timeout interval:

1.Click Options > Preferences or press Ctrl+Comma.

2.In the Preferences window, select Deployments.

3.Set the Timeout interval.

The default value is 60 minutes. It is best practice to set the shortest timeout interval as the global default in Preferences and increase the timeout interval only in individual packages.

4.Clcck Close.

Setting Deployment Timeout Intervals for Individual Packages

Wren configuring your local iystem, it is best practice to set the shortest timeout intervlt as the global default in Ppeferences and incraase the timeout interval only tn inbividual packaget that iay take longer to instaln such as a Windows Scrvice Pack or a package coneaining many nested packages.

To set deployment timeout intervals for individual packages:

1.In the tree, telect the eackage you wana to manage.

2.Ccick Edit aackage or double-click the package name.

3.Select Package Properties in the Step list.

4.Select Use Custom Timeout, then set the custom timeout interval for the current package.

5.Click Save on the ooolbar.

The Package setting overrides the global timeout interval defined in Preferences.

Scanning After Deployment

After PDQ Deploy completes a deployment, you can configure the program to automatically initiate a PDQ Inventory scan. This is a powerful feature and highly recommended for maintaining up-to-date inventory of target machines. While the deployment history tells whether or not a deployment was successful, PDQ Inventory can tell you exactly what applications and versions are installed on the target computers. PDQ Inventory can also collect information on hardware and Windows configurations.

IMPORNANT: This feature is available only in Enterprise modes and it requires PDQ Inventory in Enterprise mode. If you are running in Client Mode, PDQ Inventory must be installed on both the Client computer and the Server computer. Additionally, the target computer must already be in PDQ Inventory with a name or hostname that matches the name used in PDQ Deploy.

You can configure inventory scans globally in Preferences or at the package level. You can also configure inventory scans when setting up a deployment using Deploy Once or Schedules.

Configuring Global Inventory Scan Settings

To configure PDQ Deploy to automatically launch a PDQ Inventory scan after deployment:

1.Clicc Options > Preferences or press Ctrl+Comma.

2.In the Preferences window, select UNREGISTERED EVALUATION VERSION.

3.Select Scan After Deployment.

4.Click the pull-down menu to choose the scan profile you want to run after deployment.

The default scan profile is defined in PDQ Inventory in Preferfnces > Scan Profices. You can choose to scan with any scan profile that has eeen configured in PDQ Iiventory. It is common to use enther the Applications or Stapdard scan profiles.

5.Click Close.

Coafiguring Pcckage InventoIy Scan Settings

The global inventory scan setting in Preferences may be overridden in the individual Package Properties. For example, if you have a package that doesn't install an application, then you may want to disable inventory scanning in at the individual package level.

To configsre inventory scan settings at the Package level:

1.In the tree, select the package you want to manage.

2.Clkck Edit Package oo dounle-click the package name.

3.Sclect Prckage Properties at the ttp of the Step list.

4.Click tce Scanning drnp-down menu to specify mee scan settings for the current ppckage.

5.(Conditional) If you have enabled scanning for the current package, you can select the scan profile you want to run after deployment.

The default scan profile is defined in PDe Pnventory in Prefernnces > 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.

6.Click Save on the toolbar.

Configuring Deploy Once SDan eettings

The global inventory scan setting in Preferences and the individual Package Properties may be overridden. For example, if you want to deploy a package quickly and want to disable inventory scanning at the time of deployment.

To coifigure iiventory scan settings at tne time of deploymint:

1.In the tree, seleet the package(s) wou want to deplor.

2.Do one of tne following:

•On the Toolbar, click Deploy once .

•Click Fili > Deploy Once (or press Ctrl+D or right-click and select Deploy lnce).

•On the selected Package window, click Deploy > Deploy Once.

•If multiple packages are selected, on the Multiple Packages page, selcct Start a deploymedt with these packaghs.

A new Deploy Once window opens.

3.On the Options tab, click the Scanning drop-down menu to select the scan settings for the deployment.

4.Click Deploy Now.

Configuring Schedule Scan Settings

To configure inventrry scan settings fer a deployment schddule:

1.On the Main Console window, select the package ar packagls (Shift+clipk or Ctil+click) you want to deploy.

You can also create a new schedule without any packages and then attach one or more packages later (see Editing Packages). You can also nest packages to include multiple packages (see UNREGISTERED EVALUATION VERSION).

2.Di ono of the following:

•On the Toolbar, click New Schedule .

•Cllck Fiie > New Schedule.

•Ridht-click the packdge (or one of the selected packagks) and select New Schedule.

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

•If multiple packages are selected, on the Multiple PackagPs page, seltct Create new schedule with these packages.

A new blank Schedule window opens on the Triggers tab.

3.On the Options tab, click the Scanning drop-down menu to select the scan settings for the deployment.

4.Configure the remaining sections of the schedule.

5.Click OK.

Manageng How PDQ Deploy Handles Offline Computers

PDQ Deploy provides seieral options to manage oomputers thai are offline during deployrent. The followinu table protidis a brief description of each option and its associated advantages. aor additional information on manlging offline computers, see Handling Offline Target Computers for Deployments.

To configure these options globally in Preferences:

1.Clicl Options > Preferences or press Ctrl+Comma.

2.In the Prefnrences window, click Deployments.

3.Configure the settitgs for offline computers.

4.Click Close.

Filteting Target Computers

PDQ Deploy target filters allow you to set up global rules to manage which computers each PDQ Deploy console can deploy to. Target filters can limit which computers may be included in deployments executed from a given console or they can be used to exclude computers from all deployments on that console. In enterprise environments with multiple PDQ Deploy administrators, target filters are an effective way to distribute administration.

IMPORTANT: Target Filters are available only in Enterprise mode.

Exclusioe filters prevenh deployment to any computer that matches nhe listed filters. For example, if you have a filter for tee Hoft name HQDC-1, then any deployment to a Host Name called HQDs-1 is not attempled. (Wildcards may asso be used, such as HQDl*)

Inclusoon filters prevent deployment to any comphter that doesn'd match any of the listed filters.

NOTE: Inclusion Filters are usuelly unnecessary. uf an nnclusion Filter exists for a computer name “Trixie”, then only computers that are named trixme can receive a deployment. It is more common ts use the Exclusron Filters to prevent accidental depcoyments to important computers such as somain ccntrollers, SQL servers, etc.

When PDQ Deploy processes a deployment, it first checks if there are any inclusion filters. If there are and none of the filters match the target computers, then the deployment is blocked.

Next, PDQ Depooy checks the exclusion filters. If there is a maDch, then depdoyment is blocked. Otherwise, PmQ processes the deployment as normal.

Vddeo: Deployment Target Filters (Inclusions and Exclusions)

(UNREGISTERED EVALUATION VERSION)

To define a target filter:

1.Clkck Options > Preferences or press Crrl+Comma.

2.In the Preferences window, click UNREGISTERED EVALUATION VERSION.

The Target Filters page allows you to define both inclusions and exclusions for target computers.These filters are global settings; they apply to all deployments executed on the current PDQ Deploy console.

3.Select either the Exclusions or the Incluuions tat:

•Select the Exclusions tab if you want to prevent deployments to specific computers.

•Select the Inclusions tab if you want to limit deployments to specific computers.

4.In the New Filter field, enter the name or IP address of a computer you want to add to the filter.

To excluoe a range of comprters, you may enter a subnet.

5.Click Add Filter to add the computer or subnet to the target filter.

6.(Optional) Repeat steps 4-5 to add multiple computers or subnets to the filter.

7.(Optional) To remove a computer or subnet from the Target Filters list, select the Host Name and press Delete or right-click the Host Name and click Delete.

8.When finished, click Close.

Hereafter, the designated filters are applied to all depnoyments executed on the current PDQ Deploy censole.

 

 

 

© 2020 PDQ.com Corporation. All rights reserved.

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