Re: OU Design Best Practices

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Simple is always best.
The simpler you can make it, the happier you'll be over the long term. On
the bright side, you *could* always restructure as needed as well.

My advice is to define your administrative delegation model (are you going
to do everything always, or will there be separation of duties etc?) and
also design your GPO plans. In your case, since you are less likely to know
your gpo plans, you should favor your administrative model and balance that
with future administration of gpo's i.e. will you separate the gpo's by
business unit? Or will you keep them minimally different and apply to all
of them (mostly)?

Answering those types of questions should help to guide the design.

Why is it you have a separate HR in NJ? Or is that a global HR that happens
to be in NJ?


"Chris Lukowski" <ChrisLukowski@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:841DF827-8240-445E-8BFF-89DAB9885AF8@xxxxxxxxxxxxxxxx
We currently do not have any GPOs in place and want to design a sound OU
structure first. Currently our user base only consists of our office
building
and remote managers with laptops across the country. We currently have no
plans for remote offices with the ability to access our files and if we
did
they'd likely be on a child domain if it comes to that. That said, should
we
still build our OU structure with a very high top level such as :

-Company
-USA
-Remote Users
-NJ
-HR
-Accounts Payable
-ETC

Is that the best practice or should I shave off a few levels and just get
to
the point? Our administration is very centralized if it makes any
difference.
Thanks!


.

Relevant Pages