01-13-2005, 08:46 PM
Join Date: Oct 2004
Location: Jibi's Secret Place
Post Thanks: 0
Thanked 1 Time in 1 Post
First off, if you are wanting to have a period of no downtime, then don't expect that. I would go ahead and set your superiors' expectations to have downtime (although not much is needed).
I do not believe there is a way to do what you are wanting (BES account in AD; access to 5.5). I could be wrong. I'm not sure what other people did in their migrations, but I simply built up a new server (with test SRP) on the new AD with a new service account and then when we migrated users, they were added to the new server. The old server was decommissioned and the SRP information was changed on the new server. This step requires the end-users to recradle twice (once after their account migration; once after the SRP change).
I had one issue after that with the SRP not being updated for MDS (even though I did it within the management console). I had to drop the database and recreate it (5 minutes worth of work - no data loss or post-work user impact).
Anyone else have some best practices for Domain migrations and Exchange upgrades?
In the beginning the Universe was created. This has made a lot of people very angry and is widely regarded as a bad move.