<div>
<div class="content wysiwyg-content">
I have a list of steps to create a AD &amp;&nbsp;Exchange Federated Services running on Server 2012 Enterprise:<br />
<br />
Setup two AD-FS Servers (for company A and company B)<br />
• &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Setup AD FS federated trust between company A and company B<br />
• &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Choose a Server for Authentication Certificate for SSL Encryption (only 1)<br />
• &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Configuration of resource server(web server or other application server to which resources clients access) for company A and company B<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Create a federation trust with the Microsoft Federation Gateway<br />
• &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Create TXT records for federated delegation<br />
• &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Configure domains for federated delegation<br />
• &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Create an Autodiscover DNS<br />
• &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Create an organizational relationship<br />
Is this the correct order in which to setup AD &amp;&nbsp;Exchange 2010 Federated Services?
</div>
</div>


I have a list of steps to create a AD & Exchange Federated Services running on Server 2012 Enterprise:

Setup two AD-FS Servers (for company A and company B)
•	Setup AD FS federated trust between company A and company B
•	Choose a Server for Authentication Certificate for SSL Encryption (only 1)
•	Configuration of resource server(web server or other application server to which resources clients access) for company A and company B
	Create a federation trust with the Microsoft Federation Gateway
•	Create TXT records for federated delegation
•	Configure domains for federated delegation
•	Create an Autodiscover DNS
•	Create an organizational relationship
Is this the correct order in which to setup AD & Exchange 2010 Federated Services?

Setting up AD &amp; Exchange 2010 Federated Services

Networking is the process of connecting computing devices, peripherals and terminals together through a system that uses wiring, cabling or radio waves that enable their users to communicate, share information and interact over distances. Often associated are issues regarding operating systems, hardware and equipment, cloud and virtual networking, protocols, architecture, storage and management.

Networking

Office Productivity refers both to the act of being productive and efficient in an office or professional environment, as well as the software applications used to "produce" information. This includes the development of professional skills, creating work processes, and almost any program used to create or modify a document, image, audio or video clip. However, business application suites such as Microsoft Office, which include word processing, spreadsheet and presentation programs, are typically called productivity software, as contrasted with a "utility program," such as a file manager, which is used to organize files and folders on the computer. Many office- and business-oriented groups of programs are organized into suites.

Office Productivity

Productivity software is application software dedicated to producing information, such as documents, presentations, worksheets, databases, charts, graphs, digital paintings, electronic music and digital video. Most common programs and suites such as Microsoft Office and LibreOffice have their own topics. Office suites, which brought word processing, spreadsheet, and relational database programs to the desktop in the 1980s, are the core example of productivity software, but they can include communications software, personal information managers, groupware and log analysis software.

Setting up AD &amp; Exchange 2010 Federated Services

Setting up AD & Exchange 2010 Federated Services