Professional Documents
Culture Documents
Microsoft Corporation
Published: November, 2007
Authors: James McIllece and Brit Weston
Editor: Allyson Adley
Technical Contributors: Shyam Seshadri
Abstract
The Windows Server® 2008 Foundation Network Guide provides instructions on how to plan and
deploy 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
Windows server components:
• The Active Directory Domain Services (AD DS) server role
• The Domain Name System (DNS) server role
• The Dynamic Host Configuration Protocol (DHCP) server role
• The Network Policy Server (NPS) role service of the Network Policy and Access Services
server role
• The Windows Internet Name Service (WINS) feature
• Transmission Control Protocol/Internet Protocol version 4 (TCP/IP) connections on
individual servers
This guide also serves as a foundation for companion guides that show you how to deploy
additional network technologies in Windows Server 2008.
The information contained in this document represents the current view of Microsoft Corporation
on the issues discussed as of the date of publication. Because Microsoft must respond to
changing market conditions, it should not be interpreted to be a commitment on the part of
Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the
date of publication.
This White Paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES,
EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT.
Complying with all applicable copyright laws is the responsibility of the user.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual
property rights covering subject matter in this document. Except as expressly provided in any
written license agreement from Microsoft, the furnishing of this document does not give you any
license to these patents, trademarks, copyrights, or other intellectual property.
Unless otherwise noted, the example companies, organizations, products, domain names, e-mail
addresses, logos, people, places, and events depicted herein are fictitious, and no association
with any real company, organization, product, domain name, e-mail address, logo, person, place,
or event is intended or should be inferred.
Microsoft, Active Directory, Windows, Windows NT, and Windows Server are either registered
trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
4
About this guide
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.
Note
This guide depicts the use of four server computers. In some cases, such as on small
networks, you can use fewer servers. For example, you can install DHCP and WINS on
the same server rather than on separate servers.
Note
Client computers running Windows Vista and Windows XP are configured by default to
receive IP address leases from the DHCP server. Therefore, no additional DHCP or
Internet Protocol version 4 (IPv4) configuration of client computers is required.
5
Technology Overviews
The following sections provide brief overviews of the required and optional technologies used to
create a foundation 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 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 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.
Every computer on a TCP/IP network must have an unique IP address. The IP address (together
with its related subnet mask) identifies both the host computer and the subnet to which it is
attached. When you move a computer to a different subnet, the IP address must be changed.
DHCP allows you to dynamically assign an IP address to a client from a DHCP server IP address
database on your local network.
For TCP/IP-based networks, DHCP reduces the complexity and amount of administrative work
involved in reconfiguring computers.
WINS (optional)
While DNS is a required component of a foundation network, WINS is optional because, like
DNS, it is a naming service. In some cases, you might not need both DNS and WINS, but older
operating systems and applications might require WINS. For medium to small networks, WINS is
extremely easy to install and manage, and it is not resource-intensive. If you are in doubt about
whether you need WINS, you can test your network functionality without it and install it if needed.
WINS provides a distributed database for registering and querying dynamic mappings of NetBIOS
names for computers and groups used on your network. WINS maps NetBIOS names to IP
addresses and was designed to solve the problems arising from NetBIOS name resolution in
routed environments. WINS is the best choice for NetBIOS name resolution in routed networks
that use NetBIOS over TCP/IP.
6
NetBIOS names are used by earlier versions of Windows operating systems to identify and locate
computers and other shared or grouped resources required to register or resolve names for use
on the network.
NetBIOS names are a requirement for establishing networking services in earlier versions of
Windows operating systems. Although the NetBIOS naming protocol can be used with network
protocols other than TCP/IP (such as NetBEUI or IPX/SPX), WINS was designed specifically to
support NetBIOS over TCP/IP (NetBT).
WINS simplifies the management of the NetBIOS namespace in TCP/IP-based networks.
NPS (optional)
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 foundation network, but you should install NPS if any of the
following are true:
• You are planning to expand your network to include any remote access servers that are
compatible with the RADIUS protocol, such as a computer running Windows Server 2008 and
Routing and Remote Access service.
• You plan to deploy NAP.
• You plan to deploy 802.1X wired or wireless access.
TCP/IP
TCP/IP in Windows Server 2008 is the following:
• Networking software based on industry-standard networking protocols.
• A routable, enterprise networking protocol that supports the connection of your Windows-
based 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.
• A robust, scalable, cross-platform, client/server framework.
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 Vista
• Windows Server 2003 operating systems
• Windows XP
• Internet hosts
• Apple Macintosh systems
7
• IBM mainframes
• UNIX systems
• Open VMS systems
• Network-ready printers, such as HP LaserJet series printers that use HP JetDirect cards
8
Foundation Network Components
Following are the components of a foundation network.
9
Router
This deployment guide provides instructions for deploying a foundation network with two subnets
separated by a router that has DHCP forwarding enabled. You can, however, deploy a Layer 2
switch, a Layer 3 switch, or a hub, depending on your requirements and resources. If you deploy
a switch, the switch must be capable of DHCP forwarding or you must place a DHCP server on
each subnet. If you deploy a hub, you are deploying a single subnet and do not need DHCP
forwarding or a second scope on your DHCP server.
DHCP server
The Dynamic Host Configuration Protocol (DHCP) server 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 Vista® and Windows XP are configured by default as DHCP
clients, which obtain IP addresses and DHCP options automatically from the DHCP server.
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 foundation network servers
are located. In this guide, the private IP address range 192.168.1.1 - 192.168.0.254 is used as an
example, but you can use any private 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 foundation network later, you must contract with an ISP to obtain a public IP
address.
Important
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.
For more information, see Planning the deployment of DHCP-01.
11
Planning the Administrator account password
For security reasons, it is important to create a password for the Administrator account and to use
a strong password. In addition, it is recommended that you use a different Administrator account
password for each server on your network.
The following is an example of a strong password.
Note
Strong passwords contain a minimum
of 7 characters that consist of each of
the following: uppercase letters (A, B,
C, lowercase letters (d, e, f), numerals
(0, 1, 2, 3), and keyboard symbols (' ~ !
@ # $ % | /).
IP address 192.168.0.3
12
Configuration items: Example values:
13
• Windows Server 2008. This forest functional level supports Windows Server 2008
domain controllers only.
If you are deploying a new domain in a new forest and all of your domain controllers will be
running Windows Server 2008, it is recommended that you configure AD DS with the Windows
Server 2008 forest functional level during AD DS installation.
Important
After the forest functional level has been raised, domain controllers running earlier
operating systems cannot be introduced into the forest. For example, if you raise the
forest functional level to Windows Server 2008, domain controllers running
Windows 2000 Server or Windows Server 2003 cannot be added to the forest.
Example configuration items for AD DS are provided in the following table.
14
Configuration items: Example values:
15
Configuration Items Example values
Active Directory Zone Replication Scope To all DNS servers in this domain
First Reverse Lookup Zone Name wizard page IPv4 Reverse Lookup Zone
Note
You cannot log on to the domain with a user account that is located in the Security
Accounts Manager (SAM) user accounts database on the local computer.
After the first successful logon with domain logon credentials, the logon settings persist unless
the computer is removed from the domain or the logon settings are manually changed.
Before you log on to the domain:
• Create user accounts in AD DS. 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 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. Fore more information, see
Install Dynamic Host Configuration Protocol (DHCP).
• Join the computer to the domain. Any computer that provides or accesses network
resources must be joined to the domain. For more information, see Join the Computer to the
Domain.
16
replication partners. For simple replication between two servers, one server should be set as
a pull partner and the other as a push partner. Replication can be either manual or automatic.
• Large networks sometimes require more WINS servers for several reasons including,
most importantly, the number of client connections per server. The number of users that each
WINS server can support varies with usage patterns, data storage, and the processing
capabilities of the WINS server computer.
When planning your servers, remember that each WINS server can simultaneously handle
hundreds of registrations and queries per second.
17
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.
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 (as shown in
the preceding table) 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.
18
to other servers, non-DHCP clients, diskless workstations, or Routing and Remote Access and
PPP clients.
It is recommended that you configure your exclusion range with extra addresses to accommodate
future network growth. The following table provides an example exclusion range for a scope with
an IP address range of 192.168.0.1 - 192.168.0.254.
19
Configuration items: Example values:
Note
Specify the IP address of your alternate
WINS server only if an alternate WINS
server is deployed on the network.
20
1. Configuring All Servers
2. Deploying AD-DNS-01
3. Joining Computers to the Domain and Logging On
4. Deploying WINS-01 (optional)
5. Deploying DHCP-01
6. Deploying NPS-01 (optional)
Note
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.
21
To change the Administrator password in Windows Server 2008
1. Log on to the computer using the Administrator account.
2. Click Start, click Control Panel, and then double-click User Accounts.
3. In User Accounts, in Make changes to your user account, click Change your
password.
4. In Change your password, in Current Password, type your password.
5. In New password, type a new password.
6. In Confirm new password, retype the password.
7. In Type a password hint, type a word or phrase that will remind you of your
password or, optionally, leave this field blank.
8. Click Change password.
Windows Vista
Membership in Administrators, or equivalent, is the minimum required to perform this procedure.
Note
If you have previously created a password for the account, the text that appears
in this step is Change the password.
5. If Current password is displayed, in Current password, type the password that you
used when you logged on to the computer.
6. In New password, type a new password.
7. In Confirm new password, retype the password.
8. In Type a password hint, type a word or phrase that will remind you of your
password or, optionally, leave this field blank.
9. Click Create password or Change password.
Note
If this is the first time you have created a password for the Administrator account,
the text that appears in the last step is Create password. If you previously
created a password and are changing that password to a new one, the text that
appears in the last step is Change password.
22
Membership in Administrators, or equivalent, is the minimum required to perform this procedure.
Windows XP
Membership in Administrators, or equivalent, is the minimum required to perform this procedure.
23
opens.
2. In Computer name, domain, and workgroup settings, click Change settings. The
System Properties dialog box opens.
Note
On computers running Windows Vista, before the System Properties dialog box
opens, the User Account Control dialog box opens, requesting permission to
continue. Click Continue to proceed.
3. Click Change. The Computer Name/Domain Changes dialog box opens.
4. In Computer Name, type the name for your computer. For example, if you want to
name the computer AD-DNS-01, type AD-DNS-01.
5. Click OK twice, click Close, and then click Restart Now to restart the computer.
24
Membership in Administrators, or equivalent, is the minimum required to perform these
procedures.
25
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.
Deploying AD-DNS-01
To deploy AD-DNS-01, which is the computer running Active Directory Domain Services (AD DS)
and DNS, you must complete these steps in the following order:
• Perform the steps in the section Configuring All Servers.
• Install AD DS and DNS for a New Forest
• Create a User Account in Active Directory Users and Computers
• Add a Group
• Assign Group Membership
• Configure a DNS Reverse Lookup Zone
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.
26
Note
Members of the Domain Users group cannot log on to computers running
Windows Server® 2008.
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.
Note
The Before You Begin page of the Add Roles Wizard is not displayed if you
have previously selected Do not show this page again when the Add Roles
Wizard was run.
3. In Select Server Roles, in Roles, select Active Directory Domain Services, and
then click Next.
4. In Active Directory Domain Services, click Next.
5. In Confirm Installation Selections, click Install. The Installation Progress page
opens during installation.
6. When installation is complete, in Installation Results, review the information, and
then click Close this wizard and launch the Active Directory Domain Services
Installation Wizard. The Add Roles Wizard closes and the Active Directory Domain
Services Installation Wizard opens. Click Next.
7. In Choose a Deployment Configuration, select Create a new domain in a new
forest. Click Next.
8. In Name the Forest Root Domain, in FQDN of the forest root domain, type the
fully qualified domain name for your domain. For example, if your FQDN is example.com,
type example.com. Click Next.
27
9. In Set Forest Functional Level, select the forest functional level that you want to
use, and then click Next.
10. In Additional Domain Controller Options, in Select additional options for this
domain controller, verify that DNS server is selected, and then click Next. The Active
Directory Domain Services Installation Wizard warning dialog box opens.
11. The warning dialog box informs you that you can create a delegation to this DNS
server manually in the parent zone. Click Yes to continue Active Directory Domain
Services installation.
12. In Location for Database, Log Files, and SYSVOL, do one of the following:
• Accept the default values.
• Type folder locations that you want to use for Database folder, Log files folder,
and SYSVOL folder.
13. Click Next.
14. In Directory Services Restore Mode Administrator Password, in Password, type
a password. In Confirm password, retype the password, and then click Next.
15. In Summary, review your selections.
16. If you want to export settings to an answer file, click Export settings, and specify a
name for the answer file. Click Next.
17. In Completing the Active Directory Domain Services Installation Wizard, click
Finish, and then click Restart Now.
28
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.
To add a group
1. Click Start, click Administrative 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 example.com,
click example.com.
2. In the details pane, right-click the folder in which you want to add a new group.
Where?
• Active Directory Users and Computers/domain node/folder
3. Point to New, and then click Group.
4. In New Object – Group, in Group name, type the name of the new group.
By default, the name you type is also entered as the pre-Windows 2000 name of the new
group.
5. In Group scope, select one of the following options:
• Domain local
• Global
• Universal
6. In Group type, select one of the following options:
• Security
• Distribution
7. Click OK.
29
Assign Group Membership
You can use this procedure to add a user, computer, or group to a group in Active Directory Users
and Computers Microsoft Management Console (MMC).
Note
When you administer a domain, security principals in the parent domain or other trusted
domains are not visible on the Member Of tab of a domain users properties. The only
domain accounts that you can add or view are the present domain groups. Only domain
groups in the present domain are shown, even if the member belongs to other trusted
domain groups.
Membership in Domain Admins, or equivalent is the minimum required to perform this
procedure.
31
Note
If you are logged on to a computer running Windows Server® 2008 with the local
computer’s Administrator account, by default, you can join a computer to the domain with
a user account that is a member of Domain Users in Active Directory Users and
Computers.
In addition, you can use these instructions to join client computers to the domain and to log on to
client computers.
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 sections to join your servers to the domain and to log
on to the servers to perform additional deployment tasks:
• Join the Computer to the Domain
• Log on to the Domain
Important
To join a computer to a domain, you must be logged on to the computer with the local
Administrator account or, if you are logged on to the computer with a user account that
does not have local computer administrative credentials, you must provide the credentials
for the local Administrator account during the process of joining the computer to the
domain. In addition, you must have a user account in the domain to which you want to
join the computer. During the process of joining the computer to the domain, you will be
prompted for your domain account credentials (user name and password).
Windows Server 2008 and Windows Vista
Membership in Domain Users, or equivalent, is the minimum required to perform this procedure.
To join computers running Windows Server 2008 and Windows Vista to the domain
1. Log on to the computer with the local Administrator account.
2. Click Start, right-click Computer, and then click Properties. The System dialog box
opens.
3. In Computer name, domain, and workgroup settings, click Change settings. The
System Properties dialog box opens.
32
Note
On computers running Windows Vista®, before the System Properties dialog
box opens, the User Account Control dialog box opens, requesting permission
to continue. Click Continue to proceed.
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 example.com, type
example.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.
To join computers running Windows Server 2003 and Windows XP to the domain
1. Click Start, right-click My Computer, and then click Properties. The System
Properties dialog box opens.
2. Click Change. The Computer Name Changes dialog box opens.
3. In Computer Name Changes, in Member of, select Domain, and then type the
name of the domain you want to join. For example, if the domain name is example.com,
type example.com.
4. Click OK. The Computer Name Changes dialog box opens. In User name, type the
domain administrator account name, and in Password, type the administrator password,
and then click OK.
5. The Computer Name Changes dialog box opens, welcoming you to the domain.
6. Click OK. The Computer Name Changes dialog box displays a message indicating
that you must restart the computer to apply the changes.
7. Click OK.
8. On the System Properties dialog box, on the Computer Name tab, click OK, to
close the System Properties dialog box. The System Settings Change dialog box
opens, and displays a message, again indicating that you must restart the computer to
apply the changes.
9. Click Yes.
33
Log on to the Domain
You can use these procedures to log on to the domain using computers running
Windows Server® 2008, Windows Vista®, Windows Server 2003, and Windows XP.
Log on to the domain using computers running Windows Server 2008 and
Windows Vista
1. Log off the computer, or restart the computer.
2. Press CTRL + ALT + DELETE. The logon screen appears.
3. Click Switch User, and then click Other User.
4. In User name, type your domain and user name in the format domain\user. For
example, to log on to the domain example.com with an account named User-01, type
example\User-01.
5. In Password, type your domain password, and then click the arrow, or press ENTER.
Log on to the domain using computers running Windows Server 2003 and Windows XP
1. Log off the computer, or restart the computer.
2. Press CTRL + ALT + DELETE. The Log On to Windows dialog box appears.
3. If Log on to is not displayed, click Options.
4. In Log on to, in the drop down list, select your domain. For example, in the
example.com domain, select EXAMPLE.
5. Type your domain and user name in the format domain\user. For example, to log on
to the example.com domain with an account named User-01, type example\User-01.
6. In Password, type your domain password, and then press ENTER.
34
• Perform the steps in the section Configuring All Servers.
• Perform the steps in the section Joining Computers to the Domain and Logging On
To deploy WINS-01, which is the computer running Windows Internet Name Service (WINS), you
must complete this step:
• Install Windows Internet Name Service (WINS)
To install WINS
1. Do one of the following:
a. In Initial Configuration Tasks, in Customize This Server, click Add Features.
The Add Features Wizard opens.
b. Click Start, and then click Server Manager. In the left pane of Server Manager,
click Features, and in the details pane, in Features Summary, click Add Features.
The Add Features Wizard opens.
2. In Select Features, in Features, scroll down the list, select WINS Server, and then
click Next.
3. In Confirm installation selections, click Install.
4. In Installation Results, review your installation results, and then click Close.
Deploying DHCP-01
Before deploying this component of the foundation network, you must do the following:
• Perform the steps in the section Configuring All Servers.
• Perform the steps in the section Joining Computers to the Domain and Logging On.
35
activate the scope after DHCP is installed by using the DHCP Microsoft Management
Console (MMC) and the procedure Activate a DHCP Scope.
• Authorize the DHCP server in Active Directory Domain Services (AD DS) during
installation unless you have reason not to do so. If you authorize the server during
installation, the server is configured to function without additional configuration after the
installation process is complete. If you choose not to authorize the DHCP server during
installation, however, you can authorize the server after DHCP is installed by using the DHCP
MMC and the procedure Authorize a DHCP Server in Active Directory Domain Services.
• Do not enable Configure DHCPv6 Stateless Mode unless you plan to use Internet
Protocol version 6 (IPv6) on your network in addition to or to replace IPv4.
Deploying DHCP
To deploy DHCP-01, which is the computer running the Dynamic Host Configuration Protocol
(DHCP) server role, you must complete these steps in the following order:
• If you plan to deploy Windows Internet Name Service (WINS) on your network, it is
recommended that you perform the steps in the section Deploying WINS-01 (optional) before
installing DHCP.
• Install Dynamic Host Configuration Protocol (DHCP)
• Create an Exclusion Range in DHCP
If you chose not to perform the following actions during DHCP installation, you can perform them
after DHCP is installed:
• Authorize a DHCP Server in Active Directory Domain Services
• Activate a DHCP Scope
After DHCP is installed, you can add more scopes to the server configuration:
• Create a New DHCP Scope
To install DHCP
1. Do one of the following:
a. In Initial Configuration Tasks, in Customize This Server, click Add roles. The
Add Roles Wizard opens.
b. Click Start, and then click Server Manager. In the left pane of Server Manager,
click Roles, and in the details pane, in Roles Summary, click Add Roles. The Add
Roles Wizard opens.
2. In Before You Begin, click Next.
36
Note
The Before You Begin page of the Add Roles Wizard is not displayed if you
have previously selected Do not show this page again when the Add Roles
Wizard was run.
3. In Select Server Roles, in Roles, select DHCP Server, and then click Next.
4. In DHCP Server, click Next.
5. In Select Network Connection Bindings, in Network Connections, select the IP
addresses that are connected to the subnets for which you want to provide DHCP
service, and then click Next.
6. In Specify IPv4 DNS Server Settings, in Parent Domain, verify that the name of the
DNS domain that clients use for name resolution is correct. For example, if your domain
is named example.com, verify that the DNS domain name is example.com.
7. In Preferred DNS server IPv4 address, type the IPv4 address of your preferred
DNS server, and then click Validate. In Alternate DNS server IPv4 Address, type the
IPv4 address of your alternate DNS server, if any, and then click Validate.
Note
If a DNS server responds when you click Validate, the DHCP installation wizard
indicates the specified address for the DNS server is valid. If no DNS server
responds when you click Validate, the DHCP installation wizard returns the
message: The DNS server at the specified IP address is not responding.
8. Click Next. In Specify IPv4 WINS Server Settings, select one of the following:
• If you do not have WINS servers on your network, select WINS is not required
for applications on this network.
• If one or more WINS servers are deployed on your network, select WINS is
required for applications on this network. In Preferred WINS server IP address,
type the IPv4 address of your preferred WINS server. In Alternate WINS server IP
Address, type the IPv4 address of your alternate WINS server, if any, and then click
Next.
9. In Add or Edit DHCP Scopes, click Add. The Add Scope dialog box opens.
10. In the Add Scope dialog box, type values for all required items, and in Subnet Type,
select either Wired or Wireless, depending on the IP address lease duration that you
prefer, and then do one of the following:
• To automatically activate the scope immediately after DHCP installation is
complete, click Activate this scope. If there are computers or devices on the
network that have static IP addresses, do not activate the scope until after you have
created an exclusion range. The exclusion range prevents the DHCP server from
leasing IP addresses that are already in use by a statically configured device.
• To manually activate the scope later, use the DHCP Microsoft Management
Console (MMC).
11. Click OK. This returns you to the Add or Edit DHCP Scopes page. If your network
has multiple subnets that are serviced by this DHCP server, add scopes for each subnet
37
Create an Exclusion Range in DHCP
You can use this procedure to create an exclusion range for an existing DHCP scope.
Membership in DHCP Administrators, or equivalent, is the minimum required to perform this
procedure.
38
Activate a DHCP Scope
You can use this procedure to activate a DHCP scope using the DHCP Microsoft Management
Console (MMC).
Membership in DHCP Administrators, or equivalent, is the minimum required to perform this
procedure.
39
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.10.10.1.
b. In End IP Address, type the IP address that is the last IP address in the
exclusion range, For example, type 10.10.10.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:
• If you do not have routers on your network, click Next.
• In IP address, type the IP address of your router or default gateway. For
example, type 10.10.10.10. Click Add, and then click Next.
13. In Domain Name and DNS Servers, do the following:
a. In Parent Domain, type the name of the DNS domain that clients use for name
resolution. For example, type example.com.
b. In Server name, type the name of the DNS computer that clients use for name
resolution. For example, type AD-DNS-01.
c. Click Resolve. The IP address of the DNS server is added in IP Address. Click
Add, and then click Next.
14. In WINS Servers, do one of the following:
• If you do not have WINS servers on your network, click Next.
• If you have one or more WINS servers deployed on your network, for each WINS
server: In Server name, type the name of the WINS server. For example, type WINS-
01. Click Resolve. The IP address of the WINS server is added in IP Address. Click
Add, and then click Next.
15. In Activate Scope, do one of the following:
• To automatically activate the scope immediately after the steps in the New Scope
Wizard are complete, select Yes, I want to activate this scope now.
• To manually activate the scope later by using the DHCP MMC, select No I will
activate this scope later.
16. Click Next, and then click Finish.
40
• Perform the steps in the section Joining Computers to the Domain and Logging On
To deploy NPS-01, 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:
• Install Network Policy Server (NPS)
To install NPS
1. Do one of the following:
a. In Initial Configuration Tasks, in Customize This Server, click Add roles. The
Add Roles Wizard opens.
b. Click Start, and then click Server Manager. In the left pane of Server Manager,
click Roles, and in the details pane, in Roles Summary, click Add Roles. The Add
Roles Wizard opens.
2. In Before You Begin, click Next.
Note
The Before You Begin page of the Add Roles Wizard is not displayed if you
have previously selected Do not show this page again when the Add Roles
Wizard was run.
3. In Select Server Roles, in Roles, select Network Policy and Access Services,
and then click Next.
4. In Network Policy and Access Services, click Next.
5. In Select Role Services, in Role Services, select Network Policy Server, and then
click Next.
6. In Confirm Installation Selections, click Install.
7. In Installation Results, review your installation results, and then click Close.
41
• Dynamic Host Configuration Protocol (DHCP) in the Windows Server 2008 Technical
Library, at http://go.microsoft.com/fwlink/?LinkId=96419
• Network Access Protection in the Windows Server 2008 Technical Library, at
http://go.microsoft.com/fwlink/?LinkId=103446 and Network Access Protection at
http://go.microsoft.com/fwlink/?LinkId=84637
• Network Policy Server (NPS) in the Windows Server 2008 Technical Library, at
http://go.microsoft.com/fwlink/?LinkId=104545 and Network Policy Server at
http://go.microsoft.com/fwlink/?LinkId=93758
• TCP/IP in the Windows Server 2008 Technical Library, at http://go.microsoft.com/fwlink/?
LinkId=103329
• Windows Internet Name Service (WINS) in the Windows Server 2008 Technical Library,
at http://go.microsoft.com/fwlink/?LinkId=103331
Appendix A
You can use this Network Planning Preparation Sheet to gather the information required to install
a foundation network. This topic provides tables that contain the individual configuration items for
each server computer for which you must supply information or specific values during the
installation or configuration process. Example values are provided for each configuration item.
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.
42
• Change the Administrator Password
IP address 192.168.0.1
43
Configuration items: Example values: Values:
Administrator password
44
• Change the Administrator Password
IP address 192.168.0.2
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 three tables list pre-installation configuration items as described in Configuring All
Servers:
• Change the Administrator Password
45
Configuration items: Example values: Values:
IP address 192.168.0.3
46
Configuration items: Example values: Values:
mode
Length 8
Lease duration • 8
Days • 0
Hours • 0
Minutes
47
Configuration items: Example values: Values:
IP address 192.168.0.4
48
Configuration items for the Windows Server Foundation Network deployment procedure Install
Network Policy Server (NPS):
• No additional configuration items are required to install NPS.
49