![]() ![]() For more information, see Cleanup settings in Deployments Preferences. To view the All Deployments page, on the Main Console window, select All Deployments in the tree. The graphic below shows the All Deployments page with its components called out. The panels can be resized by clicking between them and dragging. The sidebars can be pinned open or collapsed. Click the sidebar to show or hide the details. There are two other ways to manage target computers that are offline with PDQ Deploy in addition to using Heartbeat schedules.For more information about sidebars, see Details Sidebars. You can configure PDQ Deploy to repeatedly deploy to offline target computers until they come online (Retry Queue) and/or send Wake-on-LAN (WOL) attempts before deployments. These are set globally in Preferences > Deployments but can also be set per package, per Auto Deployment, in Deploy Once, or per Schedule. Target computers that are offline during a deployment can be automatically placed in the Retry Queue. (Requires Enterprise mode.) PDQ Deploy retries deployments to computers in the queue according to your settings. You can use Wake-on-LAN (WOL) to start up offline target computers before deployments. (Requires Enterprise mode in both PDQ Deploy and PDQ Inventory.) PDQ Deploy attempts the deployment and sends a WOL packet to the target computer. The deployment waits for the target computer to come online and then deploys. ![]() If the computer does not come online within 5 minutes, PDQ Deploy attempts the deployment. ![]() ![]() NOTE: The Wake-on-LAN setting requires PDQ Inventory in Enterprise mode be installed and has scanned and captured the MAC addresses of your target computers. This section contains the following topics: For more information about PDQ Inventory, see our website at.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |