I personally made the decision to install a separate instance completely (although it can be on the same database server with no conflict, obviously) and use the Transporter tool, as mentioned. This can be staged as a pre-production environment, if he chooses. The only downside is moving users back to the BES 4.1.6 environment, in which he'd need to wipe and reactivate.
He could also upgrade the 4.1.6 database to 5.0, but he'd need to use BAS to manage the 4.1.6 server at that point, in addition to the separate 5.0 server. Obviously this gets a tad confusing and definitely changes the production server environment.
__________________
BCSA (4.1, 5.0) | BCSD (4.1, 5.0)
The views expressed by me on Port3101.org are my own and do not necessarily reflect the views of my employer.
|