Instructions for tying the Thermotech heating pad

Core Network Companion Guide

  • 2 minutes to read

Applies to: Windows Server (Semi-Annual Channel), Windows Server 2016

Refer to the Windows Server 2016 Core Networking Guide for instructions on how to deploy a new Active Directory ® forest with a new root domain and the supporting network infrastructure. However, companion manuals give you the ability to add features to your network.

Each guide can help you achieve a specific goal after you deploy the main network. In some cases, there are several companion manuals that can be used to achieve very complex goals in a considered, inexpensive, and meaningful manner, provided that you use the manuals together and in the correct order.

If you deployed the Active Directory domain and main network without the Main Network Guide, you can still use the companion guides to add features to the network. Simply use the Primary Network Guide as a list of requirements, and remember that in order to add additional features with the companion guides, the network must meet the requirements listed in the Primary Network Guide.

Companion Guide to the Main Network: Deploying Server Certificates for Wireless and Wireless 802.1x Deployments

This companion guide explains how to create the central network by providing server certificates to computers running Network Policy Server (NPS), Remote Access Service (RAS), or both.

Server certificates are required if you provide certificate-based authentication methods with the Extensible Authentication Protocol (EAP) and the protected EAP (PEAP) for network access authentication. Providing server certificates with Active Directory Certificate Services (AD CS) for EAP and PEAP certificate-based authentication methods offers the following advantages:

  • Binding the identity of the NPS or RAS server to a private key
  • A cost-effective and secure way to automatically enroll certificates for NPS and RAS servers in domain members
  • An efficient way to manage certificates and certification authorities
  • Security through certificate-based authentication
  • Ability to extend the use of certificates for other purposes

For instructions on deploying server certificates, see Deploying Server Certificates for 802.1x Wireless and Wireless Deployments.

Companion Guide to Main Network: Providing Password-Based 802.1X Authenticated Wireless Access

This companion guide explains how to build on the core network by providing instructions on how to provide "Institute of Electrical and Electronics Engineers () 802.1x - Authenticated IEEE 802.11 Wireless Access Using Protected Extensible Authentication Protocol \ - Microsoft Challenge Handshake Authentication Protocol Version 2 (PAP - MS - CHAP v2) ".

The authentication method "Peer- - MS- - CHAP v2" requires that when authenticating servers running Network Policy Server (-NPS), wireless clients with a server certificate are present in order to establish the NPS identity for the client to prove. however, user authentication does not take place via a certificate

Since - PEAP MS - CHAP v2 requires that users provide password based credentials instead of a certificate during authentication, it is usually easier and cheaper to provide than EAP - TLS or PEAP TLS -.

Before using this guide to deploy wireless access using the PAP MS - CHAP v2 authentication method, you must do the following:

  1. Follow the instructions in the main network guide to deploy your core network infrastructure, or have the technologies provided in this guide already deployed on your network.
  2. Follow the instructions in the companion Guide to the Main Network Deploying Server Certificates for Wired and Wireless 802.1x Deployments, or if you already have the technologies provided in this guide on your network.

For instructions on providing wireless access using Peer - MS - CHAP v2, see Deploying Password-Based 802.1X Authenticated Wireless Access.

Companion Guide to Main Network: Deploying BranchCache Mode for Hosted Caches

This companion guide explains how to deploy BranchCache in hosted cache mode in one or more branch offices.

BranchCache is a technology for optimizing bandwidth on a wide area network (WAN) that is included in some editions of the Windows Server 2016 and Windows 10 operating systems, as well as in earlier versions of Windows and Windows Server.

When BranchCache is deployed in hosted cache mode, the content cache in a branch is hosted on one or more server computers called hosted cache servers. Hosted cache servers can perform workloads in addition to hosting the cache, so you can use the server in the branch office for multiple purposes.

BranchCache mode for hosted caches increases the efficiency of the cache because content is available even if the client that originally requested and cached the data is offline, because the hosted cache server is always available, more content can be cached, and this is so results in greater WAN bandwidth savings and improved BranchCache efficiency.

When you deploy hosted cache mode, all clients in a multi-subnet branch office can access a single cache stored on the hosted cache server, even if the clients are on different subnets.

For instructions on deploying BranchCache in hosted cache mode, see Deploying BranchCache in hosted cache mode.