Use this condition if you want to check for files on the target computer before running the package.įor example, using the File Exists condition: Run only if Chrome.exe version is greater than 50 and product name equals Google Chrome.įor real life examples of deploying using File or Registry conditions, see the following webcast. Only run the package if a user is logged on, including locked and disconnected sessions. Only run if a user is logged on (including Locked and Disconnected) Only run the package if no users are logged on. Run the package regardless of logged on state. IMPORTANT: PowerShell version 1 is not supported in PDQ Deployĭetermines whether or not the package runs, based on whether or not a user is logged on to the target computer. (This condition will only appear on the Install and PowerShell steps) Select the version or versions of PowerShell for which the package will be applied. Select the version or versions of Windows for which the package will be applied.Ĭhoose whether the package is to run on 32-bit, 64-bit, or both operating system architectures. The following table provides information on the Deployment settings available in the Conditions tab: The conditions W hen finished, click on the Options or Offline Settings tabs. Click the Conditions tab to define the conditions that must exist for the current package to run. Provide a description with additional, relevant details about the package.įor additional guidance, look at package descriptions in the Package Library.ĥ. NOTE: Unavailable for an Auto Download package. This field is primarily used for packages in the Package Library but you are free to use it for custom packages. In order to have the version number display properly in the tree properly, leave a space between the new name and the version number. For example, the package 'Adobe Reader DC 17.012.20098', can be changed to 'CEO Reader 17.012.20098'. IMPORTANT: For an Auto Download package, in order for the package to display the most up-to-date version number in the tree of the main console, do not change or delete the version number in the Name field. For additional naming guidance, look at how packages in the Package Library are named. Use a package name that includes the product, version, and other important information such as architecture (for example, 32 or 64-bit).
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |