Source
r/exchangeserver•
usbeef

Need Exchange Migration Help

I have an existing Exchange 2010 environment where the internal virtual directories and the AutoDiscoverServiceInternalUrl setting are set to the FQDN of the Exchange server.

When I introduced the new Exchange 2013 server (yes I know) to the environment I set all the internal and external virtual directories as well as AutoDiscoverServiceInternalUrl to mail.company.com.

I then migrated a test mailbox and changed the DNS record for mail.company.com on the host file on the computer I was using so that AutoDiscover would be looking at the new server. After the migration was complete and I reset the MSExchangeAutodiscoverAppPool and restarted Outlook everything was working fine. I then changed the DNS record for mail.company.com on the internal domain to point to the new server and all is well.

I am now at the point before I start migrating mailboxes where I need to change the mail flow to go through the new server so that external connections to ActiveSync and OWA work for the mailboxes that will be moved. The IP address on the spam filter needs to be changed and the send connector needs to point to the new server as I understand.

My question is regarding the virtual directory URLs and the AutoDiscoverServiceInternalUrl being set to the FQDN on the old server. Once I make the changeover will this be a problem or can I leave these as they are on the old server?

Posted Mar 22, 2018, 9:14 PM UTC

613
joey52685MCSE: Messaging / MCSA: Office 365•

Changing over mail flow really has nothing to do with ActiveSync and owa. You can move mail flow before, during, or after your migrations depending on your needs.

Autodiscover should resolve to the new servers. The other urls can stay the same.

2
usbeefOP•

My thinking was that without pointing the spam filter to Exchange 2013 that would mean once I move a mailbox that uses ActiveSync from 2010 to 2013, ActiveSync would not work for that user?

1
joey52685MCSE: Messaging / MCSA: Office 365•

No 2010 and 2013 will route mail between each other as needed.

1
chriscolden•

Should be fine. But if you wanted to change it to mail.Company.Com both will work

1
usbeefOP•

Thanks, my only fear is that all the Outlook clients connected to a mailbox on 2010 would disconnect and I am not sure how the clients would behave after making the change. Is it just a matter of restarting Outlook? Or restarting the AutodiscoverAppPool and then restarting the clients?

1
chriscolden•

This is only for autodiscover. They won't disconnect as they have already queried autodiscover. Further to this a non migrated mailbox will autodiscover find the 2013 server which will respond for any mailbox in the org. Outlook will then connect. If it connects to the 2013 server connections will either be proxied or redirected to the correct place. So I really wouldnt worry this shouldn't have any impact.

1
usbeefOP•

Ok thanks, I figured that since when I moved a mailbox from 2010 to 2013 the Outlook client disconnected and would not reconnect until I cycled the AutodiscoverAppPool. So if my Autodiscover was mail.ad.company.com and then I suddenly changed AutoDiscoverServiceInternalUrl eventally the clients connected to mail.ad.company.com would blow up but I suppose once Outlook eventually recognizes the new AutoDiscover address Exchange 2013 would just proxy to 2010 to find the mailbox and it won't be an issue.

1
chriscolden•

App pool might have been because you had recently changed the URLs. But yes this is my understanding.

1
toanyonebutyou•

Will prolly be okay but I would change it. You always want to proxy back not forward.... If that makes sense

1
declar•

FYI there is a migration doc

also ... preparing for coexistence

1
RZKojr•

hi, #1. AutoDiscoverServiceInternalUrl should resolve to the new server. #2. if you have 2010 with 2013 in co-exisitence, 2013 should proxy all your requests to 2010. this is known as down level proxy. 2010 cannot proxy requests to 2013.

what this means is, if your connections resolve to 2010 and mailbox is migrated to 2013, the mailbox cannot receive any requests coz the requests resolve to 2010 and 2010 cannot translate this to 2013 exchange (where the mailbox resides)

So if i were you, i would read the co-existence document very carefully, plan the namespace, correct all the virtual directory URLs and make sure that 2013 proxies all the requests to 2010.

Also 2013 uses HTTP where as 2010 uses both RPC and HTTP. meaning, 2010 needs to have OutlookAnywhere enabled for co-existence.

let me know if you need more clarification

1
usbeefOP•

Thanks, my fear is that the Outlook clients pointing to a mailbox on 2010 would disconnect as soon as I change AutoDiscover on the 2010 server to point to mail.company.com which of course translates to the IP address of the 2013 server. So my understanding is that the 2013 server should proxy the request back to 2010 but how that transition happens is the problem. How is Outlook going to react once I make that change? My thought is that everyone would get disconnected temporarily. I wonder if you can test this by just tricking Outlook on one client into suddenly pointing to the new server for Autodiscover?

1
RZKojr•

So, autodiscover is only used when your client needs to open a connection with the mailbox. If an outlook client is connected, it will stay connected. Now lets say you change autodiscover settings, the next time the client tries to autodiscover, its request would reach 2013 and the 2013 will now proxy the request. You would also notice a change in the connection status, it would switch frm RPC to HTTP (and OA would be in use) Also the client ,might see a password prompt and/or a prompt to trust the new autodoscover website.

1
shiv4321•

You can try Kernel Migrator for Exchange software. It can help in Exchange to exchange migration, Exchange to Office 635 migration, Office 365 to Office 365 migration, etc.

1