0

I'm in the process of migration from Exchange 2007 to Office 365.

It is going to be a slow migration, so I need to maintain both environments running.

What I've done for the first "migrated" mailboxes is to create the account at Office365, then create a redirection from Ex2007 to O365 using the .onmicrosoft.com email, which is the secondary smtp address.

It works properly for sendings and receptions, so using OWA or laptops outside domain is good.

The problem comes with Outlook installations inside domain.

I can't manage Outlook to look Office365 for connection. It always finds the Ex2007 user and establishes connection to it. I've done the trick of deleting primary SMTP address on Ex2007, establish connection to Office365 (it has worked) and after this, re-establish primary SMTP address to what it has to be (same address as O365), and after a couple of day, it again disconnects from ExOnline and looks to Ex2007.

How do you think I could manage this? Could I stablish a non top priority MX record pointing to O365 and the delete user from Ex2007, so that if email looks to Ex2007 and doesn't find it, retry to second MX record and find it at O365?

Please, any help would be great!!

Thank you!!!

2
  • I've done the trick of deleting primary SMTP address on Ex2007 - What trick is that exactly? Autodiscover and the SCP is what's causing this, not the primary SMTP address. – joeqwerty Mar 24 '17 at 11:16
  • Autodiscover is setup both at DNS inside domain and also at ISP DNS records. If I run Outlook and try to connect to a Office365 account, it doesn't look for it because account settings are auto introduced to the configuration of account. – JorgeD. Mar 24 '17 at 14:02
1

Simple question - why aren't you doing a hybrid with Office365?

The behaviour you are seeing is what I would expect, because Autodiscover will correct Outlook for you - as it is designed to do. You should really be doing a hybrid migration to Office365 in this scenario - I wouldn't have done it any other way.

1
  • The first reason I haven't done hybrid is because of the forest level, domain controller SO version and so on. The customer has a forest level of 2000, so I can't reach the minimum requirements for a hybrid scenario. – JorgeD. Mar 24 '17 at 13:58

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.