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

    Merger

    Scheduled Pinned Locked Moved IT Discussion
    121 Posts 9 Posters 30.5k 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.
    • scottalanmillerS
      scottalanmiller @StefUk
      last edited by

      @StefUk said:

      I get they should be merged .. but how can exchange - mailboxes etc work when company B moves to company A ?

      I'm unsure which aspect is worrying you. Do you mean in email routing to different @ addresses?

      StefUkS 1 Reply Last reply Reply Quote 0
      • Minion QueenM
        Minion Queen
        last edited by

        This would be a case to move them to Office 365 for their email portion at least. You can easily migrate them all over to O365 exchange and have multiple domains for people to be receiving at.

        scottalanmillerS 1 Reply Last reply Reply Quote 0
        • scottalanmillerS
          scottalanmiller @Minion Queen
          last edited by

          @Minion-Queen said:

          This would be a case to move them to Office 365 for their email portion at least. You can easily migrate them all over to O365 exchange and have multiple domains for people to be receiving at.

          They say that they have a dependency that O365 cannot address.

          J 1 Reply Last reply Reply Quote 0
          • Minion QueenM
            Minion Queen
            last edited by

            Is that for the MSOffice portion or email?

            scottalanmillerS 1 Reply Last reply Reply Quote 0
            • scottalanmillerS
              scottalanmiller @Minion Queen
              last edited by

              @Minion-Queen said:

              Is that for the MSOffice portion or email?

              Email

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

                @StefUk said:

                i think you have both hit a good point. The two scopes are different and I would want company B scope to change and bring it in line with company A. Re scoping and setting up a trusted domain binding should allow for the two infrastructure to coexist locally.

                You can do this work now. At company B, change the IP scheme to match the scheme at company A. Of course you'll need to audit company A first to make sure you don't create any overlap.

                1 Reply Last reply Reply Quote 0
                • StefUkS
                  StefUk @scottalanmiller
                  last edited by

                  @scottalanmiller said:

                  @StefUk said:

                  I get they should be merged .. but how can exchange - mailboxes etc work when company B moves to company A ?

                  I'm unsure which aspect is worrying you. Do you mean in email routing to different @ addresses?

                  the @ address is not the issue.

                  Once the clients pc of company B move to company A where they going to authenticate, resolve the dns for the exchange - mailbox etc ?

                  DashrenderD scottalanmillerS 2 Replies Last reply Reply Quote 0
                  • scottalanmillerS
                    scottalanmiller
                    last edited by

                    Trusted domain shoudl work fine... but is there a good reason not to merge AD right away? Just wondering, while a pain up front, this is not such a big place that it can't be done in a weekend and then things would be "just ready" for the future.

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

                      @StefUk said:

                      @scottalanmiller said:

                      @StefUk said:

                      I get they should be merged .. but how can exchange - mailboxes etc work when company B moves to company A ?

                      I'm unsure which aspect is worrying you. Do you mean in email routing to different @ addresses?

                      the @ address is not the issue.

                      Once the clients pc of company B move to company A where they going to authenticate, resolve the dns for the exchange - mailbox etc ?

                      You have to move ALL of the servers of company B to company A's datacenter... and put them on the network.

                      1 Reply Last reply Reply Quote 0
                      • scottalanmillerS
                        scottalanmiller @StefUk
                        last edited by

                        @StefUk said:

                        Once the clients pc of company B move to company A where they going to authenticate, resolve the dns for the exchange - mailbox etc ?

                        Wherever you tell them to 🙂 Decide how AD is going to be handled first, then deal with Exchange. But if you have a trust domain, just make the info the same. If you merge AD, then everything is done already.

                        StefUkS 1 Reply Last reply Reply Quote 0
                        • DashrenderD
                          Dashrender
                          last edited by

                          Company B PCs will still authenticate to Company B's domain controllers, at least until you move to over to company A's domain.

                          But moving them to A seems pointless since you said you want to create a new company called C. So just leave them on the domain they are on until you make company C domain and then move everyone.

                          StefUkS 1 Reply Last reply Reply Quote 0
                          • StefUkS
                            StefUk @scottalanmiller
                            last edited by

                            @scottalanmiller said:

                            @StefUk said:

                            Once the clients pc of company B move to company A where they going to authenticate, resolve the dns for the exchange - mailbox etc ?

                            Wherever you tell them to 🙂 Decide how AD is going to be handled first, then deal with Exchange. But if you have a trust domain, just make the info the same. If you merge AD, then everything is done already.

                            if we merge AD we wont be having this conversation haha ... 🙂
                            the AD merger it's something we need to think ... the complication there is that they want to become company C so need to reconnect all the client to that domain once done
                            s

                            scottalanmillerS DashrenderD 3 Replies Last reply Reply Quote 0
                            • scottalanmillerS
                              scottalanmiller @StefUk
                              last edited by

                              @StefUk said:

                              if we merge AD we wont be having this conversation haha ... 🙂

                              See, doesn't that make it simple?

                              StefUkS 1 Reply Last reply Reply Quote 0
                              • DashrenderD
                                Dashrender @StefUk
                                last edited by

                                @StefUk said:

                                @scottalanmiller said:

                                @StefUk said:

                                Once the clients pc of company B move to company A where they going to authenticate, resolve the dns for the exchange - mailbox etc ?

                                Wherever you tell them to 🙂 Decide how AD is going to be handled first, then deal with Exchange. But if you have a trust domain, just make the info the same. If you merge AD, then everything is done already.

                                if we merge AD we wont be having this conversation haha ... 🙂
                                the AD merger it's something we need to think ... the complication there is that they want to become company C so need to reconnect all the client to that domain once done
                                s

                                There are tools to do that.

                                Build a brand new AD from scratch, then use the MS tools to import your users over. There used to be tools for importing computers as well.

                                StefUkS 1 Reply Last reply Reply Quote 2
                                • scottalanmillerS
                                  scottalanmiller @StefUk
                                  last edited by

                                  @StefUk said:

                                  the AD merger it's something we need to think ... the complication there is that they want to become company C so need to reconnect all the client to that domain once done

                                  When I say "merge them now", I mean... into company C. Do it all, right now. Just just right to the end game and be done with it. I'm not saying that that is the answer, but I want to know why it isn't 🙂

                                  1 Reply Last reply Reply Quote 3
                                  • StefUkS
                                    StefUk @Dashrender
                                    last edited by

                                    @Dashrender said:

                                    Company B PCs will still authenticate to Company B's domain controllers, at least until you move to over to company A's domain.

                                    But moving them to A seems pointless since you said you want to create a new company called C. So just leave them on the domain they are on until you make company C domain and then move everyone.

                                    so i ll bring the servers from company B and plug them in to company A . As they have a separate subnet they will still work and see the old domain etc ?
                                    this is contingency plan in case we don t get everything done ..

                                    scottalanmillerS 1 Reply Last reply Reply Quote 0
                                    • scottalanmillerS
                                      scottalanmiller @StefUk
                                      last edited by

                                      @StefUk said:

                                      so i ll bring the servers from company B and plug them in to company A . As they have a separate subnet they will still work and see the old domain etc ?
                                      this is contingency plan in case we don t get everything done ..

                                      Yup, just about everything (except DHCP of course) will "just work" because it is on the IP layer. Things that won't work are things that are layer 2, like DHCP. No business function should be at that level, so not an issue.

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

                                        @scottalanmiller said:

                                        @StefUk said:

                                        so i ll bring the servers from company B and plug them in to company A . As they have a separate subnet they will still work and see the old domain etc ?
                                        this is contingency plan in case we don t get everything done ..

                                        Yup, just about everything (except DHCP of course) will "just work" because it is on the IP layer. Things that won't work are things that are layer 2, like DHCP. No business function should be at that level, so not an issue.

                                        Right DHCP will be the problem here. To solve this, you should change Company B to use the same IP range as company A NOW. As I've posted at least 3 times already. You'll need to make sure you audit the IPs in use at Company A and don't use those IPs when changing IPs at company B.
                                        Then when you bring it all over, you will just plug and go!.

                                        One other thing, you should make the firewall's be the same IP address at company B as Company A uses. This will be one less thing you would have to worry about when you move the equipment.

                                        StefUkS 1 Reply Last reply Reply Quote 0
                                        • StefUkS
                                          StefUk @scottalanmiller
                                          last edited by

                                          @scottalanmiller said:

                                          @StefUk said:

                                          if we merge AD we wont be having this conversation haha ... 🙂

                                          See, doesn't that make it simple?

                                          really simple .. the AD merger is not the issue. The issue is the time-scale with the legacy apps. If the "accounts" software is not merged and the two company cant use the merged one we will still need to use two separate systems until this happens. But company B needs to get out of the building in two month, legacy software working or not. This is why i am planning a contingency as no everything is dictated by us ( IT) . i asume we can migrate just that app 🙂

                                          DashrenderD scottalanmillerS 2 Replies Last reply Reply Quote 0
                                          • StefUkS
                                            StefUk @Dashrender
                                            last edited by

                                            @Dashrender said:

                                            @StefUk said:

                                            @scottalanmiller said:

                                            @StefUk said:

                                            Once the clients pc of company B move to company A where they going to authenticate, resolve the dns for the exchange - mailbox etc ?

                                            Wherever you tell them to 🙂 Decide how AD is going to be handled first, then deal with Exchange. But if you have a trust domain, just make the info the same. If you merge AD, then everything is done already.

                                            if we merge AD we wont be having this conversation haha ... 🙂
                                            the AD merger it's something we need to think ... the complication there is that they want to become company C so need to reconnect all the client to that domain once done
                                            s

                                            There are tools to do that.

                                            Build a brand new AD from scratch, then use the MS tools to import your users over. There used to be tools for importing computers as well.

                                            we will need to rejoin all the servers and clients to the new domain ? s

                                            1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 3
                                            • 4
                                            • 5
                                            • 6
                                            • 7
                                            • 1 / 7
                                            • First post
                                              Last post