I have 5 deletes in a row for files in the same folder and I have seen it fail on the 4th and the 5th file. The action fails on Windows 2000 Server, Windows Server 2003 32 bit and 64 bit, but not all the time. If I stop/start besclient it pretty consistently will work without failing. I have used Procexp.exe to check for locks on the files prior to issuing the action and even scheduled the action to begin at a certain time, so I could check just prior to action start time and no locks found.
We are running besclient Product Version is 8.0.627.0. Thanks for feedback.
The file has not been created earlier in the action. The action runs once a day under a policy. I made a custom copy of the task the action comes from to test some changes to the action (the 5 file deletes remain the same as from the original), but even the original task action failed for a coworker when they executed separate from the policy.
I am under the impression that BigFix is single threaded and shouldn’t be executing any other content while an action is running. Is that a correct assumption? No process outside of BigFix should be accessing those group of files with possible exception of AV and I believe we exclude BigFix Enterprise for AV, checking.