Deploying Linux Client (11.0.2.125) using Fixlet

Usage and Config
1

Hoping someone can assist.

I have an issue pushing the BES Agent to Linux PCs and Servers. I’m hitting about a 50% success rate on whether they install or not, the failing systems appear to successfully create the /var/opt/BESClient/ folder but no install log is created - under this folder there are 2 .sh files created.

The connection appears to work fine otherwise these wouldn’t have been created, but the installation doesn’t appear to run at all.

Has anyone experienced something similar that they might know a fix for this?

Thanks

2

Do you mean are you upgrading clients? Open a support ticket, so the engineer can direct to the proper logs to inspect.

3

Thanks for the reply,

This is the initial deployment of the clients - the fixlets for deploying clients says completed without an error exit code but on 50% of linux based servers/PC’s it just creates the structure, moves two shell files and does nothing else.

Thanks for the assistance

4

Are you installing clients using Cloud Plugins or CDT? In the latter case, you can look for information into the CDT logs; for cloud plugins, you should enable verbose logging and look into the cloud plugin log (or Plugin Portal log, I don’t recall exactly).

5

I’m using the CDT Fixlet - trying to track the CDT logs now to check - tbh whilst I’ve been using BigFix a number of years - I’m finally having to get a deeper understanding of how the system fully works and what it can do for our business.

this is in an air-gapped network so that brings challenges in itself.

Could you point me in the right direction of the CDT logs please?

Thanks,.

6

Here the CDT documentation pages: Troubleshooting the client deployment

7

Thanks for the assistance - I found the issue (in this case) was needing a newer agent version due to the Ubuntu 24.04 support.