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!!
Thanks for the feedback
where do i find Database Cleanup Tools
for Windows you find information here:
http://www.ibm.com/support/knowledgecenter/SS2TKN_9.5.0/com.ibm.bigfix.doc/Platform/Installation/c_clean_up.html
for Linux, you can find the BESAdmin CLI options described here:
http://www.ibm.com/support/knowledgecenter/SS63NW_9.5.0/com.ibm.bigfix.doc/Platform/Installation/c_running_the_tivoli_endpoint_ma_onlinux.html
thanks i got it to work on my windows system
In WebUI and WebReports you can append /login to the service url to get a login page for non-LDAP operators.
With regards to supporting multiple IDPs, I’m not sure if there are plans to add that capability. Would it be possible to have a single IDP in your environment that can authenticate accounts from those five different domains?
Hi aasheim,
we have this trouble too - is there a chance to bring the BigFix Client Service stable online?
Hell! I was told by Aram that they are working on a new patch that will fix the issues. In the mean time, I have recognized that it may help to stop the Core Protection VDI services to make the client stable…
What is the best upgrade path for those of us who are still on 9.0? Upgrade to 9.2, then immediately upgrade to 9.5? Or stand up a 9.5 server and migrate clients over to it?
Standing up a new instance (and subsequently migrating endpoints, operators, content, configurations, etc…) can certainly be done, but is a fairly disruptive process. As you’ve noted, you should be able to first upgrade the Server to at least 9.2.3 ( https://www.ibm.com/support/knowledgecenter/SSQL82_9.5.0/com.ibm.bigfix.doc/Platform/Installation/c_upgrade_paths.html?lang=en ), then subsequently upgrade to 9.5. If you haven’t already reviewed the Upgrade Best Practices, I’d recommend doing so:
Okay. My server guy tells me he’d actually prefer that I stand up a new server, so we can end up with a single server with a new IP address. As I recall from setting up the 9.0 server, changing the IP address of the main server is pretty involved. If I’m going to end up with a single, primary server with a different IP address, what is the best path forward?
Thanks for your help.
I’m planning to upgrade tomorrow, but just came across this APAR that gives me pause:
IV83679: UPGRADE TO 9.5 CAN FAIL BECAUSE INCONSISTENT DATA IN THE DB
Multiple values for the same property and computer id can lead to a failure during the upgrade to BigFix 9.5.
Is there any way to determine whether this will affect me before I attempt the upgrade?
Attempt the upgrade in your Test/QA deployment first to validate. Ensure you backup your database first before any upgrade attempt.
Hi Jason,
please notice that the APAR you are mentioning applies to very specific conditions in a BigFix server on Linux with remote DB configuration. All other configurations (e.g. local DB or any Win server deployment) are not affected. However, running the upgrade on a dev/test environment is the best way to validate it.
Thanks, I had missed that note.