Server 2003 - OU/GPO best practices, fairly confused.


hi guys,

i trying restructure companies active directory , don't know best way there many conflicting articles. maybe can critique findings far.

basically have 3 companies have employees in 3 locations (random names):

locations - richmond, surrey, maple ridge

companies - abc, 123, acme

each location has employees each company, how structure:

http://www.windowsnetworking.com/articles_tutorials/best-practices-designing-group-policy.html

 

i guess main difference there 3 different companies, best idea (as examples)

richmond->acme->sales->users

surrey->acme->sales->users

surrey->abc->marketing->computers

 

still simple right?

just curious on thoughts, thanks

 

 

hello again,

if want proceed mentioned using sites then:

create ous based on:

company > job surrey > it

there no need create ou users , computers.

let's suppose have users , computers in surrey add user/computer accounts in surrey > it. all!

keep model easiest 1 can do. advice you.


posting provided "as is" no warranties or guarantees , , confers no rights.

microsoft student partner
microsoft certified professional
microsoft certified systems administrator: security
microsoft certified systems engineer: security
microsoft certified technology specialist: windows server 2008 active directory, configuration
microsoft certified technology specialist: windows server 2008 network infrastructure, configuration

microsoft certified technology specialist: windows server 2008 applications infrastructure, configuration



Windows Server  >  Group Policy



Comments

Popular posts from this blog

Error: 0x80073701 when trying to add Print Services Role in Windows 2012 Standard

Disconnecting from a Windows Server 2012 R2 file sharing session on a Windows 7,8,10 machine

Event ID 64,77,1008 Certificates Events Windows Server 2008, 2008R2