Originally Posted by jeffro01
Under this scenario each BES version has it's own separate back end SQL DB right?
No, He can install 5.0 on the new server and point to the existing DB. This will upgrade the schema of that DB and make the new bes a member of that BB domain. Then he can just 'move' the users via the new BlackBerry Administration Service (BAS) console to the 5.0 BES. This assumes he has a spare srp.
If he doesn't have a spare SRP, he can:
- Turn off the services of the 4.x bes (set them to manual so they don't come back on accidentally)
- Install 5.0 on new server and point to 4.x DB
- Use the SRP identifier and Key of the 4.x BES server.
- Finish the install, start the 5.0 BES
- Log into BAS and move all the users from the 4.x BES (this will show up as the users current location), to the new 5.0 BES.
- The BB's will switch to the new server and mail should begin flowing.
In the above scenario, don't EVER start the old 4.x BES again as it will lock our your SRP if running at the same time the 5.0 BES is using it. At this point, you would go into Component view under Servers and Components in the BAS and remove the 4.x BES... I think you would want to uninstall it from the physical hardware first and then remove the components... Or it could just live there and be orphaned...
It would be optimal to have another SRP. Then you could move the users back and forth between the 4.x BES and the 5.0 BES. You could even keep the 4.x BES around indefinitely for cheap manual failover location.
The other benefit to this method is that any IT policies that you had manually created will be on the new 5.0 server as well, since IT policies are domain centric.