Client Upgrades to v11.03 not reporting as relevant

We recently upgraded our BigFix environment from v10.0.12 to v11.0.3 on Windows. After the upgrade, I set up a policy action to deploy the latest v11.0.3 clients/agents across our environment. However, we’ve encountered an issue where only about 40% of the machines have successfully upgraded, while the remaining 60% do not find the v11.0.3 agent as relevant and therefore do not initiate the upgrade.

To troubleshoot, I upgraded most of the machines running older agents (some were upgraded to v10.0.13), but they still don’t recognize v11.0.3 as relevant. Here are the versions of the machines that haven’t found v11.0.3 relevant:

  • 10.0.0.133
  • 10.0.3.66
  • 10.0.6.66
  • 10.0.7.52
  • 10.0.8.37
  • 10.0.9.21
  • 10.0.10.46
  • 10.0.11.108
  • 10.0.12.60
  • 10.0.13.93

These machines run various OS versions including Windows Server 2012 R2 to Windows Server 2022, as well as Linux distributions such as Amazon Linux, Ubuntu, RHEL, Oracle Linux, and Debian.

Could this issue be related to TLS/SHA1 compatibility, or has anyone else encountered a similar problem during their upgrades? Any insights or suggestions would be greatly appreciated!

Thank you in advance for your help.

Have a look at some clients log for errors (especially sync errors). I suppose all relays are already at 11.0.3, doesn’t they?
In addition, some OS may be no longer supported by v11: Knowledge Article View HCL - Customer Support

The agents have to detect that their relay is 11.0 or higher, among other tests. @DanieleColi question is pertinent.

Yes, I found one relay that wasn’t updated to v11; upgraded that and then the policy action immediately added the remaining objects as relevant. That said though, there were other objects using the same relay that upgraded to v11.0.3 already.

Also, I’m assuming Windows Server 2012 and 2012 R2 can only go up to version v10.0.13 as none of them upgraded to v11.0.3. Right?

Thats correct !

BigFix 10 - Detailed System Requirements

2 Likes