[Koolvin]

Our current Environment

• Windows Server 2003 SP2
• Exchange system Manager 2003
• MS SQL running locally on server
• Exchange Server 2000 running on Windows 2000
• BES 4.1.6

Our problems

ESM mismatch with exchange

Our solution ??

We are proposing to Install Windows 2000 with ESM 2000 and SQL on a new hardware box to match our current exchange environment and stop these stupid cdo.dll mismatches. Install same version of BES as above (or may consider V5) We may virtualise this box How do we migrate our users from the old win2003 box to the new win2000 box ?

Future plans (dont know when but exchange environment already setup)

• Exchange 2007
• Windows 2008
• Different domain and different forest
  
• possibly upgrade to BES V5

all above ready to migrate users once we have finished testing.


Comments and suggestiions welcome on how to migrate users as in plonk the BES service of the old box onto the new and what process are involved with the handsets, do we need to touch them etc? Virtualisation comments and other comments bearing in mind future plans welcome also.

[knottyrope]

What version BES?

New domain in same forest?

[Koolvin]

Originally Posted by knottyrope

What version BES?

New domain in same forest?

whoops! OK ammended first post

Different forest and current BES version 4.1.6

[knottyrope]

Knife edge will work for the new 2000 box.

My notes when I did it on my 2000 server. Just use 2000 tools instead of 2003.
http://www.blackberryforums.com/bes-...e-cutover.html

new forest in same exchange org?

[Koolvin]

new forest is in different exchange org

[knottyrope]

You will have to activate on new server and possibly wipe the devices if they dont activate with your new domain.