|
<< Click to Display Table of Contents >> Types of Deployments |
There are several different ways to deploy packages with PDQ Deploy. You can deploy immediately (manual), schedule deployments for later or at specified intervals, schedule auto deployments for updated packages from the Package Library, or create deployments to deal with offline computers.
There are several PDQ Deploy features that you can use to handle deployments to target computers that are offline: Heartbeat schedules, the Retry Queue, and the Wake-on-LAN option.
The following topics provide brief descriptions for each type of deployment and links to the sections that describe each in detail.
Use Deploy Once to manually deploy a single package immediately. This is the only deployment method available for PDQ Deploy in free mode.
Scheduled Deployment is the method you’ll use for most of your deployments. (Pro or Enterprise mode required.) PDQ Deploy schedules allow you to deploy one or more packages once at a specified time, or multiple times at specified intervals in the future.
Auto Deployment is a type of scheduled deployment that allows you to automatically deploy new versions of packages as they become available in the PDQ Deploy Package Library. (Enterprise mode required.)
Heartbeat is a PDQ Deploy schedule trigger that deploys packages to target computers when their status changes from offline to online. (Requires PDQ Deploy and PDQ Inventory in Pro or Enterprise mode.)
Target computers that are offline during a deployment can be automatically placed in the Retry Queue. (Enterprise mode required.) PDQ Deploy retries deployments to computers in the queue according to your settings.
You can use the Wake-on-LAN (WOL) option to start up offline target computers before deployments. (Pro or Enterprise mode required.)
© 2015 Admin Arsenal, Inc. All rights reserved.
Admin Arsenal is a trademark of Admin Arsenal, Inc. All other product and company names are the property of their respective owners.
Help Version: 7.0.4.0