Since you opened that can of worms....here's something I'm working on. Tell me if my logic is ok.
Scenario: approximately 20 BES v3.6 within the same domain across the city, with several Exchange severs ~40. There's a consolidation effort towards that as well.
All have separate MSDE/SQL2000 local dbs
All have different BESAdmin accts - don't ask why, that's how it is
May not have any IT Policies - I'm really hoping it is so
BES users per BES - range from 60->800
Project: Consolidation to 5 BES v4.0.X with clustered SQL and remote attachment servers. All new hardware.
Plan: To make the transition as seamless/transparent as possible
Procedure: in the interim- upgrade users to v4.0 (desktop&device)-preparation for EA
Install v4.0 on new hardware with one of the current SRP IDs, possibly BES
with the least amt of users- isolated of course
Export user list, CALs etc from old BES v3.6 - use for the new BES v4.0 above
Copy/restore method for mdf & ldf files on the new sql cluster
Bring up new BES v4.0 (after testing...etc and shutting down old BES v3.6)
At this point things should be good for these uers - same srp id...etc.
For the other BESs...simply move/add them to the new BESv4.0, and activate via EA.
Eventually freeing up SRP IDs to be used for the other new BES.
My only question here is the BESAdmin accts for the older BESs. They become obsolete after the migration....but can the new BESAdmin acct be used to add the old BES servers to the new BES console. Same domain shouldn't be a problem?
What do you think?
|