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

    Solved GPO applying when it shouldn't

    IT Discussion
    3
    8
    1.5k
    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.
    • Mike DavisM
      Mike Davis
      last edited by

      I've got a printer deployment GPO that is applying to objects in an OU with blocked inheritance. I have a printers deployment GP that is linked to a physical computer OU. Then I have a RDS Server OU. In addition I have the RDS Server OU set to block inheritance just in case. The server is taking a long time to log in to and sits at "Applying Group Policy Printers policy." I did a GP result and can see it processing all the printers even through that GP isn't applied.

      When I google the issue it seems that everyone else has an issue applying GPs and not the other way around. Any ideas?

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

        I'm not sure what the problem was, but what I ended up doing was backing up the GPO, deleting the GPO, restoring the GPO, and then linking it back where it should have been linked. I'm not sure why, but that fixed the problem.

        1 Reply Last reply Reply Quote 6
        • jyatesJ
          jyates @Mike Davis
          last edited by

          If the printer policy is enforced, it will override the blocked inheritance.

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

            It's not enforced.

            1 Reply Last reply Reply Quote 0
            • jyatesJ
              jyates
              last edited by

              If you have another GPO that is enforced, just try moving the printer GPO so it's applied after that one, or before if it is already after it.

              Doesn't sound like it should be applying, but you can add a wmi filter to your printer policy, and have it exclude RDS servers. That's a bandaid solution though. If you come across a real solution, please update. I am very curious.

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

                I'm not sure what the problem was, but what I ended up doing was backing up the GPO, deleting the GPO, restoring the GPO, and then linking it back where it should have been linked. I'm not sure why, but that fixed the problem.

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

                  As soon as I deleted the GPO my login time went from 5 minutes to a few seconds, so I knew that was the issue.

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

                    @Mike-Davis said in GPO applying when it shouldn't:

                    As soon as I deleted the GPO my login time went from 5 minutes to a few seconds, so I knew that was the issue.

                    Hmmm... I might do this myself. I have always wondered why my boot times were so bad.. it's probably this.

                    Not 5 min bad.. but not anywhere near as fast as non domain joined fast.

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

                      @Dashrender None of the other machines on the domain take that long to log in. If they did, there are tricks you can use to speed up your printer deployment.

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