Exchange Online Migration From POP3
-
@garak0410 said:
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:
-
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...
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
-
Looks like MS will be doing a webinar for free next Tuesday.
http://www.microsoftvirtualacademy.com/liveevents/getting-the-most-out-of-your-office-365-trial
I think I'm going to try to attend myself.
-
Good Morning...
I woke up this morning, tried Lync on my phone and Wi-Fi connection with my main email and it worked...guess it was propagation. Got to work and after a few failed sign in attempts, was able to sign into Lync...looks like some major progress can be made today.
-
You were able to add O365 to your account following either Jared's or my instructions?
Just wondering, which are you doing?
-
@Dashrender said:
You were able to add O365 to your account following either Jared's or my instructions?
Just wondering, which are you doing?
I did some Lync accounts first...came into several "fires" I had to put out. I just added my O365 account with autodiscover and it works. So, currently, I have my POP3 and O365 account now in Outlook. I can get this set up for the rest of my users now and then, as you suggested, do the rest tomorrow night.
-
Questions about this:
- create new local Outlook profiles for everyone
a) connect users to O365
b) attach POP3 account to profile, delivery of the POP3 items needs to go to Office 365
Attach POP3 to profile, basically, ADD AN ACCOUNT, right? And then when you say delivery of the items needs to go to O365, what do you mean? Just to clarify...
- create new local Outlook profiles for everyone
-
Correct, you'll just be adding a new account to the new profile you just created.
When you add the the POP3 account, you'll have to add it manually. In the past you might have been able to use autoconfigure, but you've now changed autoconfigure to work with Office 365, so you will have to choose the manual option.
You'll need to follow this page to join the boxes into one.
http://www.msoutlook.info/question/520Now when you add the POP3 account, Outlook will create a new PST/OST for it. You don't want this - you'll need to follow the instructions on the above link to make sure delivery of new messages goes to Outlook.
In the past the default was to deliver all messages into a single store, either Exchange or a local PST (whatever you were using first). Looks like MS changed this behavior starting with Outlook 2010.
-
@Dashrender said:
Correct, you'll just be adding a new account to the new profile you just created.
When you add the the POP3 account, you'll have to add it manually. In the past you might have been able to use autoconfigure, but you've now changed autoconfigure to work with Office 365, so you will have to choose the manual option.
You'll need to follow this page to join the boxes into one.
http://www.msoutlook.info/question/520Now when you add the POP3 account, Outlook will create a new PST/OST for it. You don't want this - you'll need to follow the instructions on the above link to make sure delivery of new messages goes to Outlook.
In the past the default was to deliver all messages into a single store, either Exchange or a local PST (whatever you were using first). Looks like MS changed this behavior starting with Outlook 2010.
Thanks...doing this now...slow going though with everything else that is going on...
-
Odd...I've not touched DNS at all today...about 10 minutes ago, no one on POP3 can send/receive from Outlook...the POP3 provider is up, webmail is done, IMAP is done...just POP3 in Outlook...dead in the water and of course, people are blaming the conversion to Exchange...
