Exchange Online Migration From POP3
-
This thread will be my only "homework" during my vacation...will come back on the 18th ready to start working on this...
-
@scottalanmiller what was the name of the DNS provider you mentioned recently?
I can't find the thread -
@Dashrender said:
@scottalanmiller what was the name of the DNS provider you mentioned recently?
I can't find the threadNetwork Solutions
-
@garak0410 said:
@Dashrender said:
@scottalanmiller what was the name of the DNS provider you mentioned recently?
I can't find the threadNetwork Solutions
Not yours - @scottalanmiller suggested one to me a few weeks ago. As you saw in his post a little while ago, he's against having Registrar, DNS and Web hosting done by the same company.
-
@Dashrender CloudFlare
-
@Dashrender said:
In both our situations you have to visit the workstations twice. Though in my setup all email from the time you touch the pc the first time starts arriving in your O365 account. One of my steps when making the new profile is to have the Outlook client connect to the POP3 account and through the Outlook client upload it to your O365 account.
In all situations, you will visit the workstation twice, there is no difference there, it seems to make the trips shorter the way I described. When we rolled out a new local Exchange server 3 years ago the existing email was POP3. I ran through both of these scenarios a few times and settled on the one I posted.
What is the point of making a new "clean" profile only to add the POP3 account back to it? Just keep the Outlook profile and add the Exchange account for Office 365. You can, if desired tell the POP3 to deliver to the Office 365 inbox at this time and also you could migrate the email, but because you still have a POP3 account in the profile, there is not really much of a point to doing that IMO.
-
-
Like DDNS? No.
-
Vacation is over and I am spending my Saturday Morning collating the advice in this thread and will post what I come up with and any questions I may have... thanks again everyone,.
-
@garak0410 Good luck!
-
Back at the office, ready to tackle this. @Dashrender and @JaredBusch ...both of you had great suggestions and I've collated the best of both of these into some steps for me to do this week.
So, the first thing to do would be to "pilot" my own email, correct, or at least another one?
And forgive me if I don't understand how the MX records work in reference to this question...if I follow the directions you both provided, I should be able to start with the quick start options on the portal right? They read as this:
quick start
The fast track to getting your pilot or basic deployment running
ā¢ Create new users and mailboxes.
ā¢ Share documents and collaborate online.
ā¢ Use web conferencing and instant messaging.
ā¢ Create documents by using Office applications.In these steps above, when I click NEXT, it does ask me if I want to use onmicrosoft.com or my own domain. Is it safe at this point to use my domain?
-
You can use your own domain (you'll need access to whomever is hosting your DNS for external access to confirm ownership -MS will have you create a record on the DNS server, that verifies that you have access to make changes, and therefore are considered an owner).
FYI/reminder, doing this does not allow delivery of mail to your O365 account, it only allows the possible sending of email from O365 assuming you don't have SPF records that might prevent it.
Once you create your profile on O365, configure your profile as suggested above (either JaredBucsh or my solution will work) and test test test.
-
@Dashrender said:
You can use your own domain (you'll need access to whomever is hosting your DNS for external access to confirm ownership -MS will have you create a record on the DNS server, that verifies that you have access to make changes, and therefore are considered an owner).
FYI/reminder, doing this does not allow delivery of mail to your O365 account, it only allows the possible sending of email from O365 assuming you don't have SPF records that might prevent it.
Once you create your profile on O365, configure your profile as suggested above (either JaredBucsh or my solution will work) and test test test.
Just so I understand you correctly and beg for your patience, on this O365 wizard where it asks me to use my domain:
I can pretty much go steps 1 and 2 safely right now, correct? And then do remaining steps this weekend?
-
Yes, you can do steps 1 and 2 without affecting your current users in anyway.
Who is providing DNS to the outside world for your email domain?
-
@Dashrender said:
Yes, you can do steps 1 and 2 without affecting your current users in anyway.
Who is providing DNS to the outside world for your email domain?
Our DNS is at Network Solutions. It lists all 4 of our owned domain names (though we just use the one for everything.) All 4 domain names point back to our current POP3/IMAP provider and website host. At the POP3/website provider, it has a ton of entries that cover Name, TTL, Class, Type, Record. When we leave the POP3 email provider, all of that will go away.
Under the name heading, we have things like:
domainname.com
localhost.domainname.com
mail.domainname.com
www.domainname.com
ftp.domainname.com
cpanel.domainname.com
whm.domainname.com
webmail.domainname.com
webdisk.domainname.com
autoconfig.domainname.com
autodiscover.domainname.comMost of these are configured with 14400 TTL, are with the CLASS IN, and TYPE A. The main.domainname and webmail.domainname are CNAME's. Most records are to a specified IP address with the CNAME's going to the domainname.com
-
Why will these things go away when you leave the POP3 provider? You should own the DNS solution, not the POP3 provider.
If you're logging into Network Solutions and see this, then you probably have access to change what you need to change.
Who are you buying O365 from? If they are not providing this type of support for you included in the move, I'd seriously consider going with another firm. I'm pretty sure that NTG will help you with all of this as an included service, but perhaps @Minion-Queen will correct me.
-
@Dashrender said:
Why will these things go away when you leave the POP3 provider? You should own the DNS solution, not the POP3 provider.
If you're logging into Network Solutions and see this, then you probably have access to change what you need to change.
Who are you buying O365 from? If they are not providing this type of support for you included in the move, I'd seriously consider going with another firm. I'm pretty sure that NTG will help you with all of this as an included service, but perhaps @Minion-Queen will correct me.
Those above domain and DNS settings are in the POP3 providers control panel...I should be able to easily add this to my settings with Network Solutions, correct?
Let me double check with the vendor I purchased this from...I know they quoted $5,000 for help but that may have been physical help here with Outlook profiles and such.
-
This is what they provide:
I actually scheduled the hour training for tomorrow, so hopefully, a lot of these DNS/MS issues will get ironed out.
-
WoW.. I love the 'value' they put on those services - what a load!
-
@garak0410 said:
Very good info guys and as Scott says, good "knowledge base" info.
Let me digress for a second...because I may end up needing help here...
Our domain name is registered with Network Solutions and is currently pointed to our POP3 provider who also hosts our webpage. The webpage actually has a pointer to our WIX page, which we have set in the POP3 providers control panel. So when the POP3 provider shuts down all of our services, do I simply point the domain to the Wix page or will this be a little more complicated with the MX records and such? Thanks...
This old post tells me that your DNS provider is really your POP3 provider, not Network Solutions. Which is it? If Network Solutions is pointing to your POP3, then you should change that to either Network Solutions or another provider that you have greater control of first (Scott suggests CacheCade - which is free for a low end account). This will take upwards of 3 days to propagate throughout the internet (but could be far less).
Once you move your DNS, then you can start on confirming the ownership with MS for O365.
