- Active Directory Disaster Recovery
- Florian Rommel
- 513字
- 2021-07-02 11:37:14
Domain Design: Single Forest, Single Domain, and Star Shaped
Note
A domain is not a security boundary within a forest. By default, all domains have transitive trust relationships within a forest and are therefore visible to each other. On top of that, all Global Catalogs contain the Security database and a rogue administrator can potentially gain access to different domains or even the entire forest. Please see http://www.microsoft.com/technet/security/bulletin/MS02-001.mspx for more details on such vulnerability. Even though this particular vulnerability no longer exists within Windows 2003, something causing similar effects can be a possibility.
This is the most common design version for small-and medium-size businesses, that have offices within one country or that are geographically close. It involves a single hub site and several small sites. A hub site is defined as a big data center where the majority of your infrastructure is housed. So if you have the headquarters and development for nailcorp.com taking place in Los Angeles where 40 servers are housed in a datacenter and 900 people work, then that would be a hub site. In short, a hub site is a location where a large part of your crucial infrastructure operates.
From the hub site, all changes are replicated out to smaller sites, which can be small branch offices, small development locations, or pretty much any office that warrants its own domain controller. This puts control firmly into the one major hub site and all the branch sites just replicate with that. The advantage of this set-up is that you can push out a forced replication to all branch sites at once (provided your bandwidth supports this) and do not have to wait for any delayed replication schedules due to time zones and so on. The drawback is that if you do have a problem, due to human error, for example, and this gets replicated, everyone gets it at once. If, for example, an administrator at NailCorp deletes or renames by accident a service account that is used by a certain service throughout the organization, and he does not notice it, then after the next replication the service stops working. If the replication was star shaped and went to everywhere at the same time, the service stops everywhere at the same time. If the service is something that does not get recognized immediately, such as an antivirus policy update or some automatic update service from a third-party application, this failure will not get noticed immediately and the service will stop and won't restart because it will be a logon failure. In this scenario, NailCorp could go on for days without anyone noticing.
As you can see in the following figure, in this design NailCorp would have a single hub site and three branch sites. Each site would have its own IP address range and would have, within Active Directory, its own site with DCs located inside it.
In this case, we only have a single forest and a single domain with different sites, but even in these sites all objects belong to the same forest and hence the same domain.

- 做好PPT就靠這幾招:圖解力+吸引力+說服力
- 擁抱開源(第2版)
- SPSS進階分析與實務(wù)
- 像攝影師一樣調(diào)色
- Liferay User Interface Development
- 跟儲君老師學(xué)Excel極簡思維
- 中文版Photoshop CS6全能一本通·全彩版
- IT Inventory and Resource Management with OCS Inventory NG 1.02
- Apache Solr 3.1 Cookbook
- 中文版Photoshop CS5平面設(shè)計實用教程(第2版)
- Photoshop CC入門與提高
- Photoshop人像精修秘笈
- Photoshop+CorelDRAW平面設(shè)計實例教程(第3版)
- Creo 4.0中文版基礎(chǔ)教程
- Adobe Illustrator CC 2019經(jīng)典教程(彩色版)