Upgrading from v7.0.1 to v7.0.7 using BES Fixlets

Usage and Config Platform
1

(imported topic written by curth)

I performed the upgrade from v7.0.1 to v7.0.7 today on my production BES Server. The upgrade was successful with the following exceptions:

BigFix Web Reports (on a separate server) manual upgrade (there should be a Fixlet for this) misconfigured the bes_BFenterprise System DSN. This was an easy fix.

I noticed that the BigFix Relay Agents deployed over the last month or so (before the upgrade) were already at v7.0.7.82. This is concerning especially because BigFix makes a big deal about the installation order. I guess the BigFix Relay can be newer, older or the same version as the BigFix Server/Console.

The upgrade of the Installation Folders, however, only upgraded the Installation Folders up to v7.0.7.82. The Fixlet for the BES Client upgrades clients to v7.0.7.96. There should be a BigFix Fixlet to upgrade the appropriate Installation Folders to the newest versions i.e. v7.0.7.96.

So, do I now have to upgrade the Installation Folders manually now? <-- I have also sent this question as an email to BigFix Enterprise Support.

2

(imported comment written by BenKus)

Hey Curt,

Everything in there is by-design (except that you are right that it would be nice to handle remote web reports upgrades better)… Specifically:

  • The 7.0.7 relay is forwards and reverse compatible with all 7.0.x and so if you have 7.0.x installed, it offers to install the latest relay for you (rather than use an older relay that you would need to upgrade later).
  • There is only a Fixlet to upgrade from 7.0.7.96 for the BES Agent because the other components had very small changes and we didn’t want customers to need to upgrade unnecessarily… See http://forum.bigfix.com/viewtopic.php?id=1781 for more info about the installation generator.

Ben