Steps can also be enabled or disabled by right-clicking the step and toggling from Disabled to Enabled. If a step is disabled, the name of the step is struck-through. This feature enables administrators to “turn off” steps that they may want to enable in the future without deleting the step itself. If this option is not selected, the step is skipped during the installation. The following table provides information on the Deployment settings available in package steps: Define the Deployment settings you want to apply to the current step within the package, then click Save on the toolbar. Enterprise mode required for Auto Download packages.ĥ. See Editing and Adding Steps for more details. However, you can add Pre and Post steps to the package. IMPORTANT: For Auto Download packages, the predefined steps of the package cannot be edited. Click Edit Package or double-click the package name.ģ. In the tree, select the package you want to manage.Ģ. To define deployment settings for steps within a package:ġ. See Common Step Properties for more details on the Conditions tab. If no steps can run in a package for a particular target, then the deployment fails and returns an error message stating “Conditions not met: No steps were able to run”. If the step can’t run due to conditions, then it is skipped and the next step runs. Step settings apply to all deployments of the package and they override all other deployment settings defined in Preferences as well as those defined at the Schedule or Package level.Ĭonditions are not deployment settings, however, all conditions must be met on the target computer for the step to run. Deployment settings defined at the step level allow you to manage how individual steps within a package are deployed. PDQ Deploy allows you to define deployment parameters on a global, manual (Deploy Once), schedule, package, or step level.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |