Renaming OUs and consequences

Environment is Windows 2012 R2 servers in a Windows 2008 domain functional level.  Workstations are all Win7.

I want to rename some OUs.  The ones I want to rename contain the BULK of all of my physical workstations and VMs.

From what I have read, and from what I have done in previous domains, renaming shouldn't be a problem, but I wanted to ask before I did it all willy nilly.

What are your thoughts on the consequences\pitfalls of renaming OUs in AD?


Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Chris KonickiSecurity EngineerCommented:
As you know I'm sure, this is dependent on the size and purpose of the Domain. While many of your client machines and users may not see or experience any changes in regards to you renaming an OU, the main thing to monitor would be user membership (if applicable) to that OU, as well as object membership. While the records should propagate throughout your forest(s), that would be one of the things I would look at once you've made the changes. Some user accounts may not refresh their memberhsip on the server-side, but a simple gpupdate command should save you.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
The OU name is merely a descriptor of a record the {ou object ID will remain what it is}  If replication issue exist, the OU name change will not be reflected,m and likely any GPO/...

If you have scripts/vb/powershell wmi that use name lookups using the old OU name will no longer work

will now be

these will not auto transition.

wmi filters on GPOs if any using OU restrictions would need to be updated
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.