BlackBerry Forums Support Community               

Closed Thread
 
LinkBack Thread Tools
Old 11-09-2004, 10:27 AM   #1 (permalink)
Thumbs Must Hurt
 
Join Date: Oct 2004
Location: London
Model: 9780
Carrier: Vodafone UK
Posts: 56
Post Thanks: 3
Thanked 0 Times in 0 Posts
Default

Please Login to Remove!

Offline  
Old 11-09-2004, 04:01 PM   #2 (permalink)
Knows Where the Search Button Is
 
Join Date: Sep 2004
Posts: 33
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Offline  
Old 11-09-2004, 07:17 PM   #3 (permalink)
Thumbs Must Hurt
 
Join Date: Oct 2004
Location: North Carolina
Model: 8300
Carrier: AT&T
Posts: 119
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Offline  
Old 11-10-2004, 07:06 AM   #4 (permalink)
New Member
 
Join Date: Dec 2004
Location: Raleigh NC
Posts: 4
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Offline  
Old 11-10-2004, 09:00 AM   #5 (permalink)
CrackBerry Addict
 
Join Date: Oct 2004
Model: 9800
OS: 6.0.0.337
Carrier: (`.at&t.)
Posts: 825
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Offline  
Old 11-16-2004, 02:03 PM   #6 (permalink)
Knows Where the Search Button Is
 
Join Date: Jan 2005
Location: Columbus, OH
Posts: 18
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Offline  
Old 01-07-2005, 01:09 PM   #7 (permalink)
Thumbs Must Hurt
 
Join Date: Jan 2005
Location: Atlanta
Model: 9330
Carrier: Verizon
Posts: 107
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default BES server during Exch migration?

when migrating from exch 5.5 to 2003...with 2003 joining the 5.5 site, will BES continue to work for migrated mailboxes, until such a time as it's reconfigured to point to the new 2003 server?

Anybody been through this?

Also, does BES update the "Last Logon" userid that shows in exch admin/system manager?

Thanks for any information.
Offline  
Old 01-13-2005, 01:52 PM   #8 (permalink)
Thumbs Must Hurt
 
Join Date: Jan 2005
Location: Atlanta
Model: 9330
Carrier: Verizon
Posts: 107
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default CLARIFICATION:

Exchange is in an NT4 domain. Can I put the BES server in our AD domain (there's a two-way trust between both), have it access the Exchange 5.5 servers, and just reconfigure to point to the Exch2003 server mailboxes when that time comes?

Thanks in advance for any info.
Offline  
Old 01-13-2005, 08:46 PM   #9 (permalink)
BlackBerry God
 
jibi's Avatar
 
Join Date: Oct 2004
Location: Jibi's Secret Place
Model: 8900
OS: 4.6.1.174
Carrier: AT&T
Posts: 11,310
Post Thanks: 0
Thanked 1 Time in 1 Post
Default

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.
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.