03-08-2006, 08:54 PM
Join Date: Apr 2005
Post Thanks: 0
Thanked 2 Times in 2 Posts
Before you can get to the merging stage the following should be noted:
1. "Their BES is 2.2" .... not good...why..this BES does not use MSDE/SQL and it would have to be upgraded to 2.2.3x before you can consider going to 4.0
2. "Ours is 4.0" ....issue here is different SRP IDs, 4.0 uses an MSDE/SQL db architecture. Since both servers are on separate db architectures, and don't presently use a single configuration db, there's no possibility of "migrating" these users. You can create/add the "2.2" users as New Users on the 4.0 BES. This will lead to orphaning of the users' old mail...plus they'll have to recradle because of the new SRP ID on the 4.0 BES. This boils down to basically setting these users as new 4.0 users.
As for the DNN.....if the servers were created using the same Organization certifier...then they're using the same NAB (also called PAB) and should be "seen" when a "File->Database->Open is done. If they do not appear, then check that the server was added to the LocalDomainServers group in the NAB.
If you are using the BlackBerry Manager console (I assume this is what you're referring to) on the 4.0 BES to "see" the 2.2 BES....then that will not work, because the 4.0 BES is on a MSDE or SQL db (however you did the setup) and the 2.2 BES is using the native *.nsf databases and not the same MSDE or SQL.
The issue here is not migrating users between DNNs but rather migrating users from an older BES version using a different db architecture to the new db architecture.
There are two ways to do this....
The Clean way - Recreate the users on the 4.0 BES. This however will involve
significant user intervention like recradling, new encryption key generation and possibly a device security wipe to get get rid of IT policies if present.
The Dirty way - Upgrade the 2.2 to the minimum level (2.2.3a) and then do an upgrade to 4.0 and point to the SQL db on 4.0 BES. I believe at this stage it may be possible to use the nbesmigration command line tool to migrate the users to this single configuration database.
This upgrade process is not downgradeable because of the significant system changesnor can you roll back. Obviously you'll have to make replicas or use backups of the *.nsfs in the /BES and /BES/State folders to revert to the 2.2
There are other considerations other than what's mentioned here.