9.2 Patch 7 for IBM BigFix Platform

[Aram]

The IBM BigFix team is releasing 9.2 Patch 7 (9.2.7.53) of the BigFix Platform. The main features of this release include:

• APAR fixes
• Update to OpenSSL 1.0.1q which addresses vulnerabilities in previous OpenSSL versions
• Certification of Relay on Windows 10 and
• Certification of Agent on RHEL 7.1
• New inspector features on Linux to enable SCAP 1.2 certification for RHEL

All Platform components are being released in this patch.

Downloads and release information are available at:

http://support.bigfix.com/bes/release/9.2/patch7/

The full technical changelist is available at:

https://support.bigfix.com/bes/changes/fullchangelist-92.txt

Upgrade Fixlets are available in BES Support version 1247 (or higher).

[Aram]

[jmaple]

Where can we get the information about the new inspectors for RHEL?

[Pete_F]

Does this include a new version of the Server Components? Im not seeing a fixlet to upgrade… Only the Installation folders update is there.

[AlanM]

These should be added to developer.bigfix.com shortly with details but are you looking for just a summary?

[jmaple]

Yeah I was just hoping to see what kind of new toys there were to play with.

[AlanM]

The server components are updated yes and there should be a fixlet available. Could it possibly be not relevant?

[BigFixNinja]

Hey Alan, can we get @jmaple and all the other kids some new toys to play with?

[jmaple]

I like toys

[Pete_F]

Hmm… Its there now , greyed out as non relevant… Both the manual upgrade and the normal fixlet… On both the dev and prod instance… Im going to throw the relevances at the qna and see what breaks…

[newmanjn]

Under “Bigfix Management” -> “BES Deployment Upgrade” -> “Server” - there is nothing listed… and I am on 9.2.6.94.

There are updates listed under Relay, Client and Console, but it seems the server fixlet is not there yet… anyone else seeing this?

When can we expect a fixlet to show up for the Server component?

[Pete_F]

The problem seems to be Relevance 10… the 9.2.6. version looks for a service name that contains “MSSQL” where as the 9.2.7 version looks to see if it contains "MSSQLSERVER"
9.2.6 evaluates to true, 9.2.7 to False because the actual short service name is “MSSQL$name of your instance”

I guess if they changed it to check for he display name contains “SQL Server” that would work…
Should I get a PMR in ?

[newmanjn]

Yeah, if you don’t mind… nice find!

[dwerdwer]

This version has a repair in the software distribution file name contains Chinese support ？

[AlanM]

I don’t know if a PMR was filed but we are fixing it. It will only affect those with named instances on their SQL DB

[Aram]

Thank you for bringing this to our attention! I believe this has been addressed as of version 1248 of BES Support. Please let us know how the new approach works out for you.

[heagsta]

Is anyone running this version yet and had good/bad experiences? I am looking to upgrade and I normally go to a version behind the latest; however, I saw that 9.2.6 has an issue where the client does not start automatically after being installed, and I don’t really like that because we are pushing out to 15,000 endpoints. I guess we could just script that piece through powershell to start the service. Any experience with the latest version?

[hmmarkka]

We’ve been running the latest patch version a few days without problems. We do OSD, server automation, software distribution, web reports and all the basic stuff works just fine. We have 17K endpoints, almost all supported operating systems aboard. Haven’t upgraded all the clients yet but the ones I have, have worked OK. All bes root servers and relays we have are Windows based.

[heagsta]

We are basically in the same boat, minus the upgraded server version. That’s good news, thank you for the info.

[Aram]