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

    AD, Group Policies and Moving Users to a new OU

    IT Discussion
    5
    7
    440
    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.
    • JoelJ
      Joel
      last edited by

      We have all of our Active Directory users under the default 'Users' OU - all in one container.
      I'd like to split this up into different branches, ie. Back Office, Marketing, Managers etc etc

      However if I create new OU's and move users, will that break our group policies if applied to the original OU's?
      Is there a way I can export all Group Policies so I can view what policies are in place (assuming i'll need to re-create them)?

      Thanks
      Jason

      travisdh1T ObsolesceO 2 Replies Last reply Reply Quote 0
      • coliverC
        coliver
        last edited by

        Are the users moving to a new forest? If they are just moving to a new OU you could either make them sub OUs of the Users OU. Or you could link the existing policies to the new OUs that you create.

        No need to export or recreate OUs.

        momurdaM 1 Reply Last reply Reply Quote 0
        • travisdh1T
          travisdh1 @Joel
          last edited by

          @joel Are users not already in their respective group? Even the test users in my home lab LDAP exist in a default users OU, and are then members of different group OUs for their specific purposes.

          1 Reply Last reply Reply Quote 0
          • momurdaM
            momurda @coliver
            last edited by momurda

            @coliver said in AD, Group Policies and Moving Users to a new OU:

            Are the users moving to a new forest? If they are just moving to a new OU you could either make them sub OUs of the Users OU. Or you could link the existing policies to the new OUs that you create.

            No need to export or recreate OUs.

            You actually cant make sub OU in Users or Computers because the default Users container isnt an OU. Same with Computers default container. If you right click on these>New> you will see OU isnt available.
            0_1532618706641_0fc18aa9-e9f3-4ad4-b599-8dadd21c50e1-image.png
            I always thought this was something to be fixed but it is apparently by design.

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

              @joel said in AD, Group Policies and Moving Users to a new OU:

              However if I create new OU's and move users, will that break our group policies if applied to the original OU's?

              It depends on where your Group Policies are linked. If all your group policies are linked at the domain, and you create your OUs under that, there won't be any change.

              However, if your Group Policies are linked under the Users and Computers OU, and you create your new OUs outside of that, then you will need to move your Group Policy links so they are above and trickle down to your new OUs.

              1 Reply Last reply Reply Quote 1
              • coliverC
                coliver @momurda
                last edited by

                @momurda said in AD, Group Policies and Moving Users to a new OU:

                @coliver said in AD, Group Policies and Moving Users to a new OU:

                Are the users moving to a new forest? If they are just moving to a new OU you could either make them sub OUs of the Users OU. Or you could link the existing policies to the new OUs that you create.

                No need to export or recreate OUs.

                You actually cant make sub OU in Users or Computers because the default Users container isnt an OU. Same with Computers default container. If you right click on these>New> you will see OU isnt available.
                0_1532618706641_0fc18aa9-e9f3-4ad4-b599-8dadd21c50e1-image.png
                I always thought this was something to be fixed but it is apparently by design.

                That's true thanks for correcting me.

                1 Reply Last reply Reply Quote 0
                • JoelJ
                  Joel
                  last edited by

                  Post can be closed. I found our GPO's are not tied to the OU's so was fine to simply re-create new OUs. Cheers.

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