Reference no: EM132162990

Use Visio or an alternative to draw domains and sites; justify your design

How would you create your sites and domains based upon the following specifications for the company citibase?

You will need to consider the amount of replication traffic within domains versus the amount between domains.

You will need to design the sites to control replication traffic and speed up logon times.

The network administrators in each country want to maintain administrative control over their own domains.

Also, each division for a particular domain wants to maintain some administrative control over their users.

You should have two domain controllers at a minimum for each domain.

Assignment:

You will need two separate diagrams in this design. One for the sites and one for the domain(s).

a. Sketch out the physical site structure. Use the above graphic as a guide.

i. Indicate the sites.

ii. Indicate the site links.

iii. Indicate where the domain controllers should be located. Indicate the number of domain controllers per site.

iv. Indicate where global catalog servers should be placed.

v. Define any site link bridges and tell why necessary or not necessary.

vi. Indicate the possible bridgehead servers.

vii. Specify any site link bridges that may be necessary.

vii. Justify the sites you have specified.

b. Sketch out the logical domain structure. Use triangles for domains and circles within triangles to represent OUs.

i. Provide the namespace for the domains.

ii. Provide any additional containers within domains that you would recommend.

iii. Justify why you chose this design.

Things to consider when designing your sites and domains:

Sites: If you have less than 5Mbps of dedicated available bandwidth between two locations, these locations should be in separate sites. Assume that speeds over 5Mbps are fast enough to handle the replication overhead in addition to the normal network traffic.

Single Domains

Single domain controller at each site; two for redundancy

Reduced dependency on global catalog servers for authentication

Multiple Domains

Disagreement on Account Policies such as Password, Account Policies, and Kerberos Policy between domains and do not want to implement fine granularity password policies

Replication issues over slow WAN links (Remember replication between domains is limited to global catalogs, schema, and site information)

International considerations - many countries require management within the country

Enterprise administrator accounts can be created by Domain administrators in the root domain (can be a security issue)

Multiple Forests

Need to specify trusts

Don't want users browsing other domains

Want unique schemas

No replication of global catalog

Prevent accounts from one domain being visible in another domain

Short term ventures