I have deployed updates from Win10 to Win11 24H2 using fixlet 1111923 Windows 11 Business Editions Version 24H2 Available - Windows 11 (x64) (English (United States). All relevance criteria were met so the content was downloaded and the installer process (setup.exe) run. However, there were compatibility holds caused by old drivers, so the process failed.
The action in BigFix went into status “Fixed”, so we investigated setuperr.log and setupact.log and fixed the underlying issue. However, the fixlet still shows this machine as “Fixed” even when creating a new action for the same.
The client log shows it as “Not relevant”, but does not mention why due to low level of detail in these logs.
The action was created with unlimited reapplications should it become relevant again, which is what we want as BigFix did NOT detect that the installer actually failed. So why is it not seeing at all, that the process failed and why is it not automatically retrying after the issue was fixed by us manually?
thanks for the reply. This machine is still on 19045 as per winver and registry. Any way to increase the log level client-side? Console says on that action
The action executed successfully.
This action has been applied 1 time.
This action has been retried 1 time.
Status
Fixed
Start Time
5/14/2025 11:00:26 PM
End Time
5/14/2025 11:05:53 PM
Exit Code
0
No later status message is shown although the machine has been restarted multiple times
You can enable debug logging using Task 157: BES Client Setting: Enable Debug Logging. Use 10000 in the Action Parameter dialog when you take action on the Task. The resulting file will be named “besclientdebug.log” and located in the same folder as the BES Client.
Be sure to disable the logging when you’ve finished your troubleshooting using Task 196, which will be applicable on this machine.