Task relevance to match condition; file does NOT exist

Content Authoring
1

(imported topic written by SystemAdmin)

Hello, I need to create a (custom) Software Distribution task that will be relevant if a particular file does

not

exist on the endpoint.

Example:

Systems Lifecycle - Software Distribution Tasks

Edit a task, choose the Relevance tab, then Relevance Expression, choose Is False, then Edit Relevance;

(exists file “C:\Packages\ThisIsAFlagFile01.log”)

So, if ‘ThisIsAFlagFile01.log’ file doesn’t exist, then the endpoint should be relevant for this task.

A simpler example would be install Photoshop8 if ‘C:\Flags\photoshop8.txt’

doesn’t

exist.

Is this possible? If so what is the proper relevance?

Thanks

2

(imported comment written by Zakkus)

This happens to be super simple in relevance. In fact you almost wrote out the correct relevance in asking the question:

code

not exists file “C:\Packages\ThisIsAFlagFile01.log”

[/code]

-Zak

3

(imported comment written by SystemAdmin)

Thank you Zakkus.

I believed this to be the correct code to use, however we are showing

no

Applicable Computers for

any

Software Distribution Tasks setup like this. We do however show Applicable Computers if the relevance is set to ‘exists’ if the file exists. What isn’t working is ‘not exists’ or ‘not exist’ if the file

doesn’t

exist. Very bizarre.

There could be a larger problem or misconfiguration causing these symptoms.

I’m marking the question as answered, thanks again.

-P

4

(imported comment written by Zakkus)

There are a couple of things that could cause that.

If you just recently made the change, then you will have to wait some time for the endpoints to gather the change and report that they are applicable.

Additionally, the site you placed the new task in may be restricted to a subset of computers (or possibly no computers). Make sure all your agents are subscribed to the site you’ve placed the task in.

-Zak