Skip to Content
0
Former Member
Dec 28, 2007 at 11:36 PM

Lessons Learned Migrating from BOXI R1 to BOXI R2

23 Views

Post Author: tmiller

CA Forum: Deployment

Some notes from our upgrade from Release 1 to Release 2 to, hopefully, prevent headaches in other users:

Make sure you have your Release 2 license keys, Release 1 keys won't work (check with your vendor if you are an OEM purchaser)

Make sure you have notes on all your server configurations, including which Destinations are enabled (and their configurations) for the Job Server. Screen shots are a big help here.

If you are an OEM user, you have to install at least SP2 (which requires SP1 be installed first) or your licensing will be, uh, how to put it delicately, invalid

During upgrade, add your license keys in the console BEFORE doing the datasource upgrade.

If you are upgrading in-place, what worked best for us was to restore our pre-upgrade backup of the CMS database (we use SQL Server) to a new database and import from there to the bobjecms database. You also need to have a different ODBC DSN setup for each of these databases.

Once your datasource import is done, make sure you run the UPDATE OBJECTS process from the Central Configuration Manager, otherwise, you'll get an error if you use Windows AD authentication: Error retrieving info for Windows AD authentication: Unable to get SI_SSO_VENDOR property value. (Windows AD authentication won't work, you'll get this error when trying to configure it through CMS).

Enable servers that you noted in step 2

You'll need to update Crystal Reports for your report developers to Release 2, also - especially if you use Windows AD authentication. Do a COMPLETE UNINSTALL of Crystal Reports release 1, reboot, and then install a fresh Release 2. If you don't uninstall R1, you will most likely have an annoying "Please wait while Windows configures Crystal Reports XI Release 2" window every time you load Crystal or any VB developed app or Visual Studio 2005. This might be limited to only clients with VS 2005 installed, but might notu2026

Those were the major (and minor) hurdles we had to clear to get this upgrade done correctly u2013 and this is also an excellent example of why we have a test and a production server.

Hope this helps someone else out there.

- Tom