On two different workstations, one x86 and the other x64, I receive different results for this relevance clause:
names of files of folder "C:\Windows\system32\tasks"
On the x86 box, I get an accurate list of all files in the folder. On the x64 box, the relevance returns no results, even though there are definitely files in there. I tried running the relevance debugger as SYSTEM (using psexec) and changing the folder permissions, but the relevance debugger still didn’t return anything. I tried both the 8.0 and 7.2.5.22 versions of the debugger.
My guess is this looks to be the result of 64-bit redirection since BigFix is 32-bit. So when you run that expression, it’s actually checking “C:\Windows\SysWOW64\tasks” instead. You’ll want to branch on x64 of operating system maybe or if it’s going to be in action play with “action uses wow64 redirection”.
Looks like you’ll want to use the ‘system x64 folder’ to access the ‘system32’ folder.
My guess is this looks to be the result of 64-bit redirection since BigFix is 32-bit. So when you run that expression, it’s actually checking “C:\Windows\SysWOW64\tasks” instead. You’ll want to branch on x64 of operating system maybe or if it’s going to be in action play with “action uses wow64 redirection”.
You’re right! I’ve dealt with x64 vs x86 a million times with the registry inspectors, but this is the first time I’ve run into it with the file inspectors. Doh! Here’s the x64 relevance that I used:
names of files of x64 folder "C:\Windows\System32\Tasks"