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

    Where do I start with replacing the whole MS AD stack

    Water Closet
    microsoft active directory ad dhcp dns
    8
    104
    8.8k
    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 @Dashrender
      last edited by

      @Dashrender said in Where do I start with replacing the whole MS AD stack:

      @JaredBusch said in Where do I start with replacing the whole MS AD stack:

      @scottalanmiller said in Where do I start with replacing the whole MS AD stack:

      @JaredBusch said in Where do I start with replacing the whole MS AD stack:

      @Donahue said in Where do I start with replacing the whole MS AD stack:

      its the device or user making the request to the DNS service.

      The only device making a request to the Windows DNS service is the other DNS server.

      Correct, but that's not the basis for the licensing requirement. Anything that uses that DNS downstream is getting it from an "agregator" to the Windows service and therefore needs the CAL.

      If that is the actual term of theri license, then, yet another reason to move on to this with the target of getting to no AD agian.

      I don't think you need to be that dramatic.

      You can manage two networks - one for Windows stuff - that's all licensed up, and another for everything else (or possibly two others - one corporate and one guest). the other networks of course would use non windows services to service devices/users.

      Can, but it is very difficult to do and a huge pain.

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

        @scottalanmiller said in Where do I start with replacing the whole MS AD stack:

        @Dashrender said in Where do I start with replacing the whole MS AD stack:

        @JaredBusch said in Where do I start with replacing the whole MS AD stack:

        @scottalanmiller said in Where do I start with replacing the whole MS AD stack:

        @JaredBusch said in Where do I start with replacing the whole MS AD stack:

        @Donahue said in Where do I start with replacing the whole MS AD stack:

        its the device or user making the request to the DNS service.

        The only device making a request to the Windows DNS service is the other DNS server.

        Correct, but that's not the basis for the licensing requirement. Anything that uses that DNS downstream is getting it from an "agregator" to the Windows service and therefore needs the CAL.

        If that is the actual term of theri license, then, yet another reason to move on to this with the target of getting to no AD agian.

        I don't think you need to be that dramatic.

        You can manage two networks - one for Windows stuff - that's all licensed up, and another for everything else (or possibly two others - one corporate and one guest). the other networks of course would use non windows services to service devices/users.

        Can, but it is very difficult to do and a huge pain.

        It's not that difficult to setup two networks - but I'll agree it's a pain managing it, mainly because you have to manage it, not because it would be that difficult.

        DustinB3403D scottalanmillerS 2 Replies Last reply Reply Quote 0
        • DustinB3403D
          DustinB3403 @Dashrender
          last edited by

          @Dashrender said in Where do I start with replacing the whole MS AD stack:

          @scottalanmiller said in Where do I start with replacing the whole MS AD stack:

          @Dashrender said in Where do I start with replacing the whole MS AD stack:

          @JaredBusch said in Where do I start with replacing the whole MS AD stack:

          @scottalanmiller said in Where do I start with replacing the whole MS AD stack:

          @JaredBusch said in Where do I start with replacing the whole MS AD stack:

          @Donahue said in Where do I start with replacing the whole MS AD stack:

          its the device or user making the request to the DNS service.

          The only device making a request to the Windows DNS service is the other DNS server.

          Correct, but that's not the basis for the licensing requirement. Anything that uses that DNS downstream is getting it from an "agregator" to the Windows service and therefore needs the CAL.

          If that is the actual term of theri license, then, yet another reason to move on to this with the target of getting to no AD agian.

          I don't think you need to be that dramatic.

          You can manage two networks - one for Windows stuff - that's all licensed up, and another for everything else (or possibly two others - one corporate and one guest). the other networks of course would use non windows services to service devices/users.

          Can, but it is very difficult to do and a huge pain.

          It's not that difficult to setup two networks - but I'll agree it's a pain managing it.

          Of course it's a huge pane to setup dual networks. . .

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

            @Dashrender said in Where do I start with replacing the whole MS AD stack:

            @scottalanmiller said in Where do I start with replacing the whole MS AD stack:

            @Dashrender said in Where do I start with replacing the whole MS AD stack:

            @JaredBusch said in Where do I start with replacing the whole MS AD stack:

            @scottalanmiller said in Where do I start with replacing the whole MS AD stack:

            @JaredBusch said in Where do I start with replacing the whole MS AD stack:

            @Donahue said in Where do I start with replacing the whole MS AD stack:

            its the device or user making the request to the DNS service.

            The only device making a request to the Windows DNS service is the other DNS server.

            Correct, but that's not the basis for the licensing requirement. Anything that uses that DNS downstream is getting it from an "agregator" to the Windows service and therefore needs the CAL.

            If that is the actual term of theri license, then, yet another reason to move on to this with the target of getting to no AD agian.

            I don't think you need to be that dramatic.

            You can manage two networks - one for Windows stuff - that's all licensed up, and another for everything else (or possibly two others - one corporate and one guest). the other networks of course would use non windows services to service devices/users.

            Can, but it is very difficult to do and a huge pain.

            It's not that difficult to setup two networks - but I'll agree it's a pain managing it, mainly because you have to manage it, not because it would be that difficult.

            It is most of the effort of running two companies and maintaining two skill sets. It is nearly a doubling of the effort of just running one.

            DashrenderD 1 Reply Last reply Reply Quote 0
            • DonahueD
              Donahue
              last edited by

              Ok, DHCP is switched over. It's currently just pointing the DNS to the existing DNS servers.

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

                @Donahue said in Where do I start with replacing the whole MS AD stack:

                Ok, DHCP is switched over. It's currently just pointing the DNS to the existing DNS servers.

                Right. Now you can work on setting up your DHCP reservation, and migrating all the static IP junk to reservations.

                Once that is done, you can work towards changing DNS.

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

                  @scottalanmiller said in Where do I start with replacing the whole MS AD stack:

                  @Dashrender said in Where do I start with replacing the whole MS AD stack:

                  @scottalanmiller said in Where do I start with replacing the whole MS AD stack:

                  @Dashrender said in Where do I start with replacing the whole MS AD stack:

                  @JaredBusch said in Where do I start with replacing the whole MS AD stack:

                  @scottalanmiller said in Where do I start with replacing the whole MS AD stack:

                  @JaredBusch said in Where do I start with replacing the whole MS AD stack:

                  @Donahue said in Where do I start with replacing the whole MS AD stack:

                  its the device or user making the request to the DNS service.

                  The only device making a request to the Windows DNS service is the other DNS server.

                  Correct, but that's not the basis for the licensing requirement. Anything that uses that DNS downstream is getting it from an "agregator" to the Windows service and therefore needs the CAL.

                  If that is the actual term of theri license, then, yet another reason to move on to this with the target of getting to no AD agian.

                  I don't think you need to be that dramatic.

                  You can manage two networks - one for Windows stuff - that's all licensed up, and another for everything else (or possibly two others - one corporate and one guest). the other networks of course would use non windows services to service devices/users.

                  Can, but it is very difficult to do and a huge pain.

                  It's not that difficult to setup two networks - but I'll agree it's a pain managing it, mainly because you have to manage it, not because it would be that difficult.

                  It is most of the effort of running two companies and maintaining two skill sets. It is nearly a doubling of the effort of just running one.

                  I do this right now for my guest network... and so does just about anyone else out there who have completely separate networks for guests.

                  Is it crazy to do this for the corporate side - yeah I think so, but I also think percentage wise it's pretty low the amount of companies that have many times the number of employees compared to endpoint devices to the point where you wouldn't just CAL every user to even make this an issue.

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

                    @JaredBusch said in Where do I start with replacing the whole MS AD stack:

                    @Donahue said in Where do I start with replacing the whole MS AD stack:

                    Ok, DHCP is switched over. It's currently just pointing the DNS to the existing DNS servers.

                    Right. Now you can work on setting up your DHCP reservation, and migrating all the static IP junk to reservations.

                    Once that is done, you can work towards changing DNS.

                    yeah, that will take awhile.

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

                      @Donahue said in Where do I start with replacing the whole MS AD stack:

                      @JaredBusch said in Where do I start with replacing the whole MS AD stack:

                      @Donahue said in Where do I start with replacing the whole MS AD stack:

                      Ok, DHCP is switched over. It's currently just pointing the DNS to the existing DNS servers.

                      Right. Now you can work on setting up your DHCP reservation, and migrating all the static IP junk to reservations.

                      Once that is done, you can work towards changing DNS.

                      yeah, that will take awhile.

                      really? Your DHCP server doesn't have an option to just add an existing lease to the reservation table?

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

                        @Dashrender said in Where do I start with replacing the whole MS AD stack:

                        @Donahue said in Where do I start with replacing the whole MS AD stack:

                        @JaredBusch said in Where do I start with replacing the whole MS AD stack:

                        @Donahue said in Where do I start with replacing the whole MS AD stack:

                        Ok, DHCP is switched over. It's currently just pointing the DNS to the existing DNS servers.

                        Right. Now you can work on setting up your DHCP reservation, and migrating all the static IP junk to reservations.

                        Once that is done, you can work towards changing DNS.

                        yeah, that will take awhile.

                        really? Your DHCP server doesn't have an option to just add an existing lease to the reservation table?

                        It's easy to create reservations. It's another thing entirely to migrate over devices from static to DHCP, while also changing their ip.

                        DashrenderD DustinB3403D 2 Replies Last reply Reply Quote 0
                        • DashrenderD
                          Dashrender @Donahue
                          last edited by

                          @Donahue said in Where do I start with replacing the whole MS AD stack:

                          @Dashrender said in Where do I start with replacing the whole MS AD stack:

                          @Donahue said in Where do I start with replacing the whole MS AD stack:

                          @JaredBusch said in Where do I start with replacing the whole MS AD stack:

                          @Donahue said in Where do I start with replacing the whole MS AD stack:

                          Ok, DHCP is switched over. It's currently just pointing the DNS to the existing DNS servers.

                          Right. Now you can work on setting up your DHCP reservation, and migrating all the static IP junk to reservations.

                          Once that is done, you can work towards changing DNS.

                          yeah, that will take awhile.

                          really? Your DHCP server doesn't have an option to just add an existing lease to the reservation table?

                          It's easy to create reservations. It's another thing entirely to migrate over devices from static to DHCP, while also changing their ip.

                          aww - well, that's definitely true!

                          1 Reply Last reply Reply Quote 0
                          • DustinB3403D
                            DustinB3403 @Donahue
                            last edited by

                            @Donahue said in Where do I start with replacing the whole MS AD stack:

                            @Dashrender said in Where do I start with replacing the whole MS AD stack:

                            @Donahue said in Where do I start with replacing the whole MS AD stack:

                            @JaredBusch said in Where do I start with replacing the whole MS AD stack:

                            @Donahue said in Where do I start with replacing the whole MS AD stack:

                            Ok, DHCP is switched over. It's currently just pointing the DNS to the existing DNS servers.

                            Right. Now you can work on setting up your DHCP reservation, and migrating all the static IP junk to reservations.

                            Once that is done, you can work towards changing DNS.

                            yeah, that will take awhile.

                            really? Your DHCP server doesn't have an option to just add an existing lease to the reservation table?

                            It's easy to create reservations. It's another thing entirely to migrate over devices from static to DHCP, while also changing their ip.

                            You could just create reservations in the new DHCP server and have the existing windows DHCP server not renew requests.

                            DonahueD DashrenderD 2 Replies Last reply Reply Quote 0
                            • DonahueD
                              Donahue @DustinB3403
                              last edited by

                              @DustinB3403 said in Where do I start with replacing the whole MS AD stack:

                              @Donahue said in Where do I start with replacing the whole MS AD stack:

                              @Dashrender said in Where do I start with replacing the whole MS AD stack:

                              @Donahue said in Where do I start with replacing the whole MS AD stack:

                              @JaredBusch said in Where do I start with replacing the whole MS AD stack:

                              @Donahue said in Where do I start with replacing the whole MS AD stack:

                              Ok, DHCP is switched over. It's currently just pointing the DNS to the existing DNS servers.

                              Right. Now you can work on setting up your DHCP reservation, and migrating all the static IP junk to reservations.

                              Once that is done, you can work towards changing DNS.

                              yeah, that will take awhile.

                              really? Your DHCP server doesn't have an option to just add an existing lease to the reservation table?

                              It's easy to create reservations. It's another thing entirely to migrate over devices from static to DHCP, while also changing their ip.

                              You could just create reservations in the new DHCP server and have the existing windows DHCP server not renew requests.

                              I think you missed the point.

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

                                @DustinB3403 said in Where do I start with replacing the whole MS AD stack:

                                @Donahue said in Where do I start with replacing the whole MS AD stack:

                                @Dashrender said in Where do I start with replacing the whole MS AD stack:

                                @Donahue said in Where do I start with replacing the whole MS AD stack:

                                @JaredBusch said in Where do I start with replacing the whole MS AD stack:

                                @Donahue said in Where do I start with replacing the whole MS AD stack:

                                Ok, DHCP is switched over. It's currently just pointing the DNS to the existing DNS servers.

                                Right. Now you can work on setting up your DHCP reservation, and migrating all the static IP junk to reservations.

                                Once that is done, you can work towards changing DNS.

                                yeah, that will take awhile.

                                really? Your DHCP server doesn't have an option to just add an existing lease to the reservation table?

                                It's easy to create reservations. It's another thing entirely to migrate over devices from static to DHCP, while also changing their ip.

                                You could just create reservations in the new DHCP server and have the existing windows DHCP server not renew requests.

                                He's changing static IP'ed devices to DHCP with reservations.

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

                                  @Dashrender said in Where do I start with replacing the whole MS AD stack:

                                  @DustinB3403 said in Where do I start with replacing the whole MS AD stack:

                                  @Donahue said in Where do I start with replacing the whole MS AD stack:

                                  @Dashrender said in Where do I start with replacing the whole MS AD stack:

                                  @Donahue said in Where do I start with replacing the whole MS AD stack:

                                  @JaredBusch said in Where do I start with replacing the whole MS AD stack:

                                  @Donahue said in Where do I start with replacing the whole MS AD stack:

                                  Ok, DHCP is switched over. It's currently just pointing the DNS to the existing DNS servers.

                                  Right. Now you can work on setting up your DHCP reservation, and migrating all the static IP junk to reservations.

                                  Once that is done, you can work towards changing DNS.

                                  yeah, that will take awhile.

                                  really? Your DHCP server doesn't have an option to just add an existing lease to the reservation table?

                                  It's easy to create reservations. It's another thing entirely to migrate over devices from static to DHCP, while also changing their ip.

                                  You could just create reservations in the new DHCP server and have the existing windows DHCP server not renew requests.

                                  He's changing static IP'ed devices to DHCP with reservations.

                                  Are you agreeing with me or stating something Donohue is doing?

                                  DonahueD DashrenderD 2 Replies Last reply Reply Quote 0
                                  • DonahueD
                                    Donahue @DustinB3403
                                    last edited by

                                    @DustinB3403 said in Where do I start with replacing the whole MS AD stack:

                                    @Dashrender said in Where do I start with replacing the whole MS AD stack:

                                    @DustinB3403 said in Where do I start with replacing the whole MS AD stack:

                                    @Donahue said in Where do I start with replacing the whole MS AD stack:

                                    @Dashrender said in Where do I start with replacing the whole MS AD stack:

                                    @Donahue said in Where do I start with replacing the whole MS AD stack:

                                    @JaredBusch said in Where do I start with replacing the whole MS AD stack:

                                    @Donahue said in Where do I start with replacing the whole MS AD stack:

                                    Ok, DHCP is switched over. It's currently just pointing the DNS to the existing DNS servers.

                                    Right. Now you can work on setting up your DHCP reservation, and migrating all the static IP junk to reservations.

                                    Once that is done, you can work towards changing DNS.

                                    yeah, that will take awhile.

                                    really? Your DHCP server doesn't have an option to just add an existing lease to the reservation table?

                                    It's easy to create reservations. It's another thing entirely to migrate over devices from static to DHCP, while also changing their ip.

                                    You could just create reservations in the new DHCP server and have the existing windows DHCP server not renew requests.

                                    He's changing static IP'ed devices to DHCP with reservations.

                                    Are you agreeing with me or stating something Donohue is doing?

                                    he's telling you what I need to do.

                                    DustinB3403D 1 Reply Last reply Reply Quote 0
                                    • travisdh1T
                                      travisdh1
                                      last edited by

                                      🍿

                                      1 Reply Last reply Reply Quote 0
                                      • DustinB3403D
                                        DustinB3403 @Donahue
                                        last edited by

                                        @Donahue said in Where do I start with replacing the whole MS AD stack:

                                        @DustinB3403 said in Where do I start with replacing the whole MS AD stack:

                                        @Dashrender said in Where do I start with replacing the whole MS AD stack:

                                        @DustinB3403 said in Where do I start with replacing the whole MS AD stack:

                                        @Donahue said in Where do I start with replacing the whole MS AD stack:

                                        @Dashrender said in Where do I start with replacing the whole MS AD stack:

                                        @Donahue said in Where do I start with replacing the whole MS AD stack:

                                        @JaredBusch said in Where do I start with replacing the whole MS AD stack:

                                        @Donahue said in Where do I start with replacing the whole MS AD stack:

                                        Ok, DHCP is switched over. It's currently just pointing the DNS to the existing DNS servers.

                                        Right. Now you can work on setting up your DHCP reservation, and migrating all the static IP junk to reservations.

                                        Once that is done, you can work towards changing DNS.

                                        yeah, that will take awhile.

                                        really? Your DHCP server doesn't have an option to just add an existing lease to the reservation table?

                                        It's easy to create reservations. It's another thing entirely to migrate over devices from static to DHCP, while also changing their ip.

                                        You could just create reservations in the new DHCP server and have the existing windows DHCP server not renew requests.

                                        He's changing static IP'ed devices to DHCP with reservations.

                                        Are you agreeing with me or stating something Donohue is doing?

                                        he's telling you what I need to do.

                                        I think you missed my point.

                                        You can create a reservation on the new DHCP server and have it waiting, turn off the old DHCP server. Then just go to the clients and set them to DHCP.

                                        Walah, reservations active.

                                        DashrenderD JaredBuschJ scottalanmillerS 3 Replies Last reply Reply Quote 0
                                        • DashrenderD
                                          Dashrender @DustinB3403
                                          last edited by

                                          @DustinB3403 said in Where do I start with replacing the whole MS AD stack:

                                          @Dashrender said in Where do I start with replacing the whole MS AD stack:

                                          @DustinB3403 said in Where do I start with replacing the whole MS AD stack:

                                          @Donahue said in Where do I start with replacing the whole MS AD stack:

                                          @Dashrender said in Where do I start with replacing the whole MS AD stack:

                                          @Donahue said in Where do I start with replacing the whole MS AD stack:

                                          @JaredBusch said in Where do I start with replacing the whole MS AD stack:

                                          @Donahue said in Where do I start with replacing the whole MS AD stack:

                                          Ok, DHCP is switched over. It's currently just pointing the DNS to the existing DNS servers.

                                          Right. Now you can work on setting up your DHCP reservation, and migrating all the static IP junk to reservations.

                                          Once that is done, you can work towards changing DNS.

                                          yeah, that will take awhile.

                                          really? Your DHCP server doesn't have an option to just add an existing lease to the reservation table?

                                          It's easy to create reservations. It's another thing entirely to migrate over devices from static to DHCP, while also changing their ip.

                                          You could just create reservations in the new DHCP server and have the existing windows DHCP server not renew requests.

                                          He's changing static IP'ed devices to DHCP with reservations.

                                          Are you agreeing with me or stating something Donohue is doing?

                                          Here he says

                                          @Donahue said in Where do I start with replacing the whole MS AD stack:

                                          migrate over devices from static to DHCP, while also changing their ip.

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

                                            @Dashrender said in Where do I start with replacing the whole MS AD stack:

                                            @DustinB3403 said in Where do I start with replacing the whole MS AD stack:

                                            @Dashrender said in Where do I start with replacing the whole MS AD stack:

                                            @DustinB3403 said in Where do I start with replacing the whole MS AD stack:

                                            @Donahue said in Where do I start with replacing the whole MS AD stack:

                                            @Dashrender said in Where do I start with replacing the whole MS AD stack:

                                            @Donahue said in Where do I start with replacing the whole MS AD stack:

                                            @JaredBusch said in Where do I start with replacing the whole MS AD stack:

                                            @Donahue said in Where do I start with replacing the whole MS AD stack:

                                            Ok, DHCP is switched over. It's currently just pointing the DNS to the existing DNS servers.

                                            Right. Now you can work on setting up your DHCP reservation, and migrating all the static IP junk to reservations.

                                            Once that is done, you can work towards changing DNS.

                                            yeah, that will take awhile.

                                            really? Your DHCP server doesn't have an option to just add an existing lease to the reservation table?

                                            It's easy to create reservations. It's another thing entirely to migrate over devices from static to DHCP, while also changing their ip.

                                            You could just create reservations in the new DHCP server and have the existing windows DHCP server not renew requests.

                                            He's changing static IP'ed devices to DHCP with reservations.

                                            Are you agreeing with me or stating something Donohue is doing?

                                            Here he says

                                            @Donahue said in Where do I start with replacing the whole MS AD stack:

                                            migrate over devices from static to DHCP, while also changing their ip.

                                            Again, that has nothing to do with the creation of Reservations on a new DHCP server. (presumably with a different scope).

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