Export (0) Print
Expand All

Foundation Network Guides for Windows Server 2008

Updated: August 26, 2009

Applies To: Windows Server 2008

The Windows Server® 2008 Foundation Network Guide provides instructions for planning and deploying the components required for a fully functioning network and a new Active Directory® domain in a new forest.

Companion guides are also available to help you add new network functionality and features to the network you deployed with the Foundation Network Guide.

The following guides are featured on this page:

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

  • TCP/IP connections on individual servers

This companion guide to the Foundation Network Guide provides instructions about how to deploy 802.1X authenticated wired access by using Protected Extensible Authentication Protocol-Microsoft Challenge Handshake Authentication Protocol version 2 (PEAP-MS-CHAP v2).

To successfully deploy the technologies in this guide, you must first deploy the technologies in the following guides.

  1. Windows Server 2008 Foundation Network Guide

  2. Foundation Network Companion Guide: Deploying Server Certificates

This companion guide to the Foundation Network Guide provides instructions about how to deploy 802.1X authenticated wireless access by using Protected Extensible Authentication Protocol-Microsoft Challenge Handshake Authentication Protocol version 2 (PEAP-MS-CHAP v2).

To successfully deploy the technologies in this guide, you must first deploy the technologies in the following guides.

  1. Windows Server 2008 Foundation Network Guide

  2. Foundation Network Companion Guide: Deploying Server Certificates

This companion guide to the Foundation Network Guide provides instructions for deploying client computer and user certificates with AD CS. When you deploy EAP-TLS or PEAP-TLS, certificates are required for the authentication of servers, clients, and users during network connection attempts through network access servers, such as 802.1X authenticating switches and wireless access points, virtual private network (VPN) servers, and computers running Windows Server® 2008 and Terminal Services Gateway (TS Gateway).

To successfully deploy the technologies in this guide, you must first deploy the technologies in the Windows Server 2008 Foundation Network Guide and the Foundation Network Companion Guide: Deploying Server Certificates.

This companion guide to the Foundation Network Guide provides instructions on how to deploy Group Policy objects (GPOs) to domain joined computers independent from the organizational unit hierarchy of the domain. Membership in a single membership group causes the correct GPO to be applied to the computer, with filters ensuring that a GPO for one version of Windows is not accidentally applied to a different version.

To successfully deploy the technologies in this guide, you must first deploy the technologies in the Windows Server 2008 Foundation Network Guide.

This companion guide to the Foundation Network Guide provides instructions for deploying server certificates with Active Directory Certificate Services (AD CS) and autoenrolling server certificates to computers running Network Policy Server (NPS) and the Routing and Remote Access service.

You can use server certificates to allow client computers to authenticate servers running NPS and Routing and Remote Access when you deploy the following authentication methods for network access authentication:

  • Extensible Authentication Protocol with Transport Layer Security (EAP-TLS). This authentication method also requires the deployment of user and client computer certificates.

  • Protected EAP with TLS (PEAP-TLS). This authentication method also requires the deployment of user and client computer certificates.

  • PEAP with Microsoft Challenge Handshake Authentication Protocol version 2 (PEAP-MS-CHAP v2). This authentication method does not require the deployment of user and client computer certificates.

To successfully deploy the technologies in this guide, you must first deploy the technologies in the Windows Server 2008 Foundation Network Guide.

For EAP-TLS or PEAP-TLS, you can deploy user and client computer certificates with the Foundation Network Companion Guide: Deploying User and Client Computer Certificates.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft