How can one migrate Exchange data to a new domain without joining the old?
There are a great number of very well written guides, just on this site alone, pertaining to the correct process by which to migrate information within Microsoft Exchange from one server to another. The process (briefly) involves joining a later model server to the domain of the earlier server, adding exchange, migrating it, and decommissioning the old server.
That's all well and good, but as a network administrator of a small business with no more than 25 employees, I've really had enough of the old domain I inherited. It wasn't configured properly and it isn't to my liking. So I'm wondering if there's a relatively painless method by which I can get all my users email (because that is ALL they use this server for...until I show them otherwise) without actually joining this lovely new server to the icky old one.
Given the option I'd just export PSTs and reimport them into newly made user accounts, but several users don't understand the concept of archiving. I believe one user has a mailbox that is over 13 gigs in size.
They're fairly concerned about things that might get left behind due to compliance/auditing reasons, but I plan to seal the old server for archiving purposes, and export all the mail on it to EML as well. (No, that's not my idea, but it should ensure we get nearly everything.)
So, suggestions? And yes, I suppose suggesting "What you're trying to do is a horrible idea." is also a valid suggestion. (Provided you explain why, of course.)
Thank you in advance, regardless. I tried searching for this, but all searches just turned up HOW to migrate exchange after joining to the domain rather than how to AVOID joining the domain to get the data across.
That's all well and good, but as a network administrator of a small business with no more than 25 employees, I've really had enough of the old domain I inherited. It wasn't configured properly and it isn't to my liking. So I'm wondering if there's a relatively painless method by which I can get all my users email (because that is ALL they use this server for...until I show them otherwise) without actually joining this lovely new server to the icky old one.
Given the option I'd just export PSTs and reimport them into newly made user accounts, but several users don't understand the concept of archiving. I believe one user has a mailbox that is over 13 gigs in size.
They're fairly concerned about things that might get left behind due to compliance/auditing reasons, but I plan to seal the old server for archiving purposes, and export all the mail on it to EML as well. (No, that's not my idea, but it should ensure we get nearly everything.)
So, suggestions? And yes, I suppose suggesting "What you're trying to do is a horrible idea." is also a valid suggestion. (Provided you explain why, of course.)
Thank you in advance, regardless. I tried searching for this, but all searches just turned up HOW to migrate exchange after joining to the domain rather than how to AVOID joining the domain to get the data across.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The Remote Move Request certainly looks like it'll handle everything in one fell swoop. Thanks!
ASKER
"While performing remote mailbox moves, the Microsoft Exchange Mailbox Replication service (MRS) uses the msExchMailboxGUID attribute to find matching users, thereby maintaining the Send As and Receive As permissions. MRS then maps the trustee to the matching user in the destination forest."
I'm trying to determine if the Remote Move Request works by simply taking an existing old mailbox, and asking you the username of the new mailbox, or if it requires the Mailbox GUID to be the same, as Exchange likes to do. If that's the case, it's not as useful as I'll have to join them in AD to copy over the users.
I'm trying to determine if the Remote Move Request works by simply taking an existing old mailbox, and asking you the username of the new mailbox, or if it requires the Mailbox GUID to be the same, as Exchange likes to do. If that's the case, it's not as useful as I'll have to join them in AD to copy over the users.
ASKER
After a bit more research it seems as though both will work. I don't have the equipment yet here to test this, but I'm pretty confident both methods will work. (And I'll have everything backed up if they don't)
The following link aids in preparing something for such a shift as well:
http://blogs.technet.com/b/exchange/archive/2010/08/10/3410619.aspx
It may be helpful to anyone who is about to attempt that which I plan.
Thank you both!
The following link aids in preparing something for such a shift as well:
http://blogs.technet.com/b/exchange/archive/2010/08/10/3410619.aspx
It may be helpful to anyone who is about to attempt that which I plan.
Thank you both!
ASKER
I have a script designed to export mailboxes to PST with Exmerge, and it splits off to a new file when it hits the 2GB limit. I've used it with success.
What you've described is the only method I know to do this manually, but I didn't mention it as I wasn't sure it was a complete solution. (And I'd not heard of the Import-Mailbox utility)
If all that method doesn't leave anything behind, I'm willing to go that route. That should keep any lingering settings I haven't found in this domain away from the new one.
One issue: There is a single public calendar in a shared folder. Will that be difficult to move to 2010?