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

    Active Directory Migration

    IT Discussion
    6
    30
    3.1k
    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.
    • J
      Joel @scottalanmiller
      last edited by

      @scottalanmiller said:

      @Joel said:

      Would you suggest 1st step I install Hyper V on the new 2012 server, then backup the data on the SBS. Then create a VM on the 2012 and promote that as a DC?

      • Install Hyper-V
      • Create two VMs (one for AD, one for FS)
      • Join AD to the Domain
      • Remove AD on the old instance with only SBS and this new AD VM remaining
      • Migrate all file shares to the new FS VM
      • Turn off everything but AD on the SBS machine
      • Promote the 2012 R2 AD VM to forest root
      • Have bonfire and roast marshmallows around the burning remains of the SBS box

      I actually LOL'd at the last comment

      That leaves me to ask - How do I remove AD on the old SBS? I cant recall!!! (point 4 above)
      When I promote the 2012 to Forest root, will that migrate the AD info?

      1 Reply Last reply Reply Quote 0
      • S
        scottalanmiller
        last edited by

        Do a dcpromote just to be sure, but the forest root move should trigger it anyway.

        1 Reply Last reply Reply Quote 0
        • J
          JaredBusch
          last edited by JaredBusch

          I would start by removing the new server again and formatting it.

          Install Hyper-V server
          Join to domain
          Create new VM1
          Join VM1 to domain
          Make VM1 a DC
          Create VM2
          Join VM2 to domain
          Move shares to VM2
          Move DHCP to VM1
          Shut down SBS and confirm everything works
          Turn SBS on, and transfer FSMO to VM1
          Remove SBS from domain
          Turn off box
          Burn box

          C D S D 4 Replies Last reply Reply Quote 1
          • C
            coliver @JaredBusch
            last edited by

            @JaredBusch said:

            I would start by removing the new server again and fiormatting it.

            Install Hyper-V server
            Join to domain
            Create new VM1
            Join VM1 to domain
            Make VM1 a DC
            Create VM2
            Join VM2 to domain
            Move shares to VM2
            Move DHCP to VM1
            Shut down SBS and confirm everything works
            Turn SBS on, and transfer FSMO to VM1
            Remove SBS from domain
            Turn off box
            Burn box

            From what @scottalanmiller is saying once you join another DC to a SBS domain the SBS server refuses to work correctly. Meaning you could potentially lose the file share etc.

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

              @JaredBusch said:

              I would start by removing the new server again and fiormatting it.

              What's "fiormatting"?

              1 Reply Last reply Reply Quote 0
              • D
                Dashrender
                last edited by

                You do get something like 21 days before SBS will disable itself. It's not Promote second DC and BAM, the SBS crashes. You do get some time to migrate the rest of stuff off.

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

                  @coliver said:

                  From what @scottalanmiller is saying once you join another DC to a SBS domain the SBS server refuses to work correctly. Meaning you could potentially lose the file share etc.

                  No, that is not what @scottalanmiller said, nor is it how SBS works.

                  SBS must be the FSMO role holder. That is the only requirement to keep a SBS server functioning correctly.

                  You can join and remove as many other DC's as you want.

                  This is not knew and is how SBS worked for its entire lifespan from SBS2003 through SBS2011

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

                    @scottalanmiller said:

                    @Dashrender said:

                    @scottalanmiller said:

                    Agree with virtualizing.

                    What the "old guy" did is not that bad. He put in a new DC, he just did not decom the old system. As there are only two systems, I would not have expected him to, really.

                    Is the current system much of a problem? I would consider holding off on a new install until 2016 is available if it is not a major concern right now.

                    How does he get 2016 though? I'm assuming they bought either an OEM 2012 license with the hardware, or less likely, they bought a FPP license. They'd have to buy an upgrade to move to 2016.

                    By waiting.

                    The purchase was already made.

                    J S 2 Replies Last reply Reply Quote 1
                    • J
                      JaredBusch @Dashrender
                      last edited by

                      @Dashrender said:

                      @scottalanmiller said:

                      @Dashrender said:

                      @scottalanmiller said:

                      Agree with virtualizing.

                      What the "old guy" did is not that bad. He put in a new DC, he just did not decom the old system. As there are only two systems, I would not have expected him to, really.

                      Is the current system much of a problem? I would consider holding off on a new install until 2016 is available if it is not a major concern right now.

                      How does he get 2016 though? I'm assuming they bought either an OEM 2012 license with the hardware, or less likely, they bought a FPP license. They'd have to buy an upgrade to move to 2016.

                      By waiting.

                      The purchase was already made.

                      Exactly. This is already owned equipment/licensing.

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

                        @JaredBusch said:

                        I would start by removing the new server again and formatting it.

                        Install Hyper-V server
                        Join to domain
                        Create new VM1
                        Join VM1 to domain
                        Make VM1 a DC
                        Create VM2
                        Join VM2 to domain
                        Move shares to VM2
                        Move DHCP to VM1
                        Shut down SBS and confirm everything works
                        Turn SBS on, and transfer FSMO to VM1
                        Remove SBS from domain
                        Turn off box
                        Burn box

                        I agree, start fresh. If nothing critical is there, do this 100% fresh with 100% "known to you" and documented.

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

                          @JaredBusch said:

                          I would start by removing the new server again and formatting it.

                          Install Hyper-V server
                          Join to domain
                          Create new VM1
                          Join VM1 to domain
                          Make VM1 a DC
                          Create VM2
                          Join VM2 to domain
                          Move shares to VM2
                          Move DHCP to VM1
                          Shut down SBS and confirm everything works
                          Turn SBS on, and transfer FSMO to VM1
                          Remove SBS from domain
                          Turn off box
                          Burn box

                          This means he needs another place to put the data that was moved to this server in the mean time.

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

                            @Dashrender said:

                            @scottalanmiller said:

                            @Dashrender said:

                            @scottalanmiller said:

                            Agree with virtualizing.

                            What the "old guy" did is not that bad. He put in a new DC, he just did not decom the old system. As there are only two systems, I would not have expected him to, really.

                            Is the current system much of a problem? I would consider holding off on a new install until 2016 is available if it is not a major concern right now.

                            How does he get 2016 though? I'm assuming they bought either an OEM 2012 license with the hardware, or less likely, they bought a FPP license. They'd have to buy an upgrade to move to 2016.

                            By waiting.

                            The purchase was already made.

                            Oh, of the OS as well, right. Makes sense. Sorry.

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

                              @Dashrender said:

                              This means he needs another place to put the data that was moved to this server in the mean time.

                              Yes, he can simply move it back to the original server.

                              The problem with keeping the existing server as setup is that it has other roles and those roles means that it takes one of the licenses.

                              @Joel It is an all around bad setup. Tell the client honestly how f[moderated] up it is. Tell them they were taken for a ride. Tell them you can fix it. Tell them how much time it will take and get money up front. It is not your fault they have to throw good money after bad. That is why they are looking for you anyway.

                              1 Reply Last reply Reply Quote 0
                              • D
                                Dashrender
                                last edited by

                                Was it the best option, no of course not, but was it really so horrible either? not really.

                                What roles does the other server have right now other than file server? Even if it is a DC, that's easily fixed, just DCPROMO it down - problem solved.

                                Granted, I'm totally for the scrap and start over - the current situation also isn't the end of the world.

                                Another question - What type of backup solution does this potential client have? how much data is on the server?
                                What makes anyone think the old server is dieing?

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