9.5 Released for IBM BigFix Platform

The IBM BigFix team is releasing 9.5 (9.5.0.311) of the BigFix Platform. The main features of this release include:

  • Unicode Support
  • SAML 2.0 authentication support for the BigFix Console
  • Use of HTTPS protocol for site gathering and license updates
  • Enablement of Agent on RHEL OS running on PowerPC LE hardware
  • Database cleanup tools now included in BESAdmin

This release includes all Platform components.

For more details on the features in this release, see the following Wiki:

https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Endpoint%20Manager/page/IBM%20BigFix%209.5.0%20Release%20Notes

Downloads and release information are available at:

http://support.bigfix.com/bes/release/9.5/patch0

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

Note that 9.5 Patch 1 (9.5.1.9) is now available! For more information, please see 9.5 Patch 1 Released for IBM BigFix Platform

5 Likes

Am I correct in my understanding that this is a manual upgrade for everybody regardless of server configuration?

It appears as though the link to the documentation within the manual upgrade fixlet:

http://www-01.ibm.com/support/knowledgecenter/#!/SS63NW_9.5.0/com.ibm.tivoli.tem.doc_9.5/Platform/Adm/c_manual_upgrade.html

…is a bad link.

Correct. Your deployment keys are needed for this upgrade so you can’t upgrade the root server to 9.5 with a fixlet. Everything else can be upgraded via fixlet though

1 Like

Thanks for this catch! we’ll fix this.

1 Like

ahhhh I was just about to upgrade to 9.2.7. sounds like I should go straight to this, how’s everyone’s experience with 9.5 going so far?

The link will be fixed shortly but the correct link is:

http://www.ibm.com/support/knowledgecenter/SSQL82_9.5.0/com.ibm.bigfix.doc/Platform/Installation/c_manual_upgrade.html

And for Linux the correct link is:

http://www.ibm.com/support/knowledgecenter/SSQL82_9.5.0/com.ibm.bigfix.doc/Platform/Installation/c_upgrading1_linux.html

The links have been fixed

The BigFix client is stopping all the time without any reason: Checking that this machine is running the BES Client - NO

When I downgrade the client to the last working version, BigFix-BES-Client-9.2.7.53, then it seems to properly

You may wish to contact support as it would be difficult to determine what is wrong but do the client logs give any indication?

No indication at all!

I am the most attention to Chinese language support, :grinning::grinning::grinning::grinning::grinning::grinning::grinning:

1 Like

I’ve just upgraded my Bigfix server from 9.2.7 to 9.5.0 - everything seemed to go smoothly, our server runs on Win2008 R2 and updated just fine. I had a little hiccup with the Windows client fixlet not showing as relevant for a huge swath of my Windows clients, but I’ve resolved that.

What is happening now is that, logged in as a master operator, the Modify Custom Site Subscriptions menu entry when you right click on a computer in the besconsole is GREYED OUT - for my master operator accounts, for all my user operator accounts.

I google’d around and found the option disableNmoCustomSiteSubscribe, which supposedly when set to 1 in the advanced options using the site admin tool (or on the command line if your server is running on Linux), it would disable the ability to modify custom site subscriptions… but from what I read it should only apply to non-master-operators, and further-more we DO NOT have that option enabled. I actually tried adding it with a value of 0, restarting the bigfix server and reconnecting, but it made no difference.

There does not seem to be a enableNmoCustomSiteSubscribe option, heh. Is anyone else seeing this? Anyone have any ideas?

Thanks!


John

Hi John,

Can you confirm if you have any custom sites whose subscription policy is via ad-hoc subscription actions?

If there are no custom sites whose computer subscriptions are configured to be based on ad-hoc actions, then the ‘Modify Custom Site Subscriptions’ is expected to be unavailable in the Computer’s right-click context menu.

After enabling SAML 2 + 2 factor authentication, how will any non LDAP accounts be able to login or affected?

Will there be on the road map to support multiple IDPs’ per LDAP source? We pull accounts from 5 Domains.

This has made my BigFix deployment so much faster!!

1 Like

Thanks for the feedback