Dark Mode

3 captures
01 Dec 2016 - 20 Mar 2017
Nov DEC Jan
01
2015 2016 2017
success
fail
About this capture
COLLECTED BY
Organization: Internet Archive
The Internet Archive discovers and captures web pages through many different web crawls. At any given time several distinct crawls are running, some for months, and some every day or longer. View the web archive through the Wayback Machine.
TIMESTAMPS
The Wayback Machine - https://web.archive.org/web/20161201134937/https://technet.microsoft.com/en-us/windows-server-docs/identity/ad-fs/design/prepare-client-computers-in-the-account-partner
Table of contents

Shared to

Table of contents +
TOC
Collapse the table of content
Expand the table of content

Prepare Client Computers in the Account Partner

Bill Mathers|Last Updated: 9/30/2016

Applies To: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012

The easiest way for an administrator in an account partner organization to prepare client computers for access to Active Directory Federation Services (AD FS) federated applications is to use Group Policy. Group Policy provides a convenient way for you to push specific certificates and settings that are required for federation to all the client computers that will be used to access federated applications.

So that your client computers can seamlessly access federated applications without certificate prompts or trusted site-related prompts, we recommend that you first prepare each client computer before you deploy AD FS broadly in your organization. Consider using Group Policy to automatically:

See Also

AD FS Design Guide in Windows Server 2012

  • IN THIS ARTICLE
  • See Also
(c) 2016 Microsoft