![]() ![]() IMPORTANT: The first filename that is matched will be used. For example, the %TEMP% environment variable will evaluate to %SystemRoot%\TEMP instead of %USERPROFILE%\AppData\Local\Temp.Ĭheck to include all the sub directories of the directory above. NOTE: Environment variables will be evaluated in the context of the Local System rather than the user. This directory can include environment variables. Select to ensure there is no such existing file before running the package.Įnter the directory where the file exists on the target computer. Select to search for an existing file before running the package. Select to disable the file condition (this is the default selection). VIDEO: PDQ Live! How to Selectively Deploy Applications Using File or Registry Conditions. 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. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |