BlackBerry Forums Support Community               

Closed Thread
 
LinkBack Thread Tools
Old 10-30-2007, 12:31 PM   #1 (permalink)
New Member
 
Join Date: Oct 2007
Model: 8100
PIN: N/A
Carrier: verizon
Posts: 2
Post Thanks: 0
Thanked 0 Times in 0 Posts
Unhappy Phased migration

Please Login to Remove!

Like most people asking the questions here I am the newly designated BES "expert" in the middle of a major project. We are migrating two domains to one new domain. One domain is in the same forrest as the new domain and one is not. We are running BES 4.0.x on Exchange 2K3 on both original domains. The new domain will run BES4.1.x on Exchange 2K7. The problem is how to get everthing there as seemlessly as possible. I have two seperate SRP keys so I can do a phased migration.

We have done:

Moved BES and same forest domain users into new domain on exchange 2K3
BES 4.0.x

My idea for the moves and upgrades are as follows please let me know if they can be improved on or they are just bad.

1. Install new BES with 4.1 in new domain and move existing domain users to it. Leave them on Exchange 2k3 because that is what the timeline dictates. 2. Upgrade original BES to 4.1 for redundency/load balancing.
3. Move outside forest users to new Exchange 2K7 server in new domain and move them to new BES server.
4. Move Exchange 2k3 users to Exchange 2K7.

So what did I miss?
Offline  
Old 10-30-2007, 12:32 PM   #2 (permalink)
Grumpy Moderator
 
NJBlackBerry's Avatar
 
Join Date: Aug 2004
Location: Somewhere in the swamps of Jersey
Model: i5s
Carrier: AT&T
Posts: 27,798
Post Thanks: 33
Thanked 441 Times in 381 Posts
Default

Closing duplicate thread.
Offline  
Closed Thread


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On





Copyright 2004-2014 BlackBerryForums.com.
The names RIM and BlackBerry are registered Trademarks of BlackBerry Inc.