Tip: Upgrade - A way to prevent problems from occurring in your BigFix deployment

“UPGRADE!”

http://support.bigfix.com/bes/changes/fullchangelist-82.txt
http://support.bigfix.com/bes/changes/fullchangelist-90.txt
http://support.bigfix.com/bes/changes/fullchangelist-91.txt
http://support.bigfix.com/bes/changes/fullchangelist-92.txt

So many improvements and bug fixes with each new release!

Upgrade to 9.2.6.94 today, or plan on upgrading to 9.5 (soon to be released) to take advantage of these improvements and bug fixes.

Upgrade Guide

What is soon? :smile: (for the 9.5?)

Targetted for end of Q1 / beginning of Q2 but subject to change. :smile:

If there are those here who are planning to upgrade, we here in Support would like to get a pro-active view on it to better plan for any troubles. Also, we could start a pinned upgrade post specific for upgrade discussions. Maybe we should have a section on this forum dedicated to upgrading.

Any documentation on what is planned for v9.5?

1 Like

We are planning to upgrade (if we know what’s planned for v9.5)

1 Like

Not as of yet. :smile:

1 Like

But also potential new bugs.

It is always tough to balance new updates and stability, particularly if you aren’t having any specific problems already.

Agreed. For critical production deployments, stay at least one FP behind cutting / bleeding edge release?

1 Like

We will be upgrading from 8.2.1409 to the latest version 9.2.7. Are there any pitfalls to jumping that many versions or issues to plan for? The server/console/db are all on the same server and it is on Windows Server 2008 R2 SP1 with SQL Server 2008 R2. What kind of maintenance window should we schedule for the upgrade?

1 Like

The size of the maintenance window depends upon partially how big your environment is.

Definitely make backups / snapshots / db backups before a major upgrade like that.

You could actually do a “DR” process, by setting up everything from scratch, migrating the data/db/ect…, and switching over to the new infrastructure, with the option to switch back if something goes wrong.

Yeah, n-1 aproach on tools versions is a good practice.

Do not desperate or hurry when upgrade process is in progress, I think is a good advice for those who don’t have any experience on upgrading.