ML
    • Register
    • Login
    • Search
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups

    O365 Migration: OnPrem A to O365 b w/barracudanetworks

    IT Discussion
    7
    26
    2208
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • gjacobse
      gjacobse last edited by

      Working with a Office 365 migration. Client On prem is one domain, and o365 side is a different domain. Also in the mix is that the MX record points to server01.id.barracudanetworks.com.

      In the past my experience is Domain 1 to Domain 1 migration - so I've not had issues... This is a whole nother best.

      1 Reply Last reply Reply Quote 0
      • gjacobse
        gjacobse last edited by

        How do you connect o365 migration to Barracude Email Essentials?

        1 Reply Last reply Reply Quote 0
        • coliver
          coliver last edited by

          What is onprem?

          gjacobse 1 Reply Last reply Reply Quote 0
          • gjacobse
            gjacobse @coliver last edited by

            @coliver said in O365 Migration: OnPrem A to O365 b w/barracudanetworks:

            What is onprem?

            On Premise Exchange

            1 Reply Last reply Reply Quote 0
            • dbeato
              dbeato last edited by

              That means their email is going through Barracuda Cloud SPam FIltering. WHat tools will you be using? and how many users?

              gjacobse 1 Reply Last reply Reply Quote 0
              • gjacobse
                gjacobse @dbeato last edited by

                @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.

                dbeato 1 Reply Last reply Reply Quote 0
                • coliver
                  coliver last edited by

                  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.

                  gjacobse Dashrender 2 Replies Last reply Reply Quote 0
                  • gjacobse
                    gjacobse @coliver last edited by

                    @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.

                    1 Reply Last reply Reply Quote 0
                    • Dashrender
                      Dashrender @coliver last edited by

                      @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.

                      coliver JaredBusch 2 Replies Last reply Reply Quote 0
                      • JaredBusch
                        JaredBusch last edited by

                        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 1 Reply Last reply Reply Quote 0
                        • coliver
                          coliver @Dashrender last edited by

                          @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.

                          Dashrender 1 Reply Last reply Reply Quote 0
                          • Dashrender
                            Dashrender @JaredBusch last edited by

                            @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.

                            JaredBusch 1 Reply Last reply Reply Quote 0
                            • JaredBusch
                              JaredBusch @Dashrender last edited by JaredBusch

                              @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.

                              coliver 1 Reply Last reply Reply Quote 2
                              • JaredBusch
                                JaredBusch @Dashrender last edited by

                                @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.

                                1 Reply Last reply Reply Quote 0
                                • Dashrender
                                  Dashrender @coliver last edited by

                                  @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.

                                  1 Reply Last reply Reply Quote 0
                                  • coliver
                                    coliver @JaredBusch last edited by

                                    @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.

                                    1 Reply Last reply Reply Quote 1
                                    • dbeato
                                      dbeato @gjacobse last edited by

                                      @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

                                      gjacobse 1 Reply Last reply Reply Quote 0
                                      • gjacobse
                                        gjacobse @dbeato last edited by

                                        @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-6e8df0cd81b4

                                        Different 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
                                        
                                        dbeato 1 Reply Last reply Reply Quote 0
                                        • dbeato
                                          dbeato @gjacobse last edited by

                                          @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-6e8df0cd81b4

                                          Different 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
                                          

                                          So check on the autodiscover DNS settings for that domain.

                                          1 Reply Last reply Reply Quote 0
                                          • DustinB3403
                                            DustinB3403 last edited by

                                            @JaredBusch OWA isn't used at all. All login to their client is through the spam filter.

                                            JaredBusch 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post