• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1331
  • Last Modified:

Single label migration to 2008 r2

Hi,

I have a network with 2003 servers and exchange 2003 in a single label domain.

I have two new servers with 2008r2 and exchange 2010.

I want the single label domain to go away but after reading around it appears a domain rename in this situation is a bad idea because it will break exchange.

I went ahead and created a new domain with a fqdn, joined the second server and setup exchange 2010. After creating new stub zones on both the old and new domain's dns servers I can now ping from both sides using host name.

So now I figure I should just setup a trust and migrate from old forest/domain to the new one. Then move mailboxes from old server to new.

I'm wondering if I will run into any issues migrating from the old single label domain (domain1) to the new 2008 one (domain2.local). Is there anything I should look out for? Has anyone done this? :) Just looking for any advice, input, recommendations, recommended third party tools etc...

also the single label domain is the same as our external domain without the .com. So now the new domain name is different from our external domain. I don't think this should be a problem but new to 2008.

Any input is greatly appreciated.
0
x534n
Asked:
x534n
  • 8
  • 6
  • 4
3 Solutions
 
Stelian StanCommented:
0
 
Exchange_GeekCommented:
Precisely what are you looking out for?

Moving Exchange / Active Directory / both to the new FQDN?

Regards,
Exchange_Geek
0
 
x534nAuthor Commented:
I don't think I have a choice of what type of migration I should use. I think the only option is to create a new forest and root domain and do a intra forest migration thanks to the single label domain name. It seems a rare scenerio with that pesky single lable domain. (it wasn't me who created the single label domain) It has been mildly problematic but not bad I just assume I should fix it now rather than join the new stuff to a single lable domain. Maybe my assumption is wrong because that sure would make my life easier just to join existing ad.
0
Granular recovery for Microsoft Exchange

With Veeam Explorer for Microsoft Exchange you can choose the Exchange Servers and restore points you’re interested in, and Veeam Explorer will present the contents of those mailbox stores for browsing, searching and exporting.

 
x534nAuthor Commented:
I could rebuild active directory but I really need exchange moved to new fqdm.
0
 
Exchange_GeekCommented:
What are the number of mailboxes and their total size approx count?

Regards,
Exchange_Geek
0
 
x534nAuthor Commented:
just hoping I'm on the right track.
0
 
Exchange_GeekCommented:
Well, that wasn't the exact answer i was expecting :)

Regards,
Exchange_Geek
0
 
x534nAuthor Commented:
only 25 mailboxes, sizes vary greatly. information store about 48 gigs.
0
 
Exchange_GeekCommented:
Well, then avoid the mess of migration - simply export the mailboxes to PST. Create mailboxes on the new Exchange 2010 in new AD Forest. Have those 25 users point their OL to new forest (of course DNS is essential in this configuration).

Provide PST to all of them OR import PST back to the mailboxes.

Regards,
Exchange_Geek
0
 
x534nAuthor Commented:
Do pst files still have a size cap? Looks like my largest one is only 5 gigs.
0
 
Exchange_GeekCommented:
No such limit in E2010 that I've heard of.

Regards,
Exchange_Geek
0
 
Stelian StanCommented:
Like Exchange_Geek mentioned is no limit on Exchange but on Office 2010 the size limit is 20 GB: http://support.microsoft.com/kb/982577 and on Office 2007 the limit is 2GB: http://support.microsoft.com/kb/830336
0
 
x534nAuthor Commented:
most machines have Office 2007.  Mailboxes being exported from 2003. I have some 5GB mailboxes.
0
 
Stelian StanCommented:
To export from Exchange 2003 you can use ExMerge. Excellent explanation:
http://www.petri.co.il/brick_level_backup_of_mailboxes_by_using_exmerge.htm
or
http://www.rackspace.com/apps/support/portal/6159

For files larger than 2GB, use the Options button on the Source Server page and click on the Dates tab. You can then specify a date range for the .PST being exported to help reduce size.
0
 
x534nAuthor Commented:
I've read that using exmerge breaks a few things like the inability to reply to old emails or edit old calandar items. Do think this is a major drawback?

Today I was attempting to use the remote move request from the 2010 server to 2003 but I couldn't get it working. Do you think I would be better off using that or is it not worth the effort in my case?
0
 
Stelian StanCommented:
At some point you mentioned that you only have 25 mailboxes. I think it would be quicker to export the mailboxes to PST and import them to the new environment.

Some considerations from Microsoft doc (http://technet.microsoft.com/en-us/library/ee633455.aspx):

Before you import or export mailbox data, consider the following:

To import or export mailbox data, a network shared folder accessible by your Exchange servers must be set up. You must also grant read/write permissions to the Exchange Trusted Subsystem group so that group can access the network share where you import and export mailbox data. If you don't grant this permission, you receive an error message stating that Exchange is unable to establish a connection to the target mailbox.
The maximum .pst file size supported by Outlook is 50 gigabytes (GB). Therefore, we recommend that you don't import a .pst file larger than 50 GB. You can create multiple .pst files for mailboxes larger than 50 GB by specifying specific folders to include or exclude or by using a content filter.
Import and export requests are performed by MRS, which also processes move requests and mailbox restore requests. All requests are queued and throttled by MRS. To learn more, see Throttling the Mailbox Replication Service.
Importing and exporting mailbox data may take several hours depending on file size, network bandwidth, and MRS throttling.
Data can't be imported to a public folder or public folder database.

A really good document on how to import PST files: http://www.simple-talk.com/sysadmin/exchange/importing-psts-with-powershell-in-exchange-2010-sp1/
0
 
Exchange_GeekCommented:
@x534n

Our job here is to help you with our experiences which is what I am trying to do.

If you are working with 25mailboxes and max size of 48 gigs of database - trust me going through the hassle of adding the new box into a single domain environment - you're in for a nightmare - if this is the walk you want to go for - I'll leave that decision to you.

What my other friend mentioned about limits in OL - I don't even think any of your mailboxes would be above 5 Gigs max - so those limits may not be even thought of. However understand that ExMerge cannot export data beyond 2 Gigs. So, my best recommendation is to export data using OL for each of those accounts.

25 mailboxes you'll have the export completed if you have a good connection - max in 3-4 hrs.

Like-wise importing data would complete in same time. So, you're done with migration in max 1 day time - versus setting up Exchange and its hassle of cross over migration.

Regards,
Exchange_Geek
0
 
x534nAuthor Commented:
Ok, I'll take your advice, thanks for the input guys.
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 8
  • 6
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now