Improve company productivity with a Business Account.Sign Up

x
?
Solved

Some questions on moving mailboxes to a new Exchange server

Posted on 2008-06-24
1
Medium Priority
?
203 Views
Last Modified: 2010-03-06
In the next couple of weeks, I will be moving services slowly off a DC/Exchange 2003 box to a new Exchange 2003 box. I am going to have a 2 phase process.

Phase 1 - Build up new Exchange server with Standard using standard RAID configurations for database and log stores. I will give it a different name and Store name than old box. I then will use move mailboxes from the old box (.4 in IP terms to make it easier to follow) to the new box (.10, again IP address).

I understand that with this, the user's Outlook will automatically change to see the new store and update itself. My questions are as follows:
1) From reading Blackberry documents, BES will automatically update its pointers to the new mailboxes as well (it just might take awhile and might require a restart of BES services). Any other warnings?

2) OWA is homed on .4. When moving the mailboxes, will anything need to be changed in IIS or elsewhere for this to work?

3) RPC over HTTP is set to point to .4. When moving mailboxes, will anything need to be reconfigured on this level?

4) Will remote users who may not have access to the domain need to update anything manually before connecting RPC over HTTP on their Outlook settings? Should they VPN in to have it work?

Then Phase 2 is to move everything else to .10 and decommission .4 (AD is being housed on a different server .3 so I know I need to make sure all the roles reside with THAT server). I have done a decommission of an Exchange box  before so I am aware of some of the pitfalls, but my biggest concerns are OWA, RPC over HTTP, and the Blackberry services.  Anything I should look out for here?

I know this is a big question, so I am awarding big points (and a virtual case of your favorite frosty beverage!)

0
Comment
Question by:kirk_lesser
1 Comment
 
LVL 71

Accepted Solution

by:
Chris Dent earned 1500 total points
ID: 21868802

Hey there,

This question deserves a response of some kind...

1. I didn't have any problem last time I moved lots of mailboxes between servers (1500 of them, around 100 with accounts on a BES).

Well, other than the service restart because I'm fairly paranoid about BES and it's connections.

2. Nope

3. Uses the same proxying mechanism as OWA, so shouldn't need to be a connection to the server holding the mailbox (just an Exchange Server within the right Domain).

4. It depends how you're allowing it in. If you're changing the external URL they'll need to update that. Otherwise it should be transparent.

For the change over, OWA and RPC over HTTP can run on two different Exchange Servers simultaneously. That means you should be able to test the new one works prior to turning off the other.

BES should be able to cope with it's account moving. It would be worth checking the MAPI Profile for BES works properly afterwards (as I'm sure you would anyway). I haven't actually tried moving that one between servers before (or I don't think I have), but I see no reason for it to fail.

HTH

Chris
0

Featured Post

The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

This article involves a discussion about issues people have when it comes to Client Access in relating to Load Balancing in an Exchange environment which we had ourselves, along with a solution I found to the problem.
Microsoft Exchange Server gives you the ability to roll back a corrupt database, but still preserve any data written to that database since the last successful backup. Unfortunately the documentation on how to do this when recovering using imaging b…
This video shows how to quickly and easily deploy an email signature for all users in Office 365 and prevent it from being added to replies and forwards. (the resulting signature is applied on the server level in Exchange Online) The email signat…
Whether it be Exchange Server Crash Issues, Dirty Shutdown Errors or Failed to mount error, Stellar Phoenix Mailbox Exchange Recovery has always got your back. With the help of its easy to understand user interface and 3 simple steps recovery proced…

584 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question