Exchange Online Migration From POP3



  • @JaredBusch said:

    @garak0410 said:

    And it is OK to proceed with CloudFlare now or better to wait until this evening?

    If everything is imported matching the POP3 provider, I would just do it now. because it will be transparent.

    Agreed, as long as the settings are all the same, computers on the internet won't really see a difference.



  • Here's a question that will help determine if you need to do more for autodiscover to work.

    Let's assume your domain is acme.com for email

    What is your domain name inside your network?

    If your domain name is acme.com, then you will need to add a DNS entry internally to your DNS server for autodiscover just like you did at cloudflare.

    If your domain name is something like acme.local, then you need to do nothing.



  • @Dashrender said:

    @JaredBusch said:

    @garak0410 said:

    And it is OK to proceed with CloudFlare now or better to wait until this evening?

    If everything is imported matching the POP3 provider, I would just do it now. because it will be transparent.

    Agreed, as long as the settings are all the same, computers on the internet won't really see a difference.

    I noticed CloudFlare did not bring over autoconfig and autodiscover of the POP3 provider DNS settings...will add those with my autodiscover for O365.



  • @garak0410 said:

    @Dashrender said:

    @JaredBusch said:

    @garak0410 said:

    And it is OK to proceed with CloudFlare now or better to wait until this evening?

    If everything is imported matching the POP3 provider, I would just do it now. because it will be transparent.

    Agreed, as long as the settings are all the same, computers on the internet won't really see a difference.

    I noticed CloudFlare did not bring over autoconfig and autodiscover of the POP3 provider DNS settings...will add those with my autodiscover for O365.

    Hit a snag...when adding the O365 autodiscover, it gave me this message:

    You cannot add a CNAME record when there is already an A, AAAA, or CNAME record with the same 'name' value

    The original autodiscover is an "A"...



  • @garak0410 said:

    I noticed CloudFlare did not bring over autoconfig and autodiscover of the POP3 provider DNS settings...will add those with my autodiscover for O365.

    How long ago did you add them? Assuming there is a poll feature in cloudflare so you can repoll the old DNS hosts, that should pull them, but personally, I'd simply open two windows side by side and compare, any that are missing, just add to cloudflare manually.



  • @garak0410 said:

    Hit a snag...when adding the O365 autodiscover, it gave me this message:

    You cannot add a CNAME record when there is already an A, AAAA, or CNAME record with the same 'name' value

    The original autodiscover is an "A"...

    So it is there. perhaps on a different page.



  • @Dashrender said:

    @garak0410 said:

    Hit a snag...when adding the O365 autodiscover, it gave me this message:

    You cannot add a CNAME record when there is already an A, AAAA, or CNAME record with the same 'name' value

    The original autodiscover is an "A"...

    So it is there. perhaps on a different page.

    I had to manually enter the autodiscover info from the existing POP3 provider into CloudFlare because it didn't carry over...did that...went to add the O365 AutoDiscover info and that's when I got the error...

    And both were entered autodiscover.domainname.com



  • @Dashrender

    Wondering if I should make the name autodiscover.outlook.com as well as the value, since I already have that autodiscover....or will that not work?



  • I've made the move to CloudFlare...just going to have to fix this autodiscover problem with O365



  • @garak0410 said:

    @Dashrender

    Wondering if I should make the name autodiscover.outlook.com as well as the value, since I already have that autodiscover....or will that not work?

    This won't work.
    When you configure Outlook it takes your domain name for example [email protected] and looks for a DNS entry at autodiscover.acme.com



  • @garak0410 said:

    I had to manually enter the autodiscover info from the existing POP3 provider into CloudFlare because it didn't carry over...did that...went to add the O365 AutoDiscover info and that's when I got the error...

    And both were entered autodiscover.domainname.com

    OK hold on a second.. was there an autodiscover record in your old POP3 CP? was it something like A record Autodiscover xxx.xxx.xxx.xxx?

    If so, you can't have two records with the same name. That old autodiscover record points to your old POP3 setup... You'll need to delete that record and create a new CNAME pointing to the one provided by O365.

    This shouldn't affect anything because the clients that need to talk to the old POP3 are already configured to connect to it (though I suppose that for some craziness, they could be trying to pickup mail from autodiscover.acme.com, and if that's the case, you will break receipt of new mail from the POP3 provider).

    Please confirm this by looking at the settings in one of your preconfigured Outlook clients.. what is the server name for POP3 and SMTP, make sure it's not autodiscover.somethingorother.com



  • @Dashrender said:

    @garak0410 said:

    I had to manually enter the autodiscover info from the existing POP3 provider into CloudFlare because it didn't carry over...did that...went to add the O365 AutoDiscover info and that's when I got the error...

    And both were entered autodiscover.domainname.com

    OK hold on a second.. was there an autodiscover record in your old POP3 CP? was it something like A record Autodiscover xxx.xxx.xxx.xxx?

    If so, you can't have two records with the same name. That old autodiscover record points to your old POP3 setup... You'll need to delete that record and create a new CNAME pointing to the one provided by O365.

    Correct...I brought over the old Autodiscover pointing to POP3...so it is safe to delete, add O365 and we can still receive POP3? And thanks for the patience...would rather be safe....



  • @Dashrender said:

    @garak0410 said:

    I had to manually enter the autodiscover info from the existing POP3 provider into CloudFlare because it didn't carry over...did that...went to add the O365 AutoDiscover info and that's when I got the error...

    And both were entered autodiscover.domainname.com

    OK hold on a second.. was there an autodiscover record in your old POP3 CP? was it something like A record Autodiscover xxx.xxx.xxx.xxx?

    If so, you can't have two records with the same name. That old autodiscover record points to your old POP3 setup... You'll need to delete that record and create a new CNAME pointing to the one provided by O365.

    This shouldn't affect anything because the clients that need to talk to the old POP3 are already configured to connect to it (though I suppose that for some craziness, they could be trying to pickup mail from autodiscover.acme.com, and if that's the case, you will break receipt of new mail from the POP3 provider).

    Please confirm this by looking at the settings in one of your preconfigured Outlook clients.. what is the server name for POP3 and SMTP, make sure it's not autodiscover.somethingorother.com

    They are all pointing to mail.domainname.com...so should be safe to delete and add the O365 autodiscover... 🙂



  • What is interesting now, is after I moved to CloudFlare and added all but the MX from O365, waited 15 minutes and clicked next in O365, it said it found the info except for MX records and autodiscover. However, a check of all my O365 records now show X's, even 30 minutes later...wonder why I found it at first (after 15 mins) but not now...



  • From your test machine, open a command prompt and type ping autodiscover.xyz.com does it resolve to outlook.xyz.com and then an IP?



  • @Dashrender said:

    From your test machine, open a command prompt and type ping autodiscover.xyz.com does it resolve to outlook.xyz.com and then an IP?

    Still points to the POP3...assuming it is still propagating...though I thought the SRV records would be updated by now... 😞



  • @Dashrender said:

    @scottalanmiller said:

    As always I highly recommend that DNS not be tied to a Registrar. The system is designed to protect you and putting the two together eliminates a critical separation of duties.

    Given that better DNS providers are free, why use the registrar?

    My recommendation is CloudFlare.

    I'm only working toward moving DNS back to his registrar for simplicity - I do understand your point on the separation.

    No simpler. More complex most likely. CloudFlare is so easy and has such a nice interface.



  • @garak0410 said:

    @Dashrender said:

    @JaredBusch said:

    @garak0410 said:

    And it is OK to proceed with CloudFlare now or better to wait until this evening?

    If everything is imported matching the POP3 provider, I would just do it now. because it will be transparent.

    Agreed, as long as the settings are all the same, computers on the internet won't really see a difference.

    I noticed CloudFlare did not bring over autoconfig and autodiscover of the POP3 provider DNS settings...will add those with my autodiscover for O365.

    DNS can't be completely auto-discovered. Always some manual bits unless you have nothing but email and www records.



  • @garak0410 said:

    @Dashrender

    Wondering if I should make the name autodiscover.outlook.com as well as the value, since I already have that autodiscover....or will that not work?

    Only use the identical entry to what Microsoft provides.



  • @garak0410 said:

    @Dashrender said:

    @garak0410 said:

    I had to manually enter the autodiscover info from the existing POP3 provider into CloudFlare because it didn't carry over...did that...went to add the O365 AutoDiscover info and that's when I got the error...

    And both were entered autodiscover.domainname.com

    OK hold on a second.. was there an autodiscover record in your old POP3 CP? was it something like A record Autodiscover xxx.xxx.xxx.xxx?

    If so, you can't have two records with the same name. That old autodiscover record points to your old POP3 setup... You'll need to delete that record and create a new CNAME pointing to the one provided by O365.

    Correct...I brought over the old Autodiscover pointing to POP3...so it is safe to delete, add O365 and we can still receive POP3? And thanks for the patience...would rather be safe....

    Yes. Necessary to delete the old, incorrect records.



  • Gonna move to another project for a short bit while I wait on propagation...just kind of excited to be close to the client end of this... 🙂



  • For reference, this is the screen I am looking at on 0365...it found these entries at first but can't see them now:

    dns03.jpg



  • O365 will fail the MX record check obviously until you change it.

    You don't need to worry about this page until you are ready to switch the MX record.

    From your test machine if when you ping autodiscover.companyname.com you get autodiscover.outlook.com then an IP address (if it doesn't specifically say autodiscover.outlook.com then just ping autodiscover.outlook.com and the IP's should be close if not identical - round robin DNS could give you a different address, but I would expect them to be somewhat close in range (though there is no reason for this to be the case - something I know Scott might point out))



  • @Dashrender said:

    O365 will fail the MX record check obviously until you change it.

    You don't need to worry about this page until you are ready to switch the MX record.

    From your test machine if when you ping autodiscover.companyname.com you get autodiscover.outlook.com then an IP address (if it doesn't specifically say autodiscover.outlook.com then just ping and the IP's should be close if not identical - round robin DNS could give you a different address, but I would expect them to be somewhat close in range (though there is no reason for this to be the case - something I know Scott might point out))

    Right...I was just wondering why I couldn't connect to Lync even and with it showing "X" on this page, made me wonder about the propagation.

    Pinging autodiscover.companyname.com still goes to the IP that was associated with my POP3...pinging autodiscover.outlook.com brings up autodiscover-namsouth.outlook.com and a 157. IP address...



  • Tom Petty's "The Waiting" just keeps going through my head as I wait to do more with this...at a standstill right now...



  • This could be why I am either confused or impatient...I see this screen shows where Lync and other O365 services are fine on the DNS...

    dns04.jpg

    Yet that other screen shot I provided shows problems with Lync...I thought I could actually test Lync right now...

    Also, if I proceed with setting up the clients, what is the email server name that I use? Just mail.domainame.com? Outlook.domainname.com? I thought I had asked that question but couldn't remember...and didn't find much help online...



  • What is your PC using for DNS? I assume one of your AD servers, what are they using for DNS upstream resolution?

    Try clearing the cache on your server, that might make it find the new internet DNS server faster.



  • Since O365 is now seeing the correct information for DNS records regarding Lync, once your PC does as well, it should work.



  • @Dashrender said:

    What is your PC using for DNS? I assume one of your AD servers, what are they using for DNS upstream resolution?

    Try clearing the cache on your server, that might make it find the new internet DNS server faster.

    @Dashrender said:

    Since O365 is now seeing the correct information for DNS records regarding Lync, once your PC does as well, it should work.

    Yes...our Domain Controller is also our DNS server...it still pings to the old autodiscover...and also did a test account setup in outlook for auto discovery and it still attempted to go back to the POP3.

    I just tried the Lync app on my phone via a 4G connection...can't find the server...so goes beyond our network?



  • Since chat is broken here, hit me up on google chat

    dashrender @ gmail dot cm

    yes the o is missing from com to keep the scammers at a bit of bay


Log in to reply