Well, I am still scratching my head over this. It looks like another ‘determining factor’ is that the machine was unkown to BigFix (no BigFix agent installed) when the policy was created.
The following relevance statement is automatically created when you publish and specify ‘Run Command As Current User (Windows Only)’:
(if(name of operating system as lowercase starts with “win”) then exists logged on users else true)
In addition to the above, I have a relevance checking for a footprint file:
not exists file (“C:\Users” & (name of logged on user whose (active of it = True)) & “\AppData\Local\BigFix\FootPrint.txt”)
And finally, I also check the condition requiring a user to be logged on in the ‘Users’ tab.
I have not let the tests run for more than maybe 30 minutes, but the tests have been run in a controlled VM based environment. I have also seen this problem in a production environment (policy not executed on machines that were built after policy created).