Add the ability to verify a file/directory does NOT exist while scripting tasks.
In the verify stage of scripting tasks, you can check if a file/directory does exist, but there is no option to verify that they do not. By providing this feature, it would be easier to deploy based on trigger files instead of always relying on the registry.

-
Steve commented
So after 5 years we still don't have this as an option?
-
Anonymous commented
what I have done in the meantime is have it check that a process or service is NOT running that would be running if the installation was already in place. if the service is NOT running the install will begin but it is more fool proof if I could just have it check to see if the directory or a file does not exist instead.
-
Anonymous commented
This is still not available! Seems so obvious to me!
-
Christopher Allinson commented
Why is this not a been added yet? Seems to be a simple request to fulfill.
-
Mark Johnson commented
I had asked for this years ago even before DELL bought out KACE.
-
Mark Johnson commented
This is needed to see if a program should be run when its associated program file is NOT found. Without this, the program would run each time the script is run and that is not needed.
-
Andy Xie commented
I'm surprised this little small request still haven't been implemented yet.
-
Anonymous commented
I agreed. It would be more interesting if at least "Remediation" task have same parameters just like "Verify" so it will work like real IF IFELSE. Other wise we have to make multiple main task to catch different scenarios.
-
Jonathan VanLeuvan commented
This would be great Otherwise I have to use
Launch “$(KACE_SYS_DIR)\cmd.exe” with params “/c If EXIST $(KACE_DEPENDENCY_DIR)\someFile exit 16" to Fail if exists.A more general option for the Varify section would be a "NOT" checkbox for each step to "inverse" the logic