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

    O365 Migration: OnPrem A to O365 b w/barracudanetworks

    Scheduled Pinned Locked Moved IT Discussion
    26 Posts 7 Posters 2.8k Views
    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.
    • JaredBuschJ
      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
      • DashrenderD
        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
        • coliverC
          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
          • dbeatoD
            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

            gjacobseG 1 Reply Last reply Reply Quote 0
            • gjacobseG
              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
              
              dbeatoD 1 Reply Last reply Reply Quote 0
              • dbeatoD
                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
                • DustinB3403D
                  DustinB3403
                  last edited by

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

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

                    @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.com and then port forward 443 to the Exchange server.

                    Finally go back to O365 Admin center and make a new migration. Magic will happen.

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

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

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

                        Will you be doing a cut over migration, hybrid, or something else?

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

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

                          1 Reply Last reply Reply Quote 1
                          • Mike DavisM
                            Mike Davis
                            last edited by

                            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.

                            1 Reply Last reply Reply Quote 2
                            • Mike DavisM
                              Mike Davis
                              last edited by

                              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.

                              1 Reply Last reply Reply Quote 1
                              • 1
                              • 2
                              • 2 / 2
                              • First post
                                Last post