Export (0) Print
Expand All

Checklist: Setting Up a Federation Server Proxy

Updated: June 9, 2011

Applies To: Active Directory Federation Services (AD FS) 2.0

This checklist includes the deployment tasks for preparing a server running Windows Server 2008 for the federation server proxy role in Active Directory Federation Services (AD FS) 2.0.

Complete the tasks in this checklist in order. When a reference link takes you to a procedure, return to this topic after you complete the steps in that procedure so that you can proceed with the remaining tasks in this checklist.

Checklist Checklist: Setting Up a federation server proxy


  Task Reference

Before you begin deploying your AD FS 2.0 federation server proxies, review the AD FS 2.0 deployment topology types and their associated server placement and network layout recommendations.

Conceptual topic Determine Your AD FS 2.0 Deployment Topology

Conceptual topic Planning Federation Server Proxy Placement

Conceptual topic Where to Place a Federation Server Proxy


Review AD FS 2.0 capacity planning guidance to determine the proper number of federation server proxies you should use in your production environment.

Conceptual topic Planning for Federation Server Proxy Capacity


Determine whether a single federation server proxy or a federation server proxy farm is better for your deployment.

Federation servers also perform federation server proxy responsibilities.

Conceptual topic When to Create a Federation Server Proxy

Conceptual topic When to Create a Federation Server Proxy Farm


Determine whether this new federation server proxy will be created in the perimeter network of the account partner organization or the resource partner organization.

Conceptual topic Review the Role of the Federation Server Proxy in the Account Partner

Conceptual topic Review the Role of the Federation Server Proxy in the Resource Partner


Before you install AD FS 2.0 on a computer that will become a federation server proxy, read about the importance of obtaining a server authentication certificate—for federation server proxy farms—adding or sharing certificates across all the servers in a farm.

Conceptual topic Certificate Requirements for Federation Server Proxies


Review information in the AD FS 2.0 Design Guide about how to update Domain Name System (DNS) in the perimeter network so that successful name resolution for federation servers and federation server proxies can occur.

Conceptual topic Name Resolution Requirements for Federation Server Proxies


Determine whether the federation server proxy must be joined to a domain. Although federation server proxies do not have to be joined to a domain, they are easier to manage with remote administration and Group Policy features when they are joined to a domain.

Procedure topic Join a Computer to a Domain


Depending on how the DNS infrastructure in your perimeter network is configured, complete one of the procedures in the topics on the right before you deploy a federation server proxy in your organization.

Do not perform both procedures. Read Name Resolution Requirements for Federation Server Proxies to determine which procedure best suits the requirements of your organization.

Procedure topic Configure Name Resolution for a Federation Server Proxy in a DNS Zone That Serves Only the Perimeter Network

Procedure topic Configure Name Resolution for a Federation Server Proxy in a DNS Zone That Serves Both the Perimeter Network and Internet Clients


After you obtain a server authentication certificate, you must install it in Internet Information Services (IIS) on the default Web site of the federation server proxy.

Procedure topic Import a Server Authentication Certificate to the Default Web Site


(Optional) As an alternative to obtaining a server authentication certificate from a certification authority (CA), you can use IIS 7.0 to acquire a sample certificate for your federation server proxy.

Because IIS 7.0 generates a self-signed certificate that does not originate from a trusted source, use it to create a self-signed certificate only in the following scenarios:

  • When you have to create a Secure Sockets Layer (SSL) channel between your server and a limited, known group of users

  • When you have to troubleshoot third-party certificate problems

It is not a security best practice to deploy a federation server proxy in a production environment using a self-signed, server authentication certificate.

Procedure topic IIS 7.0: Create a Self-Signed Server Certificate in IIS 7.0(


Install the AD FS 2.0 software.

Procedure topic Install the AD FS 2.0 Software


Configure the AD FS 2.0 software on the computer to act in the federation server proxy role by using the AD FS 2.0Federation Server Proxy Configuration Wizard.

Procedure topic Configure a Computer for the Federation Server Proxy Role


Using Event Viewer, verify that the federation server proxy service has started.

Procedure topic Verify That a Federation Server Proxy Is Operational

Community Additions

© 2016 Microsoft