(The same is true if this were a scheduled Shutdown or Reboot package). The following components must be installed: Microsoft Office Excel Microsoft Office PowerPoint Visual Basic for Applications (from Office Shared Features). To prevent this manual removal, make sure that box is not checked. Those computers will not be deployed to again until that record is removed. The only con I can identify is, that we have to take time to learn some aspects of the functionality. If this box is checked and the schedule runs, all computers that succeeded will be put into the Computer History tab. I MPORTANT: In the Options tab of the schedule there is a checkbox to “Stop deploying to computers once they succeed”. Create a schedule for the “dir” package that meets your requirements (for example, wake computers first thing in the morning or wake computers for a maintenance window after hours). Create a package in Deploy that will have an inert effect on the target machine like a “dir” command:ģ. If you would prefer not to set this globally it can also be set at the package level by going to the package properties "Offline Settings" tab to only be enabled for a specific package.Ģ. Once set, your deployment packages will all attempt to wake offline machines. NOTE: This is a global setting and will affect all deployments. In the Offline Status section, enable “Use Ping for Offline Testing” and “Send Wake-on-LAN to Offline Computers”. In PDQ Deploy, go to Options > Preferences > Deployments. If youre not already using a configuration management tool, definitely take a look at Ansible. It has reduced the time spent on deployments, standardized our configuration, reduced human errors, maintains our documentation, and so much more. You want PDQ Deploy to wake computers at a specific time for example, to run updates or deploy packages (requires Pro or Enterprise license for PDQ Deploy and PDQ Inventory).ġ. Ansible has revolutionized the way we do things.
0 kommentar(er)
