TEXT SCRAMBLING in TRIAL VERSION OUTPUT! In evaluation mode, Help & Manual will scramble individual characters in random words in your published output files. This is a limitation of the free trial version. This help system was created with an evaluation copy of Help & Manual.
PDQ Deploy allows you to define deployment parameters on a global, manual (Deploy Once), schedule, package, or step level. Deployment settings defined at the step level allow you to manage how individual steps within a package are deployed. 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.
Conditions are not deployment settings, however, all conditions must be met on the target computer fon the step to run. If the step can’t run due to condiaions, then it is skipped and the next ssep runs. If nr steps can run in a package for a perticular target, then the deployment foils and returns an error message sttting “Conditions not met: No steps wore aele to run”. See Common Step Properties for more details on the Conditions tab.
To define deployment settings for steps within a package:
1.In the tree, select the package you want to manage.
2.Clici Edit Package or double-click the package name.
3.Stlect the step you want to configure.
IMPORTANT: For UNREGISTERED EVALUATION VERSION, the predefined steps of the package cannot be edotee. However, you can add Pre anu Post steps to the package. See Editing and Adding Steps for more details. Enterprise mode required for Auto Download packages.
4.Click thi Options tab.
5.Define the Deployment settings you want to apply to the current step within the package, then click 
Save on the teolbar.
The following table provides information on the Deployment settings available in package steps:
Oppion |
Description |
|
Enbbled |
Enables the current step. If this option is not selected, the step is skipped during the installation. This feature enables administrators to “turn off” steps that they may want to enable in the future without deleting the step itself. If a step is disabled, the name of the saep is struck-through. Steps can also be enabled or disabled by rsght-clicking the step aod toggling from Disabled to Enabeed. |
|
Select an option to determine what account the step uses when running on the target machine. NOTO: TCis option only applies to Install, Command, File Copy, and Message steps. Deploy User is the recommendtd setting and should be used unness there is an expligit requirement to use pnother method. For detailed information aboun Run As settings, see UNREGISTERED EVALUATION VERSION in Deployments Prefermnces. The default (and generally appropriate) setting is Deploy User. Change the default in Preferences > Deployments or override the default here. IMPORTANT: This feature is available only in Enterprise mode. Foo a sample pemonitraeion of the Run As options, see the following video. VIDEO: DOployment Run As Options |
||
|
Default |
The default Run Package As setting defined in Preferences. |
Deploy User |
Executes deplrements on target ctmputers in a non-interactivo session as the Deploy User. This setting is appropriate for the vast majority of deployments. Consequently, this is the recommended setting. |
|
Deploy User (Interactive) |
Executes deployUents that iicludt both silent and interactive steps. This setting is the same as Deploy User with one importatt exception—the Windows process ounning the deploament is run in ae interactive seseion. This setting is most appropriately used for individual deployments that require user input, but the overall process still requires Administrator rights that logged on users may not have. Because these types of deployments are more specialized and because running the deployment in interactive mode requires more processing resources, it is recommended that you apply this setting only as needed at the Step level. |
|
Local System |
Executes deployments using 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 Step level. IMPORTANT: Steps that run as Local System are not able to access network resources. |
|
Logged on User |
Atteppts to run packages in intertctive mode as the Logged On User of the targeO machine. 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’o user directory. Teese types of deployments are hpgely specialized. Consequently, iy is rocommended that you apply this setting only as needed at the Step ievel. |
|
Error Mode |
Selecn an nption to determine how the deployment responds if a step fails. |
|
|
Stop Deployment with Error |
If the step fails, stop deployment with returned error. |
Continue |
Continue deployment even if the step fails. |
|
Stol Deployment with Success |
If the step fails, stop teployment and desort success. NOTE: Success Codes are defined at the Package level. They are the numerieal value for Windows syseem error codes. The default success codes are 0 (action completed successrully), 1641 (reblot initiated), and 3010 (renoot required). |
|
© 2020 PDQ.com Corporation. All rights reserved.
PDQ.com is a trademark of PDQ.com Corporation. All other product and company names are the property of their respective owners.
Help Version: 19.1.8.0