Professional Documents
Culture Documents
Microsoft Corporation
Published: March, 2012
Authors: James McIllece and Brit Weston
Technical Contributors: Shyam Seshadri, Justin Hall, and Greg Lindsay
The Windows Server 2012 Core Network Guide provides instructions for planning and deploying
the core components required for a fully functioning network and a new Active Directory domain
in a new forest. Using this guide, you can deploy computers configured with the following server
roles and technologies:
The Network Policy Server (NPS) role service of the Network Policy and Access Services
server role
This guide also serves as a foundation for companion guides that show you how to deploy
additional technologies in Windows Server 2012.
Contents
Core Network Guide....................................................................................................................... 6
About this guide........................................................................................................................... 6
Network hardware requirements.............................................................................................. 7
What this guide does not provide................................................................................................ 7
Technology Overviews................................................................................................................. 8
Active Directory Domain Services............................................................................................ 8
DNS......................................................................................................................................... 8
DHCP....................................................................................................................................... 8
TCP/IP..................................................................................................................................... 8
Core Network Overview............................................................................................................... 9
Core Network Components.................................................................................................... 10
Router.............................................................................................................................. 10
Static TCP/IP configurations............................................................................................ 10
Active Directory Domain Services global catalog and DNS server DC1..........................11
DHCP server DHCP1...................................................................................................... 11
Client computers.............................................................................................................. 11
Core Network Planning.............................................................................................................. 11
Planning subnets.................................................................................................................... 11
Planning basic configuration of all servers.............................................................................12
Planning naming conventions for computers and devices..................................................12
Planning static IP addresses...............................................................................................13
Planning the deployment of DC1............................................................................................13
Planning the name of the forest root domain......................................................................13
Planning the forest functional level.....................................................................................14
Planning DNS zones........................................................................................................... 15
Planning domain access........................................................................................................ 16
Planning the deployment of DHCP1.......................................................................................16
Planning DHCP servers and DHCP forwarding..................................................................16
Planning IP address ranges................................................................................................17
Planning subnet masks....................................................................................................... 17
Planning exclusion ranges.................................................................................................. 18
Planning TCP/IP static configuration...................................................................................19
Core Network Deployment........................................................................................................ 20
Configuring All Servers........................................................................................................... 20
Rename the computer........................................................................................................ 20
Configure a static IP address..............................................................................................21
Deploying DC1.................................................................................................................... 22
Install AD DS and DNS for a New Forest........................................................................23
Create a User Account in Active Directory Users and Computers...................................25
Add a Group.................................................................................................................... 26
Assign Group Membership.............................................................................................. 26
Configure a DNS Reverse Lookup Zone.........................................................................27
Joining Server Computers to the Domain and Logging On.................................................28
Deploying DHCP1............................................................................................................... 29
Install Dynamic Host Configuration Protocol (DHCP)......................................................30
Create and Activate a New DHCP Scope........................................................................31
Joining Client Computers to the Domain and Logging On.....................................................32
Deploying optional features for network access authentication and Web services................33
Deploying NPS1................................................................................................................. 34
Planning the deployment of NPS1...................................................................................35
Install Network Policy Server (NPS)................................................................................35
Register the NPS Server in the Default Domain..............................................................36
Deploying WEB1................................................................................................................. 37
Install the Web Server (IIS) server role............................................................................37
Additional Technical Resources................................................................................................. 38
Appendices A through E............................................................................................................ 39
Appendix A - Renaming computers........................................................................................... 39
Windows Server 2008 R2 and Windows 7.............................................................................39
Windows Server 2008 and Windows Vista.............................................................................40
Windows Server 2003 and Windows XP................................................................................40
Appendix B - Configuring static IP addresses............................................................................40
Windows Server 2008 R2...................................................................................................... 41
Windows Server 2008............................................................................................................ 41
Windows Server 2003............................................................................................................ 42
Appendix C Joining computers to the domain........................................................................43
Windows Server 2008 R2 and Windows 7.............................................................................43
Windows Server 2008 and Windows Vista.............................................................................44
Windows Server 2003 and Windows XP................................................................................44
Appendix D Log on to the domain..........................................................................................45
Windows Server 2008 R2 and Windows 7.............................................................................45
Windows Server 2008 and Windows Vista.............................................................................45
Windows Server 2003 and Windows XP................................................................................46
Appendix E - Core Network Planning Preparation Sheet..........................................................46
Installing Active Directory Domain Services and DNS............................................................47
Pre-installation configuration items for AD DS and DNS.................................................47
AD DS and DNS installation configuration items.............................................................47
Configuring a DNS Reverse Lookup Zone..........................................................................48
Installing DHCP...................................................................................................................... 48
Pre-installation configuration items for DHCP.................................................................49
DHCP installation configuration items.............................................................................49
Creating an exclusion range in DHCP................................................................................50
Creating a new DHCP scope.............................................................................................. 50
Installing Network Policy Server (optional).............................................................................51
The Windows Server 2012 Core Network Guide in Word format in the Microsoft Download
Center at http://go.microsoft.com/fwlink/p/?LinkId=255199.
The Windows Server 2012 Core Network Guide in HTML format in the Windows Server 2012
Technical Library.
This guide is designed for network and system administrators who are installing a new network or
who want to create a domain-based network to replace a network that consists of workgroups.
The deployment scenario provided in this guide is particularly useful if you foresee the need to
add more services and features to your network in the future.
It is recommended that you review design and deployment guides for each of the technologies
used in this deployment scenario to assist you in determining whether this guide provides the
services and configuration that you need.
A core network is a collection of network hardware, devices, and software that provides the
fundamental services for your organization's information technology (IT) needs.
A Windows Server core network provides you with many benefits, including the following.
Core protocols for network connectivity between computers and other Transmission Control
Protocol/Internet Protocol (TCP/IP) compatible devices. TCP/IP is a suite of standard
protocols for connecting computers and building networks. TCP/IP is network protocol
software provided with Microsoft Windows operating systems that implements and
supports the TCP/IP protocol suite.
Domain Name System (DNS) name resolution service. DNS allows users, computers,
applications, and services to find the IP addresses of computers and devices on the network
by using the Fully Qualified Domain Name of the computer or device.
Note
A forest, which is one or more Active Directory domains that share the same class and
attribute definitions (schema), site and replication information (configuration), and forest-wide
search capabilities (global catalog).
A forest root domain, which is the first domain created in a new forest. The Enterprise Admins
and Schema Admins groups, which are forest-wide administrative groups, are located in the
forest root domain. In addition, a forest root domain, as with other domains, is a collection of
computer, user, and group objects that are defined by the administrator in Active Directory
Domain Services (AD DS). These objects share a common directory database and security
policies. They can also share security relationships with other domains if you add domains as
your organization grows. The directory service also stores directory data and allows
authorized computers, applications, and users to access the data.
A user and computer account database. The directory service provides a centralized user
accounts database that allows you to create user and computer accounts for people and
computers that are authorized to connect to your network and access network resources,
such as applications, databases, shared files and folders, and printers.
A core network also allows you to scale your network as your organization grows and IT
requirements change. For example, with a core network you can add domains, IP subnets,
remote access services, wireless services, and other features and server roles provided by
Windows Server 2012.
A hub, Layer 2 or 3 switch, router, or other device that performs the function of relaying
network traffic between computers and devices.
Computers that meet the minimum hardware requirements for their respective client and
server operating systems.
Internet connectivity
Remote access
Wireless access
Technology Overviews
The following sections provide brief overviews of the required technologies that are deployed to
create a core network.
DNS
DNS is a name resolution protocol for TCP/IP networks, such as the Internet or an organization
network. A DNS server hosts the information that enables client computers and services to
resolve easily recognized, alphanumeric DNS names to the IP addresses that computers use to
communicate with each other.
DHCP
DHCP is an IP standard for simplifying the management of host IP configuration. The DHCP
standard provides for the use of DHCP servers as a way to manage dynamic allocation of IP
addresses and other related configuration details for DHCP-enabled clients on your network.
DHCP allows you to use a DHCP server to dynamically assign an IP address to a computer or
other device, such as a printer, on your local network. Every computer on a TCP/IP network must
have a unique IP address, because the IP address and its related subnet mask identify both the
host computer and the subnet to which the computer is attached. By using DHCP, you can ensure
that all computers that are configured as DHCP clients receive an IP address that is appropriate
for their network location and subnet, and by using DHCP options, such as default gateway and
DNS servers, you can automatically provide DHCP clients with the information that they need to
function correctly on your network.
For TCP/IP-based networks, DHCP reduces the complexity and amount of administrative work
involved in reconfiguring computers.
TCP/IP
TCP/IP in Windows Server 2012 is the following:
A routable enterprise networking protocol that supports the connection of your Windowsbased computer to both local area network (LAN) and wide area network (WAN)
environments.
Core technologies and utilities for connecting your Windows-based computer with dissimilar
systems for the purpose of sharing information.
A foundation for gaining access to global Internet services, such as the World Wide Web and
File Transfer Protocol (FTP) servers.
TCP/IP provides basic TCP/IP utilities that enable Windows-based computers to connect and
share information with other Microsoft and non-Microsoft systems, including:
Windows 8
Windows 7
Windows Vista
Windows XP
Internet hosts
IBM mainframes
UNIX systems
Network-ready printers, such as HP LaserJet series printers that use HP JetDirect cards
Note
This guide also includes instructions for adding optional Network Policy Server (NPS) and
Web Server (IIS) servers to your network topology to provide the foundation for secure
network access solutions, such as 802.1X wired and wireless deployments that you can
implement using Core Network Companion guides. For more information, see Deploying
optional features for network access authentication and Web services.
Note
Important
Active Directory Domain Services global catalog and DNS server DC1
Both Active Directory Domain Services (AD DS) and Domain Name System (DNS) are installed
on this server, named DC1, which provides directory and name resolution services to all
computers and devices on the network.
DHCP server DHCP1
The DHCP server, named DHCP1, is configured with a scope that provides Internet Protocol (IP)
address leases to computers on the local subnet. The DHCP server can also be configured with
additional scopes to provide IP address leases to computers on other subnets if DHCP forwarding
is configured on routers.
Client computers
Client computers running Windows 8, Windows 7, and Windows Vista are configured by default
as DHCP clients, which obtain IP addresses and DHCP options automatically from the DHCP
server.
Planning subnets
Planning subnets
In Transmission Control Protocol/Internet Protocol (TCP/IP) networking, routers are used to
interconnect the hardware and software used on different physical network segments called
subnets. Routers are also used to forward IP packets between each of the subnets. Determine
the physical layout of your network, including the number of routers and subnets you need, before
proceeding with the instructions in this guide.
In addition, to configure the servers on your network with static IP addresses, you must determine
the IP address range that you want to use for the subnet where your core network servers are
located. In this guide, the private IP address ranges 10.0.0.1 10.0.0.254 and 10.0.1.1
10.0.1.254 are used as examples, but you can use any private IP address range that you prefer.
After you select the IP address ranges that you want to use for each subnet, ensure that
you configure your routers with an IP address from the same IP address range as that
Important
used on the subnet where the router is installed. For example, if your router is configured
by default with an IP address of 192.168.1.1, but you are installing the router on a subnet
with an IP address range of 10.0.0.0/24, you must reconfigure the router to use an IP
address from the 10.0.0.0/24 IP address range.
The following recognized private IP address ranges are specified by Internet Request for
Comments (RFC) 1918:
10.0.0.0 10.255.255.255
172.16.0.0 172.31.255.255
192.168.0.0 192.168.255.255
When you use the private IP address ranges as specified in RFC 1918, you cannot connect
directly to the Internet using a private IP address because requests going to or from these
addresses are automatically discarded by Internet service provider (ISP) routers. To add Internet
connectivity to your core network later, you must contract with an ISP to obtain a public IP
address.
When using private IP addresses, you must use some type of proxy or network address
translation (NAT) server to convert the private IP address ranges on your local network to
a public IP address that can be routed on the Internet. Most routers provide NAT
services, so selecting a router that is NAT-capable should be fairly simple.
For more information, see Planning the deployment of DHCP1.
DNS-DEN-01. This name represents the DNS server in Denver, Colorado. If additional DNS
servers are added in Denver, the numeric value in the name can be incremented, as in DNSDEN-02 and DNS-DEN-03.
DNS-SPAS-01. This name represents the DNS server in South Pasadena, California.
For this guide, the server naming convention is very simple, and consists of the primary server
function and a number. For example, the domain controller is named DC1 and the DHCP server
is named DHCP1.
Note
It is recommended that you choose a naming convention before you install your core network
using this guide.
Example values
IP address
10.0.0.2
Subnet mask
255.255.255.0
10.0.0.1
10.0.0.2
If you plan on deploying more than one DNS server, you can also plan the Alternate DNS
Server IP address.
Important
Windows Server 2003. This forest functional level supports only Windows Server 2003
domain controllers and domain controllers that are running later versions of the Windows
Server operating system.
Windows Server 2008. This forest functional level supports only domain controllers that are
running Windows Server 2008 and later versions of the Windows Server operating system.
Windows Server 2008 R2. This forest functional level supports Windows Server 2008 R2
domain controllers and domain controllers that are running later versions of the Windows
Server operating system.
Windows Server 2012. This forest functional level supports Windows Server 2012 domain
controllers and domain controllers that are running later versions of the Windows Server
operating system.
If you are deploying a new domain in a new forest and all of your domain controllers will be
running Windows Server 2012, it is recommended that you configure AD DS with the Windows
Server 2012 forest functional level during AD DS installation.
After the forest functional level is raised, domain controllers that are running earlier
operating systems cannot be introduced into the forest. For example, if you raise the
forest functional level to Windows Server 2008 R2, domain controllers running
Windows Server 2003 or Windows Server 2008 cannot be added to the forest.
Example configuration items for AD DS are provided in the following table.
Configuration items:
Example values:
Examples:
corp.contoso.com
example.com
E:\Configuration\
Or accept the default location.
Configuration items:
Example values:
E:\Configuration\
E:\Configuration\
J*p2leO4$F
AD DS_AnswerFile
Example values
Zone type
Network ID = 10.0.0.
Dynamic Updates
Note
Create user accounts in Active Directory Users and Computers. Each user must have an
Active Directory Domain Services user account in Active Directory Users and Computers. For
more information, see Create a User Account in Active Directory Users and Computers.
Ensure the correct IP address configuration. To join a computer to the domain, the computer
must have an IP address. In this guide, servers are configured with static IP addresses and
client computers receive IP address leases from the DHCP server. For this reason, the DHCP
server must be deployed before you join clients to the domain. For more information, see
Deploying DHCP1.
Join the computer to the domain. Any computer that provides or accesses network resources
must be joined to the domain. For more information, see Joining Server Computers to the
Domain and Logging On and Joining Client Computers to the Domain and Logging On.
Configure routers to forward DHCP broadcast messages across subnets and configure
multiple scopes on the DHCP server, one scope per subnet.
In most cases, configuring routers to forward DHCP broadcast messages is more cost effective
than deploying a DHCP server on each physical segment of the network.
A range of IP addresses from which to include or exclude addresses used for DHCP service
lease offerings.
A subnet mask, which determines the subnet prefix for a given IP address.
Lease duration values, which are assigned to DHCP clients that receive dynamically
allocated IP addresses.
Any DHCP scope options configured for assignment to DHCP clients, such as DNS server IP
address and router/default gateway IP address.
Reservations are optionally used to ensure that a DHCP client always receives the same IP
address.
Before deploying your servers, list your subnets and the IP address range you want to use for
each subnet.
This subnet mask number is 16 one-bits followed by 16 zero-bits, indicating that the network ID
and host ID sections of this IP address are both 16 bits in length. Normally, this subnet mask is
displayed in dotted decimal notation as 255.255.0.0.
The following table displays subnet masks for the Internet address classes.
Address class
Subnet mask
Class A
255.0.0.0
Class B
255.255.0.0
Class C
255.255.255.0
When you create a scope in DHCP and you enter the IP address range for the scope, DHCP
provides these default subnet mask values. Typically, default subnet mask values are acceptable
for most networks with no special requirements and where each IP network segment corresponds
to a single physical network.
In some cases, you can use customized subnet masks to implement IP subnetting. With IP
subnetting, you can subdivide the default host ID portion of an IP address to specify subnets,
which are subdivisions of the original class-based network ID.
By customizing the subnet mask length, you can reduce the number of bits that are used for the
actual host ID.
To prevent addressing and routing problems, you should make sure that all TCP/IP computers on
a network segment use the same subnet mask and that each computer or device has an unique
IP address.
Example values
10.0.0.1
10.0.0.25
Example values
Ethernet
DC1.corp.contoso.com
10.0.0.2
1. Primary Subnet
2. Starting IP Address
2. 10.0.0.1
3. Ending IP Address
3. 10.0.0.254
4. Subnet Mask
4. 255.255.255.0
5. 10.0.0.1
6. Lease duration
6. 8 days
Not enabled
Notes
Notes
4. Deploying DHCP1
5. Joining Client Computers to the Domain and Logging On
6. Deploying optional features for network access authentication and Web services
Equivalent Windows PowerShell commands are provided for most procedures in this guide.
Before running these cmdlets in Windows PowerShell, replace example values with values
that are appropriate for your network deployment. In addition, you must enter each cmdlet on
a single line in Windows PowerShell. In this guide, individual cmdlets might appear on several
lines due to formatting constraints and the display of the document by your browser or other
application.
The procedures in this guide do not include instructions for those cases in which the User
Account Control dialog box opens to request your permission to continue. If this dialog box
opens while you are performing the procedures in this guide, and if the dialog box was
opened in response to your actions, click Continue.
You can use the following sections to perform these actions for each server.
Membership in Administrators, or equivalent, is the minimum required to perform these
procedures.
ComputerName
Restart-Computer
1. In Server Manager, click Local Server. The computer Properties are displayed in the
details pane.
2. In Properties, in Computer name, click the existing computer name. The System
Properties dialog box opens. Click Change. The Computer Name/Domain Changes
dialog box opens.
Note
Notes
3. In the Computer Name/Domain Changes dialog box, in Computer name, type a new
name for your computer. For example, if you want to name the computer DC1, type DC1.
4. Click OK twice, and then click Close. If you want to restart the computer immediately to
complete the name change, click Restart Now. Otherwise, click Restart Later.
For information on how to rename computers that are running other Microsoft operating
systems, see Appendix A - Renaming computers.
1. In the task bar, right-click the Network icon, and then click Open Network and Sharing
Center.
2. In Network and Sharing Center, click Change adapter settings. The Network
Connections folder opens and displays the available network connections.
3. In Network Connections, right-click the connection that you want to configure, and then
click Properties. The network connection Properties dialog box opens.
4. In the network connection Properties dialog box, in This connection uses the
following items, select Internet Protocol Version 4 (TCP/IPv4), and then click
Properties. The Internet Protocol Version 4 (TCP/IPv4) Properties dialog box opens.
5. In Internet Protocol Version 4 (TCP/IPv4) Properties, on the General tab, click Use
the following IP address. In IP address, type the IP address that you want to use.
6. Press tab to place the cursor in Subnet mask. A default value for subnet mask is entered
automatically. Either accept the default subnet mask, or type the subnet mask that you
want to use.
7. In Default gateway, type the IP address of your default gateway.
Note
You must configure Default gateway with the same IP address that you use on
the local area network (LAN) interface of your router. For example, if you have a
router that is connected to a wide area network (WAN) such as the Internet as
Note
well as to your LAN, configure the LAN interface with the same IP address that
you will then specify as the Default gateway. In another example, if you have a
router that is connected to two LANs, where LAN A uses the address range
10.0.0.0/24 and LAN B uses the address range 192.168.0.0/24, configure the
LAN A router IP address with an address from that address range, such as
10.0.0.1. In addition, in the DHCP scope for this address range, configure
Default gateway with the IP address 10.0.0.1. For the LAN B, configure the LAN
B router interface with an address from that address range, such as 192.168.0.1,
and then configure the LAN B scope 192.168.0.0/24 with a Default gateway
value of 192.168.0.1.
8. In Preferred DNS server, type the IP address of your DNS server. If you plan to use the
local computer as the preferred DNS server, type the IP address of the local computer.
9. In Alternate DNS Server, type the IP address of your alternate DNS server, if any. If you
plan to use the local computer as an alternate DNS server, type the IP address of the
local computer.
10. Click OK, and then click Close.
For information on how to configure a static IP address on computers that are running
other Microsoft operating systems, see Appendix B - Configuring static IP addresses.
Deploying DC1
To deploy DC1, which is the computer running Active Directory Domain Services (AD DS) and
DNS, you must complete these steps in the following order:
Add a Group
Administrative privileges
If you are installing a small network and are the only administrator for the network, it is
recommended that you create a user account for yourself, and then add your user account as a
member of both Enterprise Admins and Domain Admins. Doing so will make it easier for you to
act as the administrator for all network resources. It is also recommended that you log on with this
account only when you need to perform administrative tasks, and that you create a separate user
account for performing non-IT related tasks.
If you have a larger organization with multiple administrators, refer to AD DS documentation to
determine the best group membership for organization employees.
Differences between domain user accounts and user accounts on the local computer
Notes
One of the advantages of a domain-based infrastructure is that you do not need to create user
accounts on each computer in the domain. This is true whether the computer is a client computer
or a server.
Because of this, you should not create user accounts on each computer in the domain. Create all
user accounts in Active Directory Users and Computers and use the preceding procedures to
assign group membership. By default, all user accounts are members of the Domain Users
group.
All members of the Domain Users group can log on to any client computer after it is joined to the
domain.
You can configure user accounts to designate the days and times that the user is allowed to log
on to the computer. You can also designate which computers each user is allowed to use. To
configure these settings, open Active Directory Users and Computers, locate the user account
that you want to configure, and double-click the account. In the user account Properties, click the
Account tab, and then click either Logon Hours or Log On To.
Install AD DS and DNS for a New Forest
You can use this procedure to install Active Directory Domain Services (AD DS) and DNS and to
create a new domain in a new forest.
Membership in Administrators is the minimum required to perform this procedure.
To perform this procedure by using Windows PowerShell, open PowerShell and type the
following cmdlets on separate lines, and then press ENTER. You must also replace the
domain name in this example with the value that you want to use.
Install-WindowsFeature AD-Domain-Services -IncludeManagementTools
Install-ADDSForest -DomainName corp.contoso.com
1. On DC1, in Server Manager, click Manage, and then click Add Roles and Features.
The Add Roles and Features Wizard opens.
2. In Before You Begin, click Next.
Note
The Before You Begin page of the Add Roles and Features Wizard is not
displayed if you have previously selected Skip this page by default when the
Add Roles and Features Wizard was run.
3. In Select Installation Type, ensure that Role-Based or feature-based installation is
selected, and then click Next.
4. In Select destination server, ensure that Select a server from the server pool is
selected. In Server Pool, ensure that the local computer is selected. Click Next.
5. In Select server roles, in Roles, click Active Directory Domain Services. In Add
features that are required for Active Directory Domain Services, click Add Features.
Notes
Click Next.
6. In Select features, click Next, and in Active Directory Domain Services, review the
information that is provided, and then click Next.
7. In Confirm installation selections, click Install. The Installation progress page displays
status during the installation process. When the process completes, in the message
details, click Promote this server to a domain controller. The Active Directory Domain
Services Configuration Wizard opens.
8. In Deployment Configuration, select Add a new forest. In Root domain name, type
the fully qualified domain name (FQDN) for your domain. For example, if your FQDN is
corp.contoso.com, type corp.contoso.com. Click Next.
9. In Domain Controller Options, in Select functional level of the new forest and root
domain, select the forest functional level and domain functional level that you want to
use. In Specify domain controller capabilities, ensure that Domain Name System
(DNS) server and Global Catalog (GC) are selected. In Password and Confirm
password, type the Directory Services Restore Mode (DSRM) password that you want to
use. Click Next.
10. In DNS Options, click Next.
11. In Additional Options, verify the NetBIOS name that is assigned to the domain, and
change it only if necessary. Click Next.
12. In Paths, in Specify the location of the AD DS database, log files, and SYSVOL, do
one of the following:
Type folder locations that you want to use for Database folder, Log files folder, and
SYSVOL folder.
To add a group
5.
After you press ENTER, type the password for the user account. The account is created
and, by default, is granted membership to the Domain Users group.
With the following cmdlet, you can assign additional group memberships for the new user
account. The example below adds User1 to the Domain Admins and Enterprise Admins
groups. Ensure before running this command that you change the user account name,
domain name, and groups to match your requirements.
Add-ADPrincipalGroupMembership -Identity
"CN=User1,CN=Users,DC=corp,DC=contoso,DC=com" -MemberOf "CN=Enterprise
Admins,CN=Users,DC=corp,DC=contoso,DC=com","CN=Domain
Admins,CN=Users,DC=corp,DC=contoso,DC=com"
1. On DC1, in Server Manager, click Tools, and then click Active Directory Users and
Computers. The Active Directory Users and Computers MMC opens. If it is not already
selected, click the node for your domain. For example, if your domain is
corp.contoso.com, click corp.contoso.com.
2. In the details pane, right-click the folder in which you want to add a user account.
Where?
3. Point to New, and then click User. The New Object User dialog box opens.
4. In First name, type the user's first name.
5. In Initials, type the user's initials.
6. In Last name, type the user's last name.
7. Modify Full name to add initials or reverse the order of first and last names.
8. In User logon name, type the user logon name. Click Next.
9. In New Object - User, in Password and Confirm password, type the user's password,
and then select the appropriate password options.
10. Click Next, review the new user account settings, and then click Finish.
Add a Group
You can use this procedure to create a new group in Active Directory Users and Computers
Microsoft Management Console (MMC).
Membership in Domain Admins, or equivalent, is the minimum required to perform this
procedure.
1. On DC1, in Server Manager, click Tools, and then click Active Directory Users and
Active Directory Users and Computers/domain node/folder that contains the group
3. In the details pane, right-click the object that you want to add to a group, such as a user
or computer, and then click Properties. The objects Properties dialog box opens. Click
the Member of tab.
4. On the Member of tab, click Add.
5. In Enter the object names to select, type the name of the group to which you want to
add the object, and then click OK.
6. To assign group membership to other users, groups or computers, repeat steps 4 and 5
of this procedure.
Notes
7.
Configure a DNS Reverse Lookup Zone
You can use this procedure to configure a reverse lookup zone in Domain Name System (DNS).
Membership in Domain Admins is the minimum required to perform this procedure.
For medium and large organizations, its recommended that you configure and use the
DNSAdmins group in Active Directory Users and Computers. For more information, see
Additional Technical Resources
To perform this procedure by using Windows PowerShell, open PowerShell and type the
following cmdlet on one line, and then press ENTER. You must also replace the DNS reverse
lookup zone and zonefile names in this example with the values that you want to use. Ensure
that you reverse the network ID for the reverse zone name. For example, if the network ID is
192.168.0, create the reverse lookup zone name 0.168.192.in-addr.arpa.
Add-DnsServerPrimaryZone 0.0.10.in-addr.arpa -ZoneFile 0.0.10.in-addr.arpa.dns
1. On DC1, in Server Manager, click Tools, and then click DNS. The DNS MMC opens.
2. In DNS, if it is not already expanded, double-click the server name to expand the tree.
For example, if the DNS server name is DC1, double-click DC1.
3. Select Reverse Lookup Zones, right-click Reverse Lookup Zones, and then click New
Zone. The New Zone Wizard opens.
4. In Welcome to the New Zone Wizard, click Next.
5. In Zone Type, select Primary zone.
6. If your DNS server is a writeable domain controller, ensure that Store the zone in Active
Directory is selected. Click Next.
7. In Active Directory Zone Replication Scope, select To all DNS servers running on
domain controllers in this domain, unless you have a specific reason to choose a
different option. Click Next.
8. In the first Reverse Lookup Zone Name page, select IPv4 Reverse Lookup Zone. Click
Next.
9. In the second Reverse Lookup Zone Name page, do one of the following:
In Network ID, type the network ID of your IP address range. For example, if your IP
address range is 10.0.0.1 through 10.0.0.254, type 10.0.0.
In Reverse lookup zone name, your IPv4 reverse lookup zone name is
automatically added. Click Next.
10. In Dynamic Update, select the type of dynamic updates that you want to allow. Click
Next.
11. In Completing the New Zone Wizard, review your choices, and then click Finish.
Notes
Note
To log
joinon
computers
to the domain
running
using
Windows
computers
Server
running
2012 toWindows
the domain
Server 2012
8.
9.
servers to the domain and log on to the servers in order to install additional technologies, such as
Dynamic Host Configuration Protocol (DHCP).
On all servers that you are deploying, except for the server running AD DS, do the following:
1. Complete the procedures provided in Configuring All Servers.
2. Use the instructions in the following two procedures to join your servers to the domain and to
log on to the servers to perform additional deployment tasks:
To perform this procedure by using Windows PowerShell, open PowerShell and type the
following cmdlet, and then press ENTER. You must also replace the domain name with
the name that you want to use.
Add-Computer -DomainName corp.contoso.com
When you are prompted to do so, type the user name and password for an account that
has permission to join a computer to the domain. To restart the computer, type the
following command and press ENTER.
Restart-Computer
1. In Server Manager, click Local Server. In the details pane, click WORKGROUP. The
System Properties dialog box opens.
2. In the System Properties dialog box, click Change. The Computer Name/Domain
Changes dialog box opens.
3. In Computer Name, in Member of, click Domain, and then type the name of the domain
that you want to join. For example, if the domain name is corp.contoso.com, type
corp.contoso.com.
4. Click OK. The Windows Security dialog box opens.
5. In Computer Name/Domain Changes, in User name, type the user name, and in
Password, type the password, and then click OK. The Computer Name/Domain
Changes dialog box opens, welcoming you to the domain. Click OK.
6. The Computer Name/Domain Changes dialog box displays a message indicating that
you must restart the computer to apply the changes. Click OK.
7. On the System Properties dialog box, on the Computer Name tab, click Close. The
Microsoft Windows dialog box opens, and displays a message, again indicating that
you must restart the computer to apply the changes. Click Restart Now.
For information on how to join computers that are running other Microsoft operating
systems to the domain, see Appendix C Joining computers to the domain.
1. Log off the computer, or restart the computer.
2. Press CTRL + ALT + DELETE. The logon screen appears.
3. Click the left arrow, and then click Other User.
4. In User name, type your domain and user name in the format domain\user. For example,
Note
Notes
Deploying DHCP1
Before deploying this component of the core network, you must do the following:
Perform the steps in the section Joining Server Computers to the Domain and Logging On.
To deploy DHCP1, which is the computer running the Dynamic Host Configuration Protocol
(DHCP) server role, you must complete these steps in the following order:
To install DHCP
10.
opens.
2. In DHCP, double-click the server name. For example, if the DHCP server name is
DHCP1.corp.contoso.com, double-click DHCP1.corp.contoso.com.
3. Right-click IPv4, and then click New Scope. The New Scope Wizard opens.
4. In Welcome to the New Scope Wizard, click Next.
5. In Scope Name, in Name, type a name for the scope. For example, type Subnet 1.
6. In Description, type a description for the new scope, and then click Next.
7. In IP Address Range, do the following:
a. In Start IP address, type the IP address that is the first IP address in the range. For
example, type 10.0.0.1.
b. In End IP address, type the IP address that is the last IP address in the range. For
example, type 10.0.0.254. Values for Length and Subnet mask are entered
automatically, based on the IP address you entered for Start IP address.
c.
If necessary, modify the values in Length or Subnet mask, as appropriate for your
addressing scheme.
d. Click Next.
8. In Add Exclusions, do the following:
a. In Start IP address, type the IP address that is the first IP address in the exclusion
range. For example, type 10.0.0.1.
b. In End IP address, type the IP address that is the last IP address in the exclusion
range, For example, type 10.0.0.15.
9. Click Add, and then click Next.
10. In Lease Duration, modify the default values for Days, Hours, and Minutes, as
appropriate for your network, and then click Next.
11. In Configure DHCP Options, select Yes, I want to configure these options now, and
then click Next.
12. In Router (Default Gateway), do one of the following:
In IP address, type the IP address of your router or default gateway. For example,
type 10.0.0.1. Click Add, and then click Next.
Click Resolve. The IP address of the DNS server is added in IP address. Click Add,
wait for DNS server IP address validation to complete, and then click Next.
14. In WINS Servers, because you do not have WINS servers on your network, click Next.
15. In Activate Scope, select Yes, I want to activate this scope now.
16. Click Next, and then click Finish.
Important
Notes
To log
joinon
computers
to the domain
running
using
Windows
computers
8 to the
running
domain
Windows 8
12.
13.
To create new scopes for additional subnets, repeat this procedure. Use a different IP
address range for each subnet that you plan to deploy, and ensure that DHCP message
forwarding is enabled on all routers that lead to other subnets.
When you are prompted to do so, type the user name and password for an account that
has permission to join a computer to the domain. To restart the computer, type the
following command and press ENTER.
Restart-Computer
Note
CORP\User-01.
5. In Password, type your domain password, and then click the arrow, or press ENTER.
The following sections provide information on adding NPS and Web servers to your network.
Deploying NPS1
Deploying WEB1
Deploying NPS1
The Network Policy Server (NPS) server is installed as a preparatory step for deploying other
network access technologies, such as virtual private network (VPN) servers, wireless access
points, and 802.1X authenticating switches. In addition, installing NPS prepares your network for
the deployment of Network Access Protection (NAP).
Network Policy Server (NPS) allows you to centrally configure and manage network policies with
the following three features: Remote Authentication Dial-In User Service (RADIUS) server,
RADIUS proxy, and Network Access Protection (NAP) policy server.
NPS is an optional component of a core network, but you should install NPS if any of the
following are true:
You are planning to expand your network to include remote access servers that are
compatible with the RADIUS protocol, such as a computer running Windows Server 2012,
Windows Server 2008 R2 or Windows Server 2008 and Routing and Remote Access service,
Terminal Services Gateway, or Remote Desktop Gateway.
Perform the steps in the section Joining Server Computers to the Domain and Logging On
To deploy NPS1, which is the computer running the Network Policy Server (NPS) role service of
the Network Policy and Access Services server role, you must complete this step:
Plan the user accounts database. By default, if you join the server running NPS to an Active
Directory domain, NPS performs authentication and authorization using the AD DS user
accounts database. In some cases, such as with large networks that use NPS as a RADIUS
Note
Notes
To install NPS
14.
proxy to forward connection requests to other RADIUS servers, you might want to install NPS
on a non-domain member computer.
Plan the use of Network Access Protection (NAP). With some NAP enforcement methods, it
is required that you install NPS on a specific server. For example, if you deploy NAP with
DHCP, NPS must be installed on the DHCP server.
Plan RADIUS accounting. NPS allows you to log accounting data to a SQL Server database
or to a text file on the local computer. If you want to use SQL Server logging, plan the
installation and configuration of your server running SQL Server.
1. On NPS1, in Server Manager, click Manage, and then click Add Roles and Features.
The Add Roles and Features Wizard opens.
2. In Before You Begin, click Next.
Note
The Before You Begin page of the Add Roles and Features Wizard is not
displayed if you have previously selected Skip this page by default when the
Add Roles and Features Wizard was run.
3. In Select Installation Type, ensure that Role-Based or feature-based installation is
selected, and then click Next.
4. In Select destination server, ensure that Select a server from the server pool is
selected. In Server Pool, ensure that the local computer is selected. Click Next.
5. In Select Server Roles, in Roles, select Network Policy and Access Services, and
Deploying WEB1
The Web Server (IIS) role in Windows Server 2012 provides a secure, easy-to-manage, modular
and extensible platform for reliably hosting websites, services, and applications. With IIS 8 you
can share information with users on the Internet, an intranet, or an extranet. IIS 8 is a unified web
platform that integrates IIS, ASP.NET, FTP services, PHP, and Windows Communication
Foundation (WCF).
In addition to allowing you to publish a CRL for access by domain member computers, the Web
Server (IIS) server role allows you to use the Web Server (IIS) role to set up and manage multiple
websites, web applications, and FTP sites. IIS8 also provides the following benefits:
Maximize web security through a reduced server foot print and automatic application
isolation.
Easily deploy and run ASP.NET, classic ASP, and PHP web applications on the same server.
Notes
Achieve application isolation by giving worker processes a unique identity and sandboxed
configuration by default, further reducing security risks.
Easily add, remove, and even replace built-in IIS components with custom modules, suited
for customer needs.
Speed up your website through built-in dynamic caching and enhanced compression.
To deploy WEB1, which is the computer that is running the Web Server (IIS) server role, you must
do the following:
Perform the steps in the section Joining Server Computers to the Domain and Logging
On
1. In Server Manager, click Manage, and then click Add Roles and Features. The Add
Roles and Features Wizard opens.
2. In Before You Begin, click Next.
Note
The Before You Begin page of the Add Roles and Features Wizard is not
displayed if you have previously selected Skip this page by default when the
Add Roles and Features Wizard was run.
3. On the Installation Type page, click Next.
4. On the Server Selection page, click Next.
5. On the Server Roles page, select Web Server (IIS), and then click Next.
6. Click Next until you have accepted all of the default web server settings, and then click
Install.
7. Verify that all installations were successful, and then click Close.
Windows Server 2008 and Windows Server 2008 R2 Technical Library Resources
TCP/IP at http://go.microsoft.com/fwlink/?LinkId=103329
Appendices A through E
The following sections contain additional configuration information for computers that are running
operating systems other than Windows Server 2012 and Windows 8, as well as a network
preparation worksheet to assist you with your deployment.
1. Appendix A - Renaming computers
2. Appendix B - Configuring static IP addresses
3. Appendix C Joining computers to the domain
4. Appendix D Log on to the domain
5. Appendix E - Core Network Planning Preparation Sheet
Important
To join computers running Windows Server 2008 R2 and Windows 7 to the domain
22.
select Internet Protocol (TCP/IP), and then click Properties. The Internet Protocol
(TCP) Properties dialog box opens.
4. In Internet Protocol Version 4 (TCP/IPv4) Properties, on the General tab, click Use
the following IP address. In IP address, type the IP address that you want to use.
5. In Subnet mask, either accept the default subnet mask, or type the subnet mask that you
want to use.
6. In Default gateway, type the IP address of your default gateway.
7. In Preferred DNS server, type the IP address of your DNS server.
8. In Alternate DNS Server, type the IP address of your alternate DNS server, if any.
9. Click OK, and then click Close.
To join computers running Windows Server 2008 and Windows Vista to the domain
23.
4. Click Change. The Computer Name/Domain Changes dialog box opens.
5. In Computer Name, in Member of, select Domain, and then type the name of the
domain you want to join. For example, if the domain name is corp.contoso.com, type
corp.contoso.com.
6. Click OK. The Windows Security dialog box opens.
7. In Computer Name/Domain Changes, in User name, type the user name, and in
Password, type the password, and then click OK. The Computer Name/Domain
Changes dialog box opens, welcoming you to the domain. Click OK.
8. The Computer Name/Domain Changes dialog box displays a message indicating that
you must restart the computer to apply the changes. Click OK.
9. On the System Properties dialog box, on the Computer Name tab, click Close. The
Microsoft Windows dialog box opens, and displays a message, again indicating that
you must restart the computer to apply the changes. Click Restart Now.
Logjoin
To
on computers
to the domain
running
usingWindows
computers
Server
running
2003Windows
and Windows
ServerXP
2008
to the
R2 domain
and
Windows
7
24.
25.
For planning and tracking purposes, spaces are provided in each table for you to enter the values
used for your deployment. If you log security-related values in these tables, you should store the
information in a secure location.
The following links lead to the sections in this topic that provide configuration items and example
values that are associated with the deployment procedures presented in this guide.
1. Installing Active Directory Domain Services and DNS
2. Installing DHCP
Configuration items
Example values
IP address
10.0.0.2
Subnet mask
255.255.255.0
Default gateway
10.0.0.1
127.0.0.1
10.0.0.15
Values
Configuration item
Example value
Computer name
DC1
Value
Configuration items
Example values
corp.contoso.com
E:\Configuration\
E:\Configuration\
E:\Configuration\
J*p2leO4$F
AD DS_AnswerFile
Values
Example values
Zone type:
Primary zone
Secondary zone
Stub zone
Zone type
Selected
Not selected
(IP type)
Values
Configuration items
Example values
10.0.0
Values
(network ID)
Installing DHCP
The tables in this section list configuration items for pre-installation and installation of DHCP.
Pre-installation configuration items for DHCP
The following tables list pre-installation configuration items as described in Configuring All
Servers:
Configuration items
Example values
IP address
10.0.0.3
Subnet mask
255.255.255.0
Default gateway
10.0.0.1
10.0.0.2
10.0.0.15
Values
Configuration item
Example value
Computer name
DHCP1
Value
Example values
Ethernet
DC1
10.0.0.2
Values
Configuration items
Example values
10.0.0.15
Scope name
Corp1
Starting IP address
10.0.0.1
Ending IP address
10.0.0.254
Subnet mask
255.255.255.0
10.0.0.1
Lease duration
8 days
Not enabled
Values
Example values
Scope name
Corp1
Scope description
10.0.0.1
10.0.0.15
Values
Example values
Corp2
Scope description
10.0.1.1
Start IP address
(IP address range)
End IP address
10.0.1.254
Values
Configuration items
Example values
Length
Subnet mask
255.255.255.0
10.0.1.1
10.0.1.15
Lease duration
Days
Hours
Values
Minutes
Router (default gateway)
10.0.1.1
IP address
DNS parent domain
corp.contoso.com
DNS server
10.0.0.2
IP address
Configuration items
Example values
IP address
10.0.0.4
Subnet mask
255.255.255.0
Default gateway
10.0.0.1
10.0.0.2
10.0.0.15
Values
Configuration item
Example value
Computer name
NPS1
Value