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

    Group Policy points to wrong DC

    IT Discussion
    6
    35
    1.3k
    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 @G I Jones
      last edited by

      @G-I-Jones said in Group Policy points to wrong DC:

      @Dashrender said in Group Policy points to wrong DC:

      @G-I-Jones said in Group Policy points to wrong DC:

      e secondary to another site, then it would default to the one I wanted it to, but I got two things wrong: first and most i

      As I recall - it's either which ever DC is provided by DNS when a query for a DC is given, OR in the case of broadcast - whomever answers first.

      Yea I think it might be the latter, as the DNS for my machine's NIC is pointing to the primary DC, but set replies with the secondary.

      It's random to load balance.

      DashrenderD 1 Reply Last reply Reply Quote 0
      • DashrenderD
        Dashrender @G I Jones
        last edited by

        @G-I-Jones said in Group Policy points to wrong DC:

        @Dashrender said in Group Policy points to wrong DC:

        @G-I-Jones said in Group Policy points to wrong DC:

        e secondary to another site, then it would default to the one I wanted it to, but I got two things wrong: first and most i

        As I recall - it's either which ever DC is provided by DNS when a query for a DC is given, OR in the case of broadcast - whomever answers first.

        Yea I think it might be the latter, as the DNS for my machine's NIC is pointing to the primary DC, but set replies with the secondary.

        you're misunderstanding DNS. The query the client machine is making is - give me the IP of a DC - ANY DC, and DNS is likely following a round robin affect and just handing out the IP of the next one that hasn't been handed out.
        Let's assume there are 2 DCs.
        ClientA queries for any DC - answer - DC1
        ClientB queries for any DC - answer - DC2
        ClientC queries for any DC - answer - DC1
        etc

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

          @scottalanmiller said in Group Policy points to wrong DC:

          @G-I-Jones said in Group Policy points to wrong DC:

          @Dashrender said in Group Policy points to wrong DC:

          @G-I-Jones said in Group Policy points to wrong DC:

          e secondary to another site, then it would default to the one I wanted it to, but I got two things wrong: first and most i

          As I recall - it's either which ever DC is provided by DNS when a query for a DC is given, OR in the case of broadcast - whomever answers first.

          Yea I think it might be the latter, as the DNS for my machine's NIC is pointing to the primary DC, but set replies with the secondary.

          It's random to load balance.

          Is it truly random? not just round-robin?

          scottalanmillerS ObsolesceO 2 Replies Last reply Reply Quote 0
          • scottalanmillerS
            scottalanmiller @Dashrender
            last edited by

            @Dashrender said in Group Policy points to wrong DC:

            @scottalanmiller said in Group Policy points to wrong DC:

            @G-I-Jones said in Group Policy points to wrong DC:

            @Dashrender said in Group Policy points to wrong DC:

            @G-I-Jones said in Group Policy points to wrong DC:

            e secondary to another site, then it would default to the one I wanted it to, but I got two things wrong: first and most i

            As I recall - it's either which ever DC is provided by DNS when a query for a DC is given, OR in the case of broadcast - whomever answers first.

            Yea I think it might be the latter, as the DNS for my machine's NIC is pointing to the primary DC, but set replies with the secondary.

            It's random to load balance.

            Is it truly random? not just round-robin?

            Well, it's round robin, but you can't know, as a client, how many queries are going on. So to you, it is random as there is a randomizer in the background.

            Nothing is truly random in the universe. But to the client it is as random as anything else.

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

              @scottalanmiller said in Group Policy points to wrong DC:

              Nothing is truly random in the universe.

              Stars being born and dying isn't random?

              1 Reply Last reply Reply Quote 0
              • G I JonesG
                G I Jones @Dashrender
                last edited by

                @Dashrender said in Group Policy points to wrong DC:

                @G-I-Jones said in Group Policy points to wrong DC:

                @Dashrender said in Group Policy points to wrong DC:

                @G-I-Jones said in Group Policy points to wrong DC:

                e secondary to another site, then it would default to the one I wanted it to, but I got two things wrong: first and most i

                As I recall - it's either which ever DC is provided by DNS when a query for a DC is given, OR in the case of broadcast - whomever answers first.

                Yea I think it might be the latter, as the DNS for my machine's NIC is pointing to the primary DC, but set replies with the secondary.

                you're misunderstanding DNS. The query the client machine is making is - give me the IP of a DC - ANY DC, and DNS is likely following a round robin affect and just handing out the IP of the next one that hasn't been handed out.
                Let's assume there are 2 DCs.
                ClientA queries for any DC - answer - DC1
                ClientB queries for any DC - answer - DC2
                ClientC queries for any DC - answer - DC1
                etc

                Ah, I see what you are saying here. Goes in with the idea that these are a pool. Appreciate that point of view, I hadn't thought of that just yet.

                DashrenderD 1 Reply Last reply Reply Quote 0
                • DashrenderD
                  Dashrender @G I Jones
                  last edited by Dashrender

                  @G-I-Jones said in Group Policy points to wrong DC:

                  @Dashrender said in Group Policy points to wrong DC:

                  @G-I-Jones said in Group Policy points to wrong DC:

                  @Dashrender said in Group Policy points to wrong DC:

                  @G-I-Jones said in Group Policy points to wrong DC:

                  e secondary to another site, then it would default to the one I wanted it to, but I got two things wrong: first and most i

                  As I recall - it's either which ever DC is provided by DNS when a query for a DC is given, OR in the case of broadcast - whomever answers first.

                  Yea I think it might be the latter, as the DNS for my machine's NIC is pointing to the primary DC, but set replies with the secondary.

                  you're misunderstanding DNS. The query the client machine is making is - give me the IP of a DC - ANY DC, and DNS is likely following a round robin affect and just handing out the IP of the next one that hasn't been handed out.
                  Let's assume there are 2 DCs.
                  ClientA queries for any DC - answer - DC1
                  ClientB queries for any DC - answer - DC2
                  ClientC queries for any DC - answer - DC1
                  etc

                  Ah, I see what you are saying here. Goes in with the idea that these are a pool. Appreciate that point of view, I hadn't thought of that just yet.

                  This is one of the many things you learn reading a Windows Server/Active Directory book. Though everyone here will tell you that's a waste of time.

                  1 Reply Last reply Reply Quote 0
                  • G I JonesG
                    G I Jones @scottalanmiller
                    last edited by G I Jones

                    @scottalanmiller said in Group Policy points to wrong DC:

                    It really only boiled down to I don't want to wait 15 minutes (the minimum replication between DC's) for a GPO to apply.

                    Then time to go to a single DC 🙂

                    But GPOs aren't meant to work this way, really. If you want faster results, GPO is the wrong tool.

                    What alternative to Group Policy do you recommend?

                    DustinB3403D DashrenderD scottalanmillerS 3 Replies Last reply Reply Quote 0
                    • DustinB3403D
                      DustinB3403 @G I Jones
                      last edited by

                      @G-I-Jones said in Group Policy points to wrong DC:

                      @scottalanmiller said in Group Policy points to wrong DC:

                      It really only boiled down to I don't want to wait 15 minutes (the minimum replication between DC's) for a GPO to apply.

                      Then time to go to a single DC 🙂

                      But GPOs aren't meant to work this way, really. If you want faster results, GPO is the wrong tool.

                      What alternative to Group Policy do you recommend?

                      Using a tool like PDQ Deploy is pretty smooth, but it's a substantial annual cost.

                      1 Reply Last reply Reply Quote 0
                      • DashrenderD
                        Dashrender @G I Jones
                        last edited by

                        @G-I-Jones said in Group Policy points to wrong DC:

                        @scottalanmiller said in Group Policy points to wrong DC:

                        It really only boiled down to I don't want to wait 15 minutes (the minimum replication between DC's) for a GPO to apply.

                        Then time to go to a single DC 🙂

                        But GPOs aren't meant to work this way, really. If you want faster results, GPO is the wrong tool.

                        What alternative to Group Policy do you recommend?

                        Salt would likely be his first suggestion.

                        ObsolesceO 1 Reply Last reply Reply Quote 1
                        • ObsolesceO
                          Obsolesce @Dashrender
                          last edited by

                          @Dashrender said in Group Policy points to wrong DC:

                          @scottalanmiller said in Group Policy points to wrong DC:

                          @G-I-Jones said in Group Policy points to wrong DC:

                          @Dashrender said in Group Policy points to wrong DC:

                          @G-I-Jones said in Group Policy points to wrong DC:

                          e secondary to another site, then it would default to the one I wanted it to, but I got two things wrong: first and most i

                          As I recall - it's either which ever DC is provided by DNS when a query for a DC is given, OR in the case of broadcast - whomever answers first.

                          Yea I think it might be the latter, as the DNS for my machine's NIC is pointing to the primary DC, but set replies with the secondary.

                          It's random to load balance.

                          Is it truly random? not just round-robin?

                          AD is a multi-master system. The best DC for the client in the site will reply.

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

                            @Dashrender said in Group Policy points to wrong DC:

                            @G-I-Jones said in Group Policy points to wrong DC:

                            @scottalanmiller said in Group Policy points to wrong DC:

                            It really only boiled down to I don't want to wait 15 minutes (the minimum replication between DC's) for a GPO to apply.

                            Then time to go to a single DC 🙂

                            But GPOs aren't meant to work this way, really. If you want faster results, GPO is the wrong tool.

                            What alternative to Group Policy do you recommend?

                            Salt would likely be his first suggestion.

                            I didn't catch what his use case here was for not wanting to wait 15 minutes. Policy is something you set, and doesn't need to be instant.

                            Config management like you said, will work for that. I used Salt heavily in a Windows environment where Group Policy was really lacking. It was a great success.

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

                              @Obsolesce said in Group Policy points to wrong DC:

                              @Dashrender said in Group Policy points to wrong DC:

                              @G-I-Jones said in Group Policy points to wrong DC:

                              @scottalanmiller said in Group Policy points to wrong DC:

                              It really only boiled down to I don't want to wait 15 minutes (the minimum replication between DC's) for a GPO to apply.

                              Then time to go to a single DC 🙂

                              But GPOs aren't meant to work this way, really. If you want faster results, GPO is the wrong tool.

                              What alternative to Group Policy do you recommend?

                              Salt would likely be his first suggestion.

                              I didn't catch what his use case here was for not wanting to wait 15 minutes. Policy is something you set, and doesn't need to be instant.

                              Config management like you said, will work for that. I used Salt heavily in a Windows environment where Group Policy was really lacking. It was a great success.

                              Likely his reasoning is testing - he makes a change and doesn't want to wait to test that change. I already provided a solution to the waiting above.

                              find the server the client is polling,
                              update GPO on that server
                              tell client to gpupdate /force
                              see results

                              But you (@Obsolesce) quoted my Salt reply which was a response to what other tools to use besides GPO.

                              Salt could be a good GP replacement in a LANLess setup, for example.

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

                                @Dashrender said in Group Policy points to wrong DC:

                                Salt could be a good GP replacement in a LANLess setup, for example.

                                Works fine LAN-based, too.

                                1 Reply Last reply Reply Quote 0
                                • scottalanmillerS
                                  scottalanmiller @G I Jones
                                  last edited by

                                  @G-I-Jones said in Group Policy points to wrong DC:

                                  @scottalanmiller said in Group Policy points to wrong DC:

                                  It really only boiled down to I don't want to wait 15 minutes (the minimum replication between DC's) for a GPO to apply.

                                  Then time to go to a single DC 🙂

                                  But GPOs aren't meant to work this way, really. If you want faster results, GPO is the wrong tool.

                                  What alternative to Group Policy do you recommend?

                                  Salt, Ansible, Chef, Puppet, etc.

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