Creating Deployment Schedules

Creating a New Schedule

Schedules in PDQ Deploy allow you to automate package deployments, according to the defined triggers.

To create a new Schedule in PDQ Deploy, perform any one of the following actions:

• Select New Schedule in the toolbar.
• Select File > New Schedule from the menu.
• Right click a package, or multiple selected packages, and select New Schedule.
• Select Deploy > New Schedule in the selected package page.
• Select New Schedule from the All Schedules page.
• With multiple packages, select Create new schedule with these packages from the Multiple Packages Page.

Note: Don't forget to name your schedules. Un-named schedules will save with an empty name, making it difficult to distinguish between schedules in the All Schedules page.

Triggers Tab

Schedule Triggers define when the schedule runs. Schedules can be configured with multiple triggers.

Schedule Triggers Properties

Once - The Schedule will automatically run once, at the configured date & time

The Once Trigger contains the following options:

• Trigger On - Set the date & time for the Schedule to run once

Interval - The Schedule will automatically run according to the configured interval

The Interval Trigger contains the following options:

• Every d/h/m - Configure the day/hour/minute intervals that you wish for the Schedule to run
• Only run during the following time frame - When checked, the Schedule will run during the time set here
• Starting / Ending dates & times - Configure the Starting & optional Ending times for the Schedule
• The Starting date & time is the first time the Schedule will run
• When the optional Ending date & time is checked, the Schedule will stop running once the configured date & time has passed

Daily - The Schedule will run every day at the configured time

The Daily Trigger contains the following options:

• Every Day At - Configure the time that the Schedule should run every day
• Starting / Ending dates- Configure the Starting and optional Ending dates for the Schedule
  • The Starting date is the first date the Schedule will run
  • The Ending date (Optional) is the last date the Schedule will run

Weekly - The Schedule will run every week on the configured days and times

The Weekly Trigger contains the following options:

• Every Week On - Configure the days & times that you wish for the Schedule to run every week (multiple selections allowed)
• Starting / Ending dates- Configure the Starting and optional Ending times for the Schedule
  • The Starting time is the first time the Schedule will run
  • The Ending date (Optional) is the last date the Schedule will run

Monthly - The Schedule will run every month on the configured days and times

The Monthly Trigger contains the following options:

• Every Month - Configure the days of the month and the time for the Schedule to run every Month
• Day of Month - Configure the date (or dates) of the month and time for the Schedule to run (multiple selections allowed)
• Day of Week - Configure the Schedule to run on the nth day of the month (multiple selections allowed)
  • For example:
    • The 1st & 3rd Monday of the Month
    • The Last Friday of the Month
    • The second Tuesday of the Month
• Starting / Ending dates- Configure the Starting and optional Ending times for the Schedule
  • The Starting time is the first time the Schedule will run
  • The Ending date (Optional) is the last date the Schedule will run

Heartbeat - Runs the Schedule against target computers when their status changes from Offline to Online in PDQ Inventory.

• Only run during the following time frame - (Optional) Configure the times of the day for the Heartbeat Trigger to run the Schedule. Heartbeats detected outside of the configured time-frame will not receive the deployment.
  • If the 'Between' time is set after the 'And' time, the trigger will run overnight.
• Starting / Ending dates- Configure the Starting and optional Ending times for the Schedule.
  • The Starting time is the first time the Schedule will run.
  • The Ending date (Optional) is the last date the Schedule will run.

Targets Tab

The Targets tab is where the target computers are selected for a Schedule.

Type a computer name in the Enter Computer Name field, and select Add Computer to add an individual computer to the Schedule. Multiple computers can be added, by entering multiple computer names, with this method.

Select Choose Targets to open a menu with options for selecting one or more computers. Each dropdown has options for selecting multiple or individual computers from target sources.

Targeting Computers in a Target Source

• Choose Targets:
  • Active Directory > Container - Select Active Directory Containers or Groups.
  • PDQ Inventory > Collection - Select a PDQ Inventory Collection.
  • Spiceworks > Group - Select Spiceworks Groups.
  • Target List > List - Select a PDQ Deploy Target List.

Targeting Individual Computers from a Target Source

• Choose Targets:
  • Active Directory > Computers - Select individual computers from Active Directory Containers or Groups.
  • PDQ Inventory > Computers - Select individual computers from PDQ Inventory Collections.
  • Spiceworks > Computers - Select individual computers from Spiceworks Groups.
  • Target List > Computers - Select individual computers from a PDQ Deploy Target List.
  • Text File - Select a text file containing a list of target computer names.

Packages Tab

The Packages tab is where packages are attached to a Schedule.

Select Attach to display a menu of the packages in PDQ Deploy, and choose one or more packages from the list.

Highlight one, or more, packages from the package list and select Detach to remove package(s) from a Schedule.

Highlight a package and select the Up or Down arrow button to change the order the schedule will apply the package. When the Schedule runs, packages are applied from top to bottom of this list.

Options Tab

The Options tab in a Schedule allows you to configure some deployment and performance settings that will override what is configured in Options > Preferences as well as the same options for individual packages. 

Any un-defined option on this page will default to (use package setting) (varies). Leaving these options un-defined in the Schedule will use the settings configured in the attached package(s).

Schedule Options Properties

• Schedule Enabled - When checked, the Schedule is enabled. Uncheck this option to disable the Schedule and prevent it from running. Schedules can be enabled or disabled at anytime.
• Credentials - Select the Deploy User Credentials for the Schedule's deployment(s).
  • Edit Credentials - If the Deploy User you wish to use has not yet been configured in Options > Credentials. Select this button to add or remove Deploy Users without leaving the Schedule.
  • Use PDQ Inventory Scan User credentials first, when available - When checked, the deployment will attempt to use the PDQ Inventory Scan User's credentials, and will fall back to using the Deploy User account if unsuccessful.
    • If you are using LAPS, and PDQ Inventory's LAPS integration, select this option to use the LAPS User configured in PDQ Inventory.
• Copy Mode - Determine how the required package files are copied to the targets
  
  • Push - The Background Service copies the package files from the repository straight to the target computers
    • If the repository does not reside on the same server that PDQ Deploy is installed on, the files will first be copied to the PDQ server and then pushed to the target computers.
  • Pull - The PDQ Deploy Runner Service on the target computers will retrieve the package files from the repository directly.
    • This method is best for situations where the package files are not hosted on the same server as PDQ Deploy.
• Scanning - Determine if PDQ Inventory should scan the target computers after the deployment, and which Scan Profile to use.
  
  • Because most deployments are installing or updating applications, it is recommended to use a lightweight Scan Profile (e.g. the pre-configured Applications Scan Profile) for most post-deployment scans.
• Run As - Determine the user this package (or step) will Run As.
  • This Option is also available in the Options tab of each step. Setting this option per-step will override the Package setting.
  • The Run As options are:
    • Deploy User (Program Default) - The Default Deploy User, configured in Options > Credentials
    • Deploy User - Selecting this option allows you to select which Deploy User to use for the package. Click on the preferences button to the right of the drop-down to open the Deploy Users menu.
    • Deploy User (Interactive) - Allows for executing deployments that include both silent and interactive steps.
      • The difference between this setting and the Deploy User setting is that the Windows process running the deployment is ran in an interactive session.
      • This setting will use more processing resources on the target computer and is only recommended to use as-needed at the individual package level.
    • Local System - The deployment is ran as 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 level.
      • Packages using this setting cannot access network resources.
    • Logged on User - The PDQ Deploy Runner Service attempts to run the package as the currently logged on user.
      • 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 level.
• Notifications - (Optional) Configure email notifications for the deployment.
  • The Post Deployment Notification will send an email after each completed deployment.
  • The Post Schedule Notification will send one email for the completed schedule and all the included deployment(s).
  • You must configure the Mail Server settings in Preferences as well as designate at least one email recipient in the selected Post Deployment Notification or Post Schedule Notification before you can enable this option.
• Stop deploying to targets once they succeed - Stop deploying to targets that have successfully received this package.
  
  • Because Auto Download Packages clear the Target History of the Schedules they are attached to when updated, it is safe to leave this option enabled for Schedules with Auto Download Packages.
• Stop deploying to targets if they fail _ times - Stops deploying to target computers once they fail the designated number of times.
• Stop deploying to remaining queued targets after _ minutes - Stops deploying and aborts all remaining target computers after the designated number of minutes. Any targets that are running when the timeout elapses will complete their deployment.
  • This option is useful for overnight deployments so queued targets can be stopped before anyone arrives in the office.

Offline Settings Tab

The Offline Settings tab in a Schedule determines how the Schedule will handle offline targets.

Settings configured in a Schedule's Offline tab will overwrite the global Offline settings as well as the per-package Offline Settings.

Offline Settings Tab Properties:

• Offline Status - Configure how PDQ Deploy determines a targets online / offline status before attempting the deployment. If Use settings from package(s) is selected, each package's Offline Settings will be applied as the package is deployed from the Schedule. If unchecked, the below settings will become available. 
  
  • Ping before deployment - Performs a ping (ICMP echo) to all addresses returned by DNS before attempting the deployment on the first to respond. If the target does not respond to the ping within 2 seconds, then the deployment is not attempted on that target.
    • When this is not selected, PDQ Deploy attempts the deployment regardless of the online or offline status of the target computer.
  • 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.
    • In order for this option to work, PDQ Inventory must have the MAC address of the target computers' NICs.
• Retry Queue - Determine whether or not to place offline targets into the Retry Queue. If Use settings from package(s) is selected, each package's Retry Queue setting will be applied as the package is deployed from the Schedule. If unchecked, the below setting will become available.
  • Put offline targets in Retry Queue - When selected, the offline targets will be placed into the Retry Queue, and the deployment will retry, according to the Allowed Retries setting.
  • Allowed Retries - How many times PDQ Deploy will attempt to retry the deployment to the offline targets.

Target History Tab

The Target History tab in a Schedule displays the targets the Schedule has ran against. The Target History tab will list each target, the package that was ran, and if it was successful or failed. One, or more, targets can be removed manually from the Target History tab by highlighting the target and selecting Delete. Selecting Delete from All Schedules will remove the selected target(s) from the Target History of all Schedules.

Note: Deployment history will not be affected by deleting targets from the Target History tab.

Manually Running a Schedule

PDQ Deploy Schedules can be manually ran, if you need to run a Schedule one time outside of the defined Schedule Triggers.

All Attached Packages

Right Click any Schedule in the All Schedules page, and select Start Schedule > All Attached Packages.

Individual Attached Packages

To run a single package from a Schedule, right click the Schedule an select Start Schedule > Select the package from the list.

Enabling / Disabling a Schedule

Schedules can be quickly enabled or disabled. Disabling a Schedule will prevent it from running, without having to delete the Schedule and losing your settings.

To enable or disable a Schedule:

• In the Options tab of a Schedule, select Schedule Enabled to enable the Schedule
• In the Options tab of a Schedule, de-select the Schedule Enabled checkbox to disable the Schedule.
• In the All Schedules page, right click an enabled Schedule and select Disable to disable the Schedule.
• In the All Schedules page, right click a disabled Schedule and select Enable to enable the Schedule.