[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 464
  • Last Modified:

Exchange 2010 / Split DNS for migration

I am preparing to rollout Exchange 2010 for our organization. Currently we are using GoDaddy for email. Does anyone have a step by step document on setting up split DNS and configuring the various transports in Exchange so that I can migrate users from their POP email to Exchange? I have 165 users geographically dispersed and cannot migrate them all at once
0
hhnetworks
Asked:
hhnetworks
  • 3
  • 2
1 Solution
 
wolfcamelCommented:
split dns isnt really what you are after.
however.
i would do the following..
configure exchange and all the mailboxes
configure users to connect to exchange and their pop mailboxes - 1 by one
once all are configured this way change the MX record to move incomgin mail to exchange
get users to move mail from their pst files to exchange
once no mail is incoming to the old pop server (which may take a couple of days) then decommission the pop - by slowly removing pop/smtp from each user and deleting the godday mailboxes.
0
 
hhnetworksAuthor Commented:
Wont that cause routing issues with intracompany email between employees during the time it takes me to setup 165 instances of Outlook / Exchange? Exchange will automatically route all email within our AD domain directly inside Exchange, bypassing Godaddy altogether
0
 
wolfcamelCommented:
yes - but this way you wont lose any incoming mail.
you will need to keep everyone sending via smtp / and told to check both mailboxes.
with smtp as the default they should only see mail in exchange as it starts getting used properly.

you can also configure exchange to forward mail for any unresolved recipients to an external host

0
 
hhnetworksAuthor Commented:
I will set this up in a small lab and post my results back here. Thank you
0
 
hhnetworksAuthor Commented:
Sorry for the late closure on this. Here are the results:
1) GoDaddy does NOT allow relaying back to your own domain, even with an authenticated account once the MX records are pointed somewhere else. Truly the sign of an inferior hosting service concerned more with putting hot girls on the website than actually providing business grade services.
2) To work around, I published OWA to all my users and had them use this while I drove to all 12 locations to round up pst files and then used powershell to bulk-import them
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now