Creating a Domain Model

Creating a Domain Model
Student
POS/421
Today’s Date
Instructor

Subdomain stratford.usa.companybeta.com Subnet1
Subnet2
Subnet3

Subdomain concord.usa.companybeta.com Subnet1
Subnet2
Subnet3

Subdomain philadelphia.usa.companybeta.com Subnet1
Subnet2
Subnet3

Subdomain vancouver.canada.companybeta.com Subnet1
Subnet2

Subdomain montreal.canada.companybeta.com Subnet1
Subnet2
Forrest Root companybeta.com Location: Boston, Ma.
Tree 1 Root Domain usa.companybeta.com Location Boston, Ma.

Tree 2 Root Domain canada.companybeta.com Location: Toronto, Canada

The Domain Model
A Windows domain model is an organized collaboration of Windows servers whose database contain user information, organizational, functional, and security policies amongst other things. By the nature of the class, the use of Windows Server 2008 R2 is established. Depending on the business and hierarchical topology of the organization that is served by the model, it can be a single domain or made up of multiple domains. If there are multiple domains, they could be organized into a tree or trees that make up a forest or forests.
In the case of Company Beta, all city locations represent enough users and resources to be represented by domains. Although the exact numbers are not presented, the fact that all the subdomains use subnets attest to this fact and necessity.
Company Beta is represented by a Domain Forest model with the forest root seated in the main location in Boston. This serves a parent to child relationship with the two trees: Company Beta, U.S.A (usa.companybeta.com in Boston) and Company Beta, Canada (canada.companybeta.com, in Toronto). These two tree roots in turn serve parent to child relations with their respective subdomains residing in the separate cities.
Since subnets are basically allotments of IP addresses used as tools to separate virtual LANs within the domain, they are represented and named as Subnet1, Subnet2, and