More Windows Networking Answers
Question Library
Ask a question about Windows Networking
Volunteer
Experts of the Month
Expert Login
Awards
About Us
Tell friends
Link to Us
Disclaimer
|
| |
|
|
| |
| | | |
About Tim Fenner
Expertise
Currently, my focus has been on the management of a Microsoft Windows, Exchange and Office deployment (with the majority of all servers running within an ESX Infrastructure 3 virtual environment). Along with supporting the previously listed solutions/products, I also have administration experience with an array of other technologies, such as backup solutions, SANs, anti-virus products, wired and wireless networking, mobile devices, VPNs, IPS, printing and much, much more...
Experience
I have over 9 years of technology related experience.
Publications
TechTarget.com
Education/Credentials
ITIL: Foundations; Microsoft: MCSE (2000 & 2003), MCSA (2000 & 2003), MCTS (Vista), MCP: Messaging (Exchange 2003); Cisco: CCNA, CompTIA: Security+, Network+, A+
| | |
| |
You are here: Experts > Computing/Technology > Focus on Windows 2000/NT > Windows Networking > Deployment of Windows 2003 servers
Windows Networking - Deployment of Windows 2003 servers
Expert: Tim Fenner - 8/10/2008
Question
I hope you will be doing well. I am planning to install windows 2003 server in my head office and 4 sub-office.
My first quiestion is When we need multiple forests and when we need multiple trees? can we deploy multiple forests and multiple trees in one organization? and what is best schema for one organization spanned on multiple gegraphical locations?
My second questioin is specific to my organization. I have deployed on windows 2003 domain controller in my head office and i have 4 sub-offices on different gegrapical location and i want to deploy DCs on each sub-office. What schema should i follow?
Regards
Saif
Answer
Hello Saif,
I highly doubt you need multiple forests. In fact, I highly doubt you need multiple trees. It sounds like you have a small environment (5 sites) and that they are all going to be managed the same (probably by you). If so, do not OVER COMPLICATE your Active Directory design, or you will pay for it later.
Personally, you can attack this setup in the following manner:
1. Setup an "empty root" domain to act as the top-level admin point for the rest of the domains that could be setup for each office.
2. Setup a single domain, with domain controllers located at each site, then setup AD synchronization to only occur during non-peak hours. You can also setup your Organizational Unit structure to mimic the layout of your geographical dispersement.
See here for more:
http://searchwinit.techtarget.com/news/article/0,289142,sid1_gci947393,00.html
http://www.tech-faq.com/active-directory-tree-forest.shtml
http://technet.microsoft.com/en-us/library/cc268205.aspx
If you need more help, please let me know.
Add to this Answer
Ask a Question
|
|
