Best Practices for Simplifying AD after SBS2003 to 2012R2 Migration

Successfully migrated SBS2003 to Windows Standard 2012 R2.  Simple network setup - single domain, subnet, location, 35x Win7 Pro x64 PC’s and 5x Win7 Pro x64 Laptops.  The migrated AD includes the "MyBusiness" OU with "Computers", "Users" OU's below and "SBSComputers" & "SBSUsers" under those.  All users and computers reside in those folders.  All (5?) SBS-related GPO's were removed as part of the migration process and I am a complete GP Novice and so have never created anything custom or unique.  
The 2012R2 Standard Server has "Users" and "Computers" as part of the base AD structure and I'm wondering if I should move all the computers and users into those respective containers?  Or should I create OU's somewhere under those?

So my question is:  What are the best-practices for simplifying this AD structure before I start creating GPO's and performing other administrative tasks?
Gandalf GreyAsked:
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.

Cliff GaliherCommented:
If you are happy with it, don't mess with it.  What isn't broken and all that.

It is worth noting that the users and computers items you mentioned were in SBS as well. They are default containers (they are NOT OUs) and most businesses want more organization than those containers.  You can't link group policies to them for example.  So yes, SBS sets up a basic OU structure in addition to those default containers and the SBS wizards knew to create new users and joined computers in those OUs.  But they weren't particularly SBS magic and can continue to serve that function in a standard domain.

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
Gandalf GreyAuthor Commented:
Ok thanks Cliff - I appreciate your insight.  Needless to say I am looking to simplify things in AD before rolling-out GPO solutions in my other Question.  

I meant to mention I understand the Containers vs OU's and wondered if folks usually just create OU's below those default Users/Computers containers or what?  I'd prefer not to have quite the "deep" structure of those SBS-related entries if they are no longer being utilized as designed.  I do understand "if it ain't broke" but my OCD kicks in sometimes too and likes to keep things simple (lol).  I do note that I would have to use the utilities to point new computers and users to their respective new homes.  Even if I could get rid of the "SBSComputers" & "SBSUsers" OU's - again - just to simplify things and remove all remaining references to SBS.
Cliff GaliherCommented:
You cannot create OUs nested under containers.  You can remove a layer or two of those OUs if you really feel it necessary. But I'd at least keep some sort of separation of OUs.
Gandalf GreyAuthor Commented:
Thank you for the help - I removed the one layer of OU's and maintained the MyBusiness OU structure for now.
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
Windows OS

From novice to tech pro — start learning today.