General discussion


OU Design Help

By bfeltus ·
Need help on OU design. We are a financial institution. We have about aprox 300 employees and about 300 workstations. Have about 30 windows 2000 and 2003 servers (terminal server, dhcp, sql, web, dns,). We have about 20 branches in state, but different cities. We have 5 branches in another state. All our servers are at the main office. Branches connect through T1. Some of the major departments are Marketing, Mortgage, Consumer Lending, Tellers, Customer Service. 2 applications are accessed through terminal services. All the departments except marketing can be found in branch office although they are not autonomous. Based on the information I have given, please give EXAMPLES of how you would design the ou structure and why. How would you handle the terminal server users. How would we handle users for example that do some work in more than one department for example, mortgage and consumer lending. I was thinking about doing a function-base design. Some functions would include underwriting, lending, originating for the mortgage and consumer lending.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

by Greybeard770 In reply to OU Design Help

The first thing is to forget about departmental structure. You design your OUs according to what group policies you want applied how, and by which OUs you want to delegate control. You will have fewer OUs that way which makes for easier manageability. My guess is that all the OUs will be centrally managed - so much for the delegation excuse to create an OU. If your Tellers, underwriters, and terminal server users will have the same group policies and you don't intend to delegate control then they should all be in the same OU.
Departments will change in your organization but that doesn't mean your AD needs to. Simple is better.

Related Discussions

Related Forums