Organizational Units?

[Maximus2000]

Ok,

I just migrated my old Nt Domain into a Windows Server 2003 Active Directory. My question is this.... since my compny is fairly small on ly 120 users and 115 computers, I was going to create OU's more for structure purpose than Admin purpose. I was going to create a Finance, Quality, R&D OU's just so I know what user belongs where and what system is where. Yeah, down the road I may find it handy to have these OU's for Admin reasons. However, now it would be just for organizing. Is there any reason not to create OU's. Should I just leave them in the default binis Users along with the Computers too? Thanks for any help.

 

[schtek]

I was going to create a Finance, Quality, R&D OU's just so I know what user belongs where and what system is where..

you have really answered your question in this statement that u said. it will be easy to solve and problems and look after your network if you use ou's

"Ask not what your computer network can do for you - ask what you can do to the computer network to give you a quiet moment ."

 

[mrdenny]

OUs are there to be used to make your life easier. If you use them to deploy GPOs against or not is for you to decide. If you just want to use it to make it easier to find people there is nothing wrong with that at all. If it makes your life easier, then it is the correct use of the GPOs.

Denny
MCSA (2003) / MCDBA (SQL 2000)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

(Not quite so old any more.)

 

[Tightpants]

If you are not sure at the moment you could just leave everything as the default setup. You may even find that if you create OUs which seem logical now, they may not achieve what you need in the future.

If you are using GPOs then set up your OUs now.

 

[Maximus2000]

Thanks for all your help I have set up my OU's and will soon start looking at linking GPO's to them.