O365 Migration: OnPrem A to O365 b w/barracudanetworks
-
@coliver said in O365 Migration: OnPrem A to O365 b w/barracudanetworks:
On-premises Exchange to Office 365 should be a no problem. The cloud filter (and the onsite appliance) both integrate with O365 very easily. Shouldn't be any different then a standard migration.
Shouldn't be - I agree..
However, I have yet to get O365 to Connect to the On-Prem.
-
@coliver said in O365 Migration: OnPrem A to O365 b w/barracudanetworks:
On-premises Exchange to Office 365 should be a no problem. The cloud filter (and the onsite appliance) both integrate with O365 very easily. Shouldn't be any different then a standard migration.
Even if the domain names are completely different?
At a minimum I would assume Gene needs to tell O365 how to map from one account to another.
-
The Spam service is not relevant.
You open the inbound firewall on site for 443 to forward to Exchange (it likely does already if they use OWA/OA)
The Office 365 migration stuff just uses OA/OWA functionality. I forget which.
-
@dashrender said in O365 Migration: OnPrem A to O365 b w/barracudanetworks:
@coliver said in O365 Migration: OnPrem A to O365 b w/barracudanetworks:
On-premises Exchange to Office 365 should be a no problem. The cloud filter (and the onsite appliance) both integrate with O365 very easily. Shouldn't be any different then a standard migration.
Even if the domain names are completely different?
At a minimum I would assume Gene needs to tell O365 how to map from one account to another.
IIRC you can add the new domain name as an alias to the existing Exchange environment. I haven't had to do this yet though.
-
@jaredbusch said in O365 Migration: OnPrem A to O365 b w/barracudanetworks:
You open the inbound firewall on site for 443 to forward to Exchange (it likely does already if they use OWA/OA)
Unless you use a proxy, then it points to your proxy instead.
-
@dashrender said in O365 Migration: OnPrem A to O365 b w/barracudanetworks:
@coliver said in O365 Migration: OnPrem A to O365 b w/barracudanetworks:
On-premises Exchange to Office 365 should be a no problem. The cloud filter (and the onsite appliance) both integrate with O365 very easily. Shouldn't be any different then a standard migration.
Even if the domain names are completely different?
This I think is the problem. I have never done this.
Changing during migration just makes my head hurt debating the disasters that could happen.
-
@dashrender said in O365 Migration: OnPrem A to O365 b w/barracudanetworks:
@jaredbusch said in O365 Migration: OnPrem A to O365 b w/barracudanetworks:
You open the inbound firewall on site for 443 to forward to Exchange (it likely does already if they use OWA/OA)
Unless you use a proxy, then it points to your proxy instead.
Proxy just forwards.
-
@coliver said in O365 Migration: OnPrem A to O365 b w/barracudanetworks:
@dashrender said in O365 Migration: OnPrem A to O365 b w/barracudanetworks:
@coliver said in O365 Migration: OnPrem A to O365 b w/barracudanetworks:
On-premises Exchange to Office 365 should be a no problem. The cloud filter (and the onsite appliance) both integrate with O365 very easily. Shouldn't be any different then a standard migration.
Even if the domain names are completely different?
At a minimum I would assume Gene needs to tell O365 how to map from one account to another.
IIRC you can add the new domain name as an alias to the existing Exchange environment. I haven't had to do this yet though.
Right - that would be the step I'm talking about.
-
@jaredbusch said in O365 Migration: OnPrem A to O365 b w/barracudanetworks:
@dashrender said in O365 Migration: OnPrem A to O365 b w/barracudanetworks:
@coliver said in O365 Migration: OnPrem A to O365 b w/barracudanetworks:
On-premises Exchange to Office 365 should be a no problem. The cloud filter (and the onsite appliance) both integrate with O365 very easily. Shouldn't be any different then a standard migration.
Even if the domain names are completely different?
This I think is the problem. I have never done this.
Changing during migration jsut makes my head hurt debating the disasters that could happen.
This is where I'm at. I didn't read that part about the different domain name. This could be an issue. I think there is documentation around for it but I'm not 100% positive.
-
@gjacobse said in O365 Migration: OnPrem A to O365 b w/barracudanetworks:
@dbeato said in O365 Migration: OnPrem A to O365 b w/barracudanetworks:
That means their email is going through Barracuda Cloud SPam FIltering. WHat tools will you be using? and how many users?
Very good question. Previously haven't needed any tools was able to go direct.
Right now it is about 100 accounts.
Use the cutover migration from Office 365 it connects directly to Exchange
https://support.office.com/en-us/article/Cutover-migration-to-Office-365-9496e93c-1e59-41a8-9bb3-6e8df0cd81b4 -
@dbeato said in O365 Migration: OnPrem A to O365 b w/barracudanetworks:
@gjacobse said in O365 Migration: OnPrem A to O365 b w/barracudanetworks:
@dbeato said in O365 Migration: OnPrem A to O365 b w/barracudanetworks:
That means their email is going through Barracuda Cloud SPam FIltering. WHat tools will you be using? and how many users?
Very good question. Previously haven't needed any tools was able to go direct.
Right now it is about 100 accounts.
Use the cutover migration from Office 365 it connects directly to Exchange
https://support.office.com/en-us/article/Cutover-migration-to-Office-365-9496e93c-1e59-41a8-9bb3-6e8df0cd81b4Different that I have been doing,.. but this is what I get:
The connection settings for this migration batch have been automatically selected based on the migration endpoints created in your organization. Learn moreThe connection settings for this migration batch have been automatically selected based on the migration endpoints created in your organization. Learn more Warning We couldn't detect your server settings. Please enter them. AutoDiscover failed with a configuration error: The migration service failed to detect the migration endpoint using the Autodiscover service. Consider using the Exchange Remote Connectivity Analyzer (https://testexchangeconnectivity.com) to diagnose the connectivity issues. Remote MRS proxy server: The FQDN of the Exchange server that the Mailbox Replication Service (MRS) Proxy is on -
@gjacobse said in O365 Migration: OnPrem A to O365 b w/barracudanetworks:
@dbeato said in O365 Migration: OnPrem A to O365 b w/barracudanetworks:
@gjacobse said in O365 Migration: OnPrem A to O365 b w/barracudanetworks:
@dbeato said in O365 Migration: OnPrem A to O365 b w/barracudanetworks:
That means their email is going through Barracuda Cloud SPam FIltering. WHat tools will you be using? and how many users?
Very good question. Previously haven't needed any tools was able to go direct.
Right now it is about 100 accounts.
Use the cutover migration from Office 365 it connects directly to Exchange
https://support.office.com/en-us/article/Cutover-migration-to-Office-365-9496e93c-1e59-41a8-9bb3-6e8df0cd81b4Different that I have been doing,.. but this is what I get:
The connection settings for this migration batch have been automatically selected based on the migration endpoints created in your organization. Learn moreThe connection settings for this migration batch have been automatically selected based on the migration endpoints created in your organization. Learn more Warning We couldn't detect your server settings. Please enter them. AutoDiscover failed with a configuration error: The migration service failed to detect the migration endpoint using the Autodiscover service. Consider using the Exchange Remote Connectivity Analyzer (https://testexchangeconnectivity.com) to diagnose the connectivity issues. Remote MRS proxy server: The FQDN of the Exchange server that the Mailbox Replication Service (MRS) Proxy is onSo check on the autodiscover DNS settings for that domain.
-
@JaredBusch OWA isn't used at all. All login to their client is through the spam filter.
-
@dustinb3403 said in O365 Migration: OnPrem A to O365 b w/barracudanetworks:
@JaredBusch OWA isn't used at all. All login to their client is through the spam filter.
Ah, while unusual, that makes it easy.
You setup a new DNS record that points to the Office's IP such as
migration.domain.comand then port forward 443 to the Exchange server.Finally go back to O365 Admin center and make a new migration. Magic will happen.
-
@jaredbusch said in O365 Migration: OnPrem A to O365 b w/barracudanetworks:
@dustinb3403 said in O365 Migration: OnPrem A to O365 b w/barracudanetworks:
@JaredBusch OWA isn't used at all. All login to their client is through the spam filter.
Ah, while unusual, that makes it easy.
You setup a new DNS record that points to the Office's IP such as
migration.domain.comand then port forward 443 to the Exchange server.Finally go back to O365 Admin center and make a new migration. Magic will happen.
This sounds like the way to go.
-
Will you be doing a cut over migration, hybrid, or something else?
-
@coliver said in O365 Migration: OnPrem A to O365 b w/barracudanetworks:
Will you be doing a cut over migration, hybrid, or something else?
AFAIunderstand - cutover.
-
Are they dumping the Barracuda when they go to o365? I did and the spam filtering was better on the o365 side. If that's the case, just make sure you have access to their DNS to change the MX records.
-
Two domains shouldn't be an issue. If both domains are added to o365, you can powershell the addition of aliases to the users mailboxes. o365 can accept email to either domain.
