Important update to 11.0 Patch 5 agents

Release Announcements Platform (Release Announcements)
1

The BigFix Platform team announces the re-release of BigFix 11.0 Patch 5 agents; the new version is v11.0.5.204. This version provides all previously announced 11.0.5 functionality and also resolves a defect identified in the original v11.0.5.203 agents:

https://support.hcl-software.com/csm?id=kb_article&sysparm_article=KB0125086

This applies to all agent operating systems.

The supported 11.0.5 environment will have v11.0.5.204 agents reporting to v11.0.5.203 relays, server and console - only the agents are being re-released.

Urgent action needed:

1. Any endpoint running v11.0.5.203 agent should be upgraded to v11.0.5.204.

To avoid that the agent upgrade action triggers the problem described in the defect article, the agent upgrade task must be run from within a baseline.

a. For each operating system that you need to target for the upgrade, create a baseline in a custom site of your choice that can be deployed to the interested endpoints

b. Add the relevant upgrade fixlet for the operating system from BES Support site to the baseline

c. Deploy the baseline to the interested endpoints

2. After a fresh installation of a 11.0.5 BigFix Root Server, or in most cases after an upgrade of the BigFix Root Server to version 11.0.5, on either Windows or Linux, the agent component on the Root Server itself must be upgraded to v11.0.5.204. For doing that, please run the same steps described in point 1. towards the BigFix Root Server computer.

Please note that this continues to apply also if you install/upgrade the server to 11.0.5 after this announcement.

3. Agent installers for Windows and RedHat that are made available on the BigFix Root Server file system are not being updated with version 204 at this time.

  • On Windows Server:
   <BESServer_inst_path>\BES Installers\Client\setup.exe

   <BESServer_inst_path>\BES Installers\ClientARM\setup.exe

   <BESServer_inst_path>\BES Installers\ClientMSI\BigFixAgent.msi

   <BESServer_inst_path>\BES Installers\ClientARMMSI\BigFixAgent.msi
  • On RedHat Server:
    /var/opt/BESInstallers/Client/BESAgent-11.0.5.203-rhe7.x86_64.rpm

    /var/opt/BESInstallers/Client/BigFix-BES-Client-11.0.5.203.exe

   /var/opt/BESInstallers/Client/BigFix-BES-Client-ARM-11.0.5.203.exe

If you need to download the latest version, you can do it at the following links:

http://software.bigfix.com/download/bes/110/BigFix-BES-Client-11.0.5.204.exe

http://software.bigfix.com/download/bes/110/BigFix-BES-Client-ARM-11.0.5.204.exe

http://software.bigfix.com/download/bes/110/BigFix-BES-ClientMSIBundle-11.0.5.204.zip

http://software.bigfix.com/download/bes/110/BigFix-BES-ClientARMMSIBundle-11.0.5.204.zip

https://software.bigfix.com/download/bes/110/BESAgent-11.0.5.204-rhe7.x86_64.rpm

The upgrade fixlets for agents are available in BES Support version 1505 (or later).

The BigFix Platform team

2 Likes
3

Why do we have to created a baseline if we are only upgrading one OS? I guess I see that the instructions say that the baseline will not have the download issue that 11.0.5.203 has.

I updated to 11.0.5.203 two weeks ago and have not noticed an issue with downloads. However, it does seem like evaluation times have gone up.

4

How can we know if our deployment is affected? Sending an action with any download would be enough to detect the problem?

We upgraded our BigFix environment to V 11.0.5 a couple of weeks ago.

1 Like
5

We've noticed an issue with crashing 11.0.5 clients on 11.0.4 infra.

Will the big changelist be updated to include the applicable issues?
https://support.bigfix.com/bes/changes/fullchangelist-110.txt

6

Yes, baseline is recommended for the agent upgrade in any case, as having the fixlet inside a baseline will prevent the crash that the fix is solving.

If you have not been affected by the crash it is unlikely that you will be in the short term, but the agent upgraded is strongly recommended anyway. Evaluation time should not be related to this.

7

If you have not been affected by the crash when running actions with downloads, it is unlikely that you will be affected in the short term, but the agent upgrade is strongly recommended anyway.

8

The changelist document has just been updated.

Thank you

2 Likes
9

What are the symptoms of systems having the issue with the 11.0.5.203 client? I see a client that has a bunch of pending downloads, and I have many clients reporting slowly since going to 11.0.5.

10

Hello,

the symptom is that the BES Client service crashes when processing downloads. On Windows you get exception code 0xc0000005; crash happens on other operating systems as well.

We are not aware of a relation of this problem with report times or other download issues.

Thank you

11

I am experiencing the BES Client crashing on some of my relays. I keep starting the client and it keeps stopping. Do I have to keep starting the client? I have sent the updated client but it is not updating because the client keeps stopping.

12

You should include the client upgrade fixlet in a baseline; in this way, you avoid that the download of the installer itself crashes the client.

13

This topic was automatically closed after 30 days. New replies are no longer allowed.