Wednesday, 2 November 2011

Using Identity Federation with Active Directory Rights Management Services Step-by-Step Guide





Using Identity Federation with Active Directory Rights Management Services Step-by-Step Guide

Microsoft Corporation
Published: March 2008
Author: Brian Lich
Editor: Carolyn Eller
Abstract
This step-by-step guide provides instructions for setting up a test environment to deploy and evaluate Active Directory Rights Management Services (AD RMS) with federated identity support in Windows Server® 2008. It includes the necessary information for installing and configuring AD RMS and AD FS and verifying AD RMS features after configuration is complete.


This document is provided for informational purposes only and Microsoft makes no warranties, either express or implied, in this document. Information in this document, including URL and other Internet Web site references, is subject to change without notice. The entire risk of the use or the results from the use of this document remains with the user. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

© 2008 Microsoft Corporation. All rights reserved.

Microsoft, Active Directory, MS-DOS, Windows, Windows NT, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

All other trademarks are property of their respective owners.




Contents

Using Identity Federation with Active Directory Rights Management Services Step-by-Step Guide 5
About This Guide 5
What This Guide Does Not Provide 5
Deploying AD RMS with Identity Federation Support in a Test Environment 6
Step 1: Setting up the CP&L Enterprises Domain 8
Configure the AD FS resource partner (ADFS-RESOURCE) 9
Configure the Windows Server 2003 R2–based AD FS resource partner 9
Configure the Windows Server 2008–based AD FS resource partner 11
Create the ADFSADMIN user account 12
Add the ADFSADMIN user account to the local Administrators group on ADFS-RESOURCE 12
Configure a DNS forwarder on CPANDL-DC 13
Step 2: Setting up the Trey Research Domain 14
Configure the domain controller (TREY-DC) 15
Configure the Windows Server 2003–based domain controller 15
Configure the Windows Server 2008–based domain controller 17
Create user accounts 19
Configure the federation account partner (ADFS-ACCOUNT) 20
Configure the Windows Sever 2003–based AD FS account partner 20
Configure the Windows Server 2008–based AD FS account partner 22
Configure the AD RMS-enabled client computer (ADRMS-CLNT2) 24
Step 3: Installing and Configuring AD FS 26
Install the Federation Service on ADFS-RESOURCE and ADFS-ACCOUNT 26
Install Federation Service on a Windows Server 2003 R2 Enterprise Edition–based server 26
Install Federation Service role service on a Windows Server 2008 Enterprise–based server 27
Configure ADFS-ACCOUNT to work with AD RMS 28
Configure ADFS-RESOURCE to Work with AD RMS 30
Step 4: Configuring ADRMS-SRV to Work with AD FS 34
Grant security audit privileges to the AD RMS service account 34
Add the AD RMS extranet cluster URLs 34
Add the AD RMS Identity Federation Support role service 35
Enable Identity Federation Support in the Active Directory Rights Management Services console 35
Step 5: Verifying AD RMS Functionality 36

Using Identity Federation with Active Directory Rights Management Services Step-by-Step Guide


About This Guide

This step-by-step guide will assist you in using Active Directory Rights Management Services (AD RMS) with Active Directory® Federation Services (AD FS) in a test environment. Specifically, this guide will look at how to implement AD RMS if you have also deployed AD FS in your organization and have established a trust relationship with another organization that has not deployed AD RMS. Using the information in this guide, you can extend the basic AD RMS deployment to use AD FS credentials to establish trusted user accounts. This will enable you to share access to rights-protected content with another organization without having to establish a separate trust.
In this guide, you will create a test deployment that includes the following components:
An AD FS resource partner server
An AD FS account partner server
An AD RMS server
An AD RMS database server
Two AD RMS clients
Two Active Directory domain controllers
This guide assumes that you previously completed Windows Server Active Directory Rights Management Services Step-by-Step Guide, and that you have already deployed the following components:
An AD RMS server
An AD RMS database server
One AD RMS-enabled client
One Active Directory domain controller

What This Guide Does Not Provide

This guide does not provide the following:
An overview of AD RMS. For more information about the advantages that AD RMS can bring to your organization, see http://go.microsoft.com/fwlink/?LinkId=84726.
Guidance for setting up and configuring AD RMS in a production environment.
Complete technical reference for AD RMS or AD FS.
Guidance for setting up AD FS with Microsoft Office SharePoint Server 2007 and AD RMS. For more information about using identity federation with Office SharePoint Server 2007 and AD RMS, see Appendix A of the Deploying Active Directory Rights Management Services with Microsoft Office SharePoint Server 2007 Step-By-Step Guide (http://go.microsoft.com/fwlink/?LinkId=93136).

Deploying AD RMS with Identity Federation Support in a Test Environment

We recommend that you first use the steps provided in this guide in a test lab environment. Step-by-step guides are not necessarily meant to be used to deploy Windows Server features without additional deployment documentation and should be used with discretion as a stand-alone document.
Upon completion of this guide, you will have a working AD RMS and AD FS infrastructure. You can then test and verify AD RMS and AD FS functionality as follows:
Restrict permissions on a Microsoft Word 2007 document in the CPANDL.COM domain.
Have an authorized user in the TREYRESEARCH.NET domain open and work with the document.
Have an unauthorized user in the CPANDL.COM domain attempt to open and work with the document.
The test environment described in this guide includes eight computers connected to a private network and using the following operating systems, applications, and services:

Computer NameOperating SystemApplications and Services
ADRMS-SRVWindows Server® 2008AD RMS, Internet Information Services (IIS) 7.0, World Wide Web Publishing Service, and Message Queuing
CPANDL-DC
TREY-DC
Windows Server 2003 with Service Pack 2 (SP2)Note
Domain controllers running Windows 2000 Server with Service Pack 4 can be used. However, in this step-by-step guide it is assumed that you will be using domain controllers running Windows Server 2003 with SP2.
Active Directory, Domain Name System (DNS)
ADRMS-DBWindows Server 2003 with SP2Microsoft SQL Server® 2005 Standard Edition with Service Pack 2 (SP2)
ADRMS-CLNT
ADRMS-CLNT2
Windows Vista®Microsoft Office Word 2007 Enterprise Edition
ADFS-RESOURCE
ADFS-ACCOUNT
Windows Server® 2008 Enterprise or Windows Sever 2003 R2 Enterprise EditionAD FS, IIS

Note
Before installing and configuring the components in this guide, you should verify that your hardware meets the minimum requirements for AD RMS (http://go.microsoft.com/fwlink/?LinkId=84733).
The computers form two private intranets and are connected through a common hub or Layer 2 switch. This configuration can be emulated in a virtual server environment, if desired. This step-by-step exercise uses private addresses throughout the test lab configuration. The private network ID 10.0.0.0/24 is used for the intranet. The domain controller for the domain named cpandl.com is CPANDL-DC and the domain controller for the domain name treyresearch.net is TREY-DC. The following figure shows the configuration of the test environment:

Step 1: Setting up the CP&L Enterprises Domain


Before you install AD FS and the AD RMS Identity Federation Support role service, you need to make changes to the infrastructure of the CPANDL domain. In this step, you will perform the following tasks to install the required Active Directory Federation Services resource partner and add it to the CP&L Enterprises infrastructure.
This section includes the following procedures:
Install AD FS resource partner (ADFS-RESOURCE)
Create the ADFSADMIN user account
Add the ADFSADMIN user account to the local Administrators group on ADFS-RESOURCE
Configure a DNS forwarder
This step assumes that you have completed the Windows Server Active Directory Rights Management Services Step-by-Step Guide (http://go.microsoft.com/fwlink/?LinkId=72134).
Use the following table as a reference when setting up the appropriate computer names, operating systems, and network settings that are required to complete the steps in this guide.Important
Before you configure your computers with static Internet Protocol (IP) addresses, we recommend that you first complete Windows product activation while each of your computers still has Internet connectivity. You should also install any available critical security updates from Windows Update (http://go.microsoft.com/fwlink/?LinkID=47290).

Computer nameOperating system requirementIP settingsDNS settings
ADFS-RESOURCEWindows Server 2003 R2 Enterprise Edition with Service Pack 2 (SP2) or Windows Server® 2008 EnterpriseIP address:
10.0.0.7
Subnet mask:
255.255.255.0
Preferred:
10.0.0.1


Configure the AD FS resource partner (ADFS-RESOURCE)

AD RMS can use federation servers that are running either Windows Server 2003 R2 or Windows Server 2008 Enterprise. Use one of the following sections to configure Windows Server depending on the requirements in your organization:
Configure the Windows Sever 2003 R2–based AD FS resource partner
Configure the Windows Server 2008–based AD FS resource partner

Configure the Windows Server 2003 R2–based AD FS resource partner

In this section you will install Windows Server 2003 R2 Enterprise Edition, configure TCP/IP properties, add ADFS-RESOURCE to the CP&L domain, and then add the Application server role.
First, install Windows Server 2003 R2 Enterprise Edition as a stand-alone server on ADFS-RESOURCE.Important
Windows Server 2003 R2 Enterprise Edition is required for the federation servers.To install Windows Server 2003 R2 Enterprise Edition
1. Start your computer by using the Windows Server 2003 R2 Enterprise Edition product CD.
2. Follow the instructions that appear on your computer screen, and when prompted for a computer name, type ADFS-RESOURCE.

In this step configure TCP/IP properties so that ADFS-RESOURCE has a static IP address of 10.0.0.7.To configure TCP/IP properties on ADFS-RESOURCE
1. Log on to ADFS-RESOURCE as a member of the local Administrators group.
2. Click Start, point to Control Panel, and then double-click Network Connections.
3. Right-click Local Area Connection, and then click Properties.
4. On the General tab, click Internet Protocol (TCP/IP), and then click Properties.
5. Click the Use the following IP address option. In the IP address box, type 10.0.0.7. In the Subnet mask box, type 255.255.255.0.
6. Click the Use the following DNS server addresses option. In the Preferred DNS server box, type 10.0.0.1.
7. Click OK, and then click Close to close the Local Area Connection Properties dialog box.

Next, join the federation resource partner (ADFS-RESOURCE) computer to the CP&L domain:To join ADFS-RESOURCE to CPANDL domain
1. Log on to ADFS-RESOURCE as a member of the local administrators group.
2. Click Start, right-click My Computer, and then click Properties.
3. Click Computer Name tab, and then click Change.
4. In the Computer Name Changes dialog box, click Domain, and then type cpandl.com.
5. Click More, and then type cpandl.com in the Primary DNS suffix of this computer box.
6. Click OK twice.
7. When a Computer Name Changes dialog box appears prompting you for administrative credentials, provide the credentials, and click OK.
8. When a Computer Name Changes dialog box appears welcoming you to the cpandl.com domain, click OK.
9. When a Computer Name Changes dialog box appears telling you that the computer must be restarted, click OK, and then click Close.

Finally, add the application server role on the ADFS-RESOURCE computer.To add the application server role
1. Log on to ADFS-RESOURCE as CPANDL\Administrator. The Manage Your Server window appears.
2. Click Add or remove a role.
3. On the Preliminary Steps page of the Configure your Server Wizard, click Next.
4. Click Application Server (IIS, ASP.NET), and then click Next.
5. Select the Enable ASP.NET check box, and then click Next twice.
6. When asked for files from the Windows Server 2003 product CD, insert it into the CD-ROM drive of the computer.
7. Click Finish to complete the installation.

Configure the Windows Server 2008–based AD FS resource partner

First, install Windows Server 2008 Enterprise as a stand-alone server on ADFS-RESOURCE.Important
Windows Server 2008 Enterprise is required for the federation servers.To install Windows Server 2008 Enterprise
1. Start your computer by using the Windows Server 2008 product CD.
2. When prompted for a computer name, type ADFS-RESOURCE.
3. Follow the rest of the instructions that appear on your screen to finish the installation.

In this step, configure TCP/IP properties so that the ADFS-RESOURCE computer has a static IP address of 10.0.0.7.To configure TCP/IP properties on the ADFS-RESOURCE computer
1. Log on to ADFS-RESOURCE with the ADFS-RESOURCE\Administrator account or another user account in the local Administrators group.
2. Click Start, click Control Panel, click Network and Internet, double-click Network and Sharing Center, click Manage Network Connections, right-click Local Area Connection, and then click Properties.
3. On the Networking tab, click Internet Protocol Version 4 (TCP/IPv4), and then click Properties.
4. Select the Use the following IP address option. In IP address, type 10.0.0.7, in Subnet mask, type 255.255.255.0.
5. Select the Use the following DNS server addresses option. In Preferred DNS server, type 10.0.0.1.
6. Click OK, and then click Close to close the Local Area Connection Properties dialog box.

Next, join the ADFS-RESOURCE computer to the CPANDL domain:To join ADFS-RESOURCE to the cpandl.com domain
1. Click Start, right-click Computer, and then click Properties.
2. Click Change settings (at the right side under Computer name, domain, and workgroup settings), and then click Change.
3. In the Computer Name/Domain Changes dialog box, select the Domain option, and then type cpandl.com.
4. Click More, and type cpandl.com in Primary DNS suffix of this computer box.
5. Click OK, and then click OK again.
6. When a Computer Name/Domain Changes dialog box appears prompting you for administrative credentials, provide the credentials of CPANDL\Administrator, and then click OK.
7. When a Computer Name/Domain Changes dialog box appears welcoming you to the cpandl.com domain, click OK.
8. When a Computer Name/Domain Changes dialog box appears telling you that the computer must be restarted, click OK, and then click Close.
9. Click Restart Now.

Create the ADFSADMIN user account

In this step, create the ADFSADMIN user account in Active Directory.To add ADFSADMIN to the CPANDL domain
1. Log on to CPANDL-DC with the CPANDL\Administrator account.
2. Click Start, point to Administrative Tools, and then click Active Directory Users and Computers.
3. In the console tree, expand cpandl.com, right-click Users, point to New, and then click User.
4. In the New Object – User dialog box, type ADFSADMIN in Full name and User logon name boxes, and then click Next.
5. In the New Object – User dialog box, type a password of your choice in the Password and Confirm password boxes. Clear the User must change password at next logon check box, click Next, and then click Finish.

Add the ADFSADMIN user account to the local Administrators group on ADFS-RESOURCE

Installing AD FS requires that the logged-on user have administrative privileges on the local server.
If you are running Windows Server 2003 R2 Enterprise Edition on ADFS-RESOURCE, use the following procedure:To add ADFSADMIN to the Administrators group on a Windows Server 2003–based server
1. Log on to ADFS-RESOURCE as cpandl\administrator.
2. Click Start, point to Administrative Tools, and then click Computer Management.
3. Expand System Tools, expand Local Users and Groups, and then click Groups.
4. Right-click Administrators, and then click Add to Group.
5. Click Add.
6. In the Select Users, Computers, or Groups window, type cpandl\adfsadmin, and then click OK.
7. Click OK to close the Administrators properties sheet.

If you are running Windows Server 2008 Enterprise on ADFS-RESOURCE, use the following procedure:To add ADFSADMIN to the Administrators group on a Windows Server 2008–based server
1. Log on to ADFS-RESOURCE as cpandl\administrator.
2. Click Start, point to Administrative Tools, and then click Server Manager.
3. Expand Configuration, expand Local Users and Groups, and then click Groups.
4. Right-click Administrators, and then click Add to Group.
5. Click Add.
6. In the Select Users, Computers, or Groups window, type cpandl\adfsadmin, and then click OK.
7. Click OK to close the Administrators properties sheet.

Configure a DNS forwarder on CPANDL-DC

DNS forwarders are used in this guide to forward DNS requests that cannot be resolved from the cpandl.com domain to the treyresearch.net domain, and vice versa.
To configure the DNS forwarder when the computer is running Windows Server 2003:To configure a DNS forwarder on a Windows Server 2003–based computer
1. Log on to CPANDL-DC with the CPANDL\Administrator account or another user account in the local Administrators group.
2. Click Start, point to Administrative Tools, and then click DNS.
3. Right-click CPANDL-DC, and then click Properties.
4. Click the Forwarders tab.
5. In the Selected domain's forward IP address list section, type 10.0.0.30, and then click Add.
6. Click OK.

To configure the DNS forwarder when the computer is running Windows Server 2008:To configure a DNS forwarder on a Windows Server 2008–based computer
1. Log on to CPANDL-DC with the CPANDL\Administrator account or another user account in the local Administrators group.
2. Click Start, point to Administrative Tools, and then click DNS.
3. Right-click CPANDL-DC, and then click Properties.
4. Click the Forwarders tab.
5. Click Edit.
6. Type 10.0.0.30, and then click OK.
7. Click OK to close the properties sheet.


Step 2: Setting up the Trey Research Domain


Before you install AD FS and the AD RMS Federation Identity Support role service, you should install and configure the Trey Research infrastructure. In this step, you will install the required computers that make up the Trey Research domain:
Configure the domain controller (TREY-DC)
Create user accounts
Configure the federation account partner (ADFS-ACCOUNT)
Configure the AD RMS-enabled client computer (ADRMS-CLNT2)
Use the following table as reference when setting up the appropriate computer names, operating systems, and network settings that are required to complete the steps in this guide.Important
Before you configure your computers with static Internet Protocol (IP) addresses, we recommend that you first complete Windows product activation while each of your computers still has Internet connectivity.

Computer nameOperating system requirementIP settingsDNS settings
TREY-DCWindows Server 2003 with Service Pack 2 (SP2) or Windows Server® 2008IP address:
10.0.0.30
Subnet mask:
255.255.255.0
Configured by DNS server role.
ADFS-ACCOUNTWindows Server 2008 Enterprise or Windows Server 2003 R2 Enterprise Edition with Service Pack 2 (SP2)IP address:
10.0.0.31
Subnet mask:
255.255.255.0
Preferred:
10.0.0.30
ADRMS-CLNT2Windows VistaIP address
10.0.0.32
Subnet mask:
255.255.255.0
Preferred:
10.0.0.30


Configure the domain controller (TREY-DC)

Depending on your environment, you can evaluate AD RMS in either a Windows Server 2008 domain or a Windows Server 2003 domain. Use one of the following sections depending on the domain to be used.
Configure the Windows Server 2003–based domain controller
Configure the Windows Server 2008–based domain controller

Configure the Windows Server 2003–based domain controller

To configure the domain controller TREY-DC, you must install Windows Server 2003, configure TCP/IP properties, install Active Directory, and raise the Active Directory domain functional level to Windows Server 2003.
First, install Windows Server 2003 with SP2 on the TREY-DC computer.To install Windows Server 2003 Standard Edition
1. Start your computer by using the Windows Server 2003 product CD. (You can use any edition of Windows Server 2003 except the Web Edition to establish the domain)
2. Follow the instructions that appear on your computer screen, and when prompted for a computer name, type TREY-DC.

In this step configure TCP/IP properties so that TREY-DC has a static IP address of 10.0.0.30.To configure TCP/IP properties on TREY-DC
1. Log on to TREY-DC with the TREY-DC\Administrator account or another user account in the local Administrators group.
2. Click Start, point to Control Panel, point to Network Connections, click Local Area Connection, and then click Properties.
3. On the General tab, click Internet Protocol (TCP/IP), and then click Properties.
4. Click the Use the following IP address option. In the IP address box, type 10.0.0.30. In the Subnet mask box, type 255.255.255.0.
5. Click OK, and then click Close to close the Local Area Connection Properties dialog box.

Install Active Directory
In this step, you are going to create a domain controller for Trey Research. It is important that you first configure the IP addresses as specified in the previous table before you attempt to install Active Directory. This helps ensure that DNS records are configured appropriately.Note
If you need to use fewer computers to test this scenario, you can use the Dcpromo tool to create two new Active Directory forests on both of the federation servers rather than configuring separate domain controllers. As a security best practice, domain controllers should not run as both federation servers and domain controllers in a production environment.To configure TREY-DC as a domain controller
1. Click Start, and click Run. In the Open box, type dcpromo, and then click OK.
2. On the Welcome page of the Active Directory Installation Wizard, click Next.
3. Click Next, select the Domain controller for a new domain option, and then click Next.
4. Select the Domain in a new forest option, and click Next.
5. In Full DNS name for new domain, type treyresearch.net and then click Next.
6. In Domain NetBIOS name, type treyresearch, and then click Next three times.
7. Select the Install and configure the DNS server on this computer and set this computer to use this DNS server as its preferred DNS server option, and then click Next.
8. Select the Permissions compatible only with Windows 2000 or Windows Server 2003 operating systems option, and then click Next.
9. In the Restore Mode Password and Confirm Password boxes, type a strong password, and then click Next.
10. Click Next.
11. When the Active Directory Installation Wizard is done, click Finish.
12. Click Restart Now.

Raise the domain functional level to Windows Server 2003
In this step, we will raise the Active Directory domain functional level to Windows Server 2003. This functional level allows the use of Active Directory universal groups.To raise the domain functional level to Windows Server 2003
1. Log on to TREY-DC with the TREYRESEARCH\Administrator account or another user account in the local Administrators group.
2. Click Start, point to Administrative Tools, and then click Active Directory Users and Computers.
3. Right-click treyresearch.net, and then click Raise Domain Functional Level.
4. In the list under Select an available domain functional level, click Windows Server 2003, and then click Raise.Note
You cannot change the domain functional level once you have raised it.
5. Click OK, and then click OK again.

Configure a DNS forwarder
DNS forwarders are used in this guide to forward DNS requests that cannot be resolved from the treyresearch.net domain to the cpandl.com domain, and vice versa.To configure a DNS forwarder on a Windows Server 2003–based computer
1. Log on to TREY-DC with the TREYRESEARCH\Administrator account or another user account in the local Administrators group.
2. Click Start, point to Administrative Tools, and then click DNS.
3. Right-click TREY-DC, and then click Properties.
4. Click the Forwarders tab.
5. In the Selected domain's forward IP address list section, type 10.0.0.1, and then click Add.
6. Click OK.

Configure the Windows Server 2008–based domain controller

To configure the domain controller TREY-DC, you must install Windows Server 2008, configure TCP/IP properties, and install Active Directory Domain Services.
First, install Windows Server 2008.To install Windows Server 2008
1. Start your computer by using the Windows Server 2008 product CD.
2. Follow the instructions that appear on your screen, and when prompted for a computer name, type TREY-DC.

Next, configure TCP/IP properties so that TREY-DC has a IPv4 static IP address of 10.0.0.30.To configure TCP/IP properties on TREY-DC
1. Log on to TREY-DC with the TREY-DC\Administrator account or another user account in the local Administrators group.
2. Click Start, click Control Panel, click Network and Internet, click Network and Sharing Center, click Manage Network Connections, right-click Local Area Connection, and then click Properties.
3. On the Networking tab, click Internet Protocol Version 4 (TCP/IPv4), and then click Properties.
4. Click the Use the following IP address option. In IP address, type 10.0.0.30, in Subnet mask, type 255.255.255.0.
5. Click the Use the following DNS server addresses option. In Preferred DNS server, type 10.0.0.30, and then click OK.
6. On the Networking tab, clear the Internet Protocol Version 6 (TCP/IPv6) check box.Note
If you want to leave IPv6 enabled, you must assign a static IPv6 address before configuring the computer as a domain controller.
7. Click OK, and then click Close to close the Local Area Connection Properties dialog box.

Install Active Directory Domain Services
In this step, you are going to create a domain controller for Trey Research. It is important that you first configure the IP addresses as specified in the previous procedure before you attempt to install Active Directory Domain Services (AD DS). This helps ensure that DNS records are configured appropriately.Note
If you need to use fewer computers to test this scenario, you can use the Dcpromo tool to create two new Active Directory forests on both of the federation servers rather than configuring separate domain controllers. As a security best practice, domain controllers should not run as both federation servers and domain controllers in a production environment.To configure TREY-DC as a domain controller
1. Click Start, and then click Run.
2. In the Open box, type dcpromo, and then click OK.
3. On the Welcome to the Active Directory Domain Services Installation Wizard page, click Next.
4. Click the Domain controller for a new domain option, and then click Next.
5. Click the Create a new domain in a new forest option, and then click Next.
6. In the FQDN of the forest root domain box, type treyresearch.net, and then click Next.
7. In the Forest functional level box, click Windows Server 2003, and then click Next.
8. In the Domain functional level box, click Windows Server 2003, and then click Next.
9. Ensure that the DNS server check box is selected, and then click Next.
10. Click Yes, confirming that you want to create a delegation for this DNS server.
11. On the Location for Database, Log Files, and SYSVOL page, click Next.
12. In the Password and Confirm password boxes, type a strong password, and then click Next.
13. On the Summary page, click Next to start the installation.
14. When the installation is complete, click Finish, and then click Restart Now.
*Note
You must restart the computer after you complete this procedure.
Configure a DNS forwarder
DNS forwarders are used in this guide to forward DNS requests that cannot be resolved from the treyresearch.net domain to the cpandl.com domain, and vice versa.To configure a DNS forwarder on a Windows Server 2008–based computer
1. Log on to TREY-DC with the TREYRESEARCH\Administrator account or another user account in the local Administrators group.
2. Click Start, point to Administrative Tools, and then click DNS.
3. Right-click TREY-DC, and then click Properties.
4. Click the Forwarders tab.
5. Click Edit.
6. Type 10.0.0.1, and then click OK.
7. Click OK to close the properties sheet.

Create user accounts

In this section, add the user accounts shown in the following table to Active Directory. Use the procedure following the table to create the user accounts.

Account NameUser Logon NameE-mail address
ADFSADMINADFSADMIN
Terrence Philiptphiliptphilip@treyresearch.net

To add new user accounts to the TREYRESEARCH domain
1. Log on to TREY-DC with the TREYRESEARCH\Administrator account or another user account in the local Administrators group.
2. Click Start, point to Administrative Tools, and then click Active Directory Users and Computers.
3. In the console tree, expand treyresearch.net.
4. Right-click Users, point to New, and then click User.
5. In the New Object – User dialog box, type ADFSADMIN in the Full name and User logon name boxes, and then click Next.
6. In the New Object – User dialog box, type a password of your choice in the Password and Confirm password boxes. Clear the User must change password at next logon check box, click Next, and then click Finish.
7. Perform steps 3-6 for Terrence Philip (tphilip).

Next, add an e-mail address for Terrence Philip.To add e-mail addresses to user accounts
1. In the Active Directory Users and Computers console, right-click Terrence Philip, click Properties, type tphilip@treyresearch.net in the E-mail box, and then click OK.
2. Close the Active Directory Users and Computers console.

Configure the federation account partner (ADFS-ACCOUNT)

AD RMS can use federation servers that are running either Windows Server 2003 R2 Enterprise Edition or Windows Server 2008 Enterprise. Use one of the following sections depending on the requirements in your organization.
Configure the Windows Sever 2003–based AD FS account partner
Configure the Windows Server 2008–based AD FS account partner

Configure the Windows Sever 2003–based AD FS account partner

In this section you will install Windows Server 2003 R2 Enterprise Edition, configure TCP/IP properties, add ADFS-ACCOUNT to the TreyResearch domain, and then add the Application server role.
First, install Windows Server 2003 R2 Enterprise Edition as a stand-alone server on ADFS-ACCOUNT.Important
Windows Server 2003 R2 Enterprise Edition is required for the federation servers.To install Windows Server 2003 R2 Enterprise Edition
1. Start your computer by using the Windows Server 2003 R2 Enterprise Edition product CD.
2. Follow the instructions that appear on your computer screen, and when prompted for a computer name, type ADFS-ACCOUNT.

In this step configure TCP/IP properties so that ADFS-ACCOUNT has a static IP address of 10.0.0.31.To configure TCP/IP properties on ADFS-ACCOUNT
1. Log on to ADFS-ACCOUNT as a member of the local Administrators group.
2. Click Start, point to Control Panel, and then double-click Network Connections.
3. Right-click Local Area Connection, and then click Properties.
4. On the General tab, click Internet Protocol (TCP/IP), and then click Properties.
5. Click the Use the following IP address option. In the IP address box, type 10.0.0.31. In the Subnet mask box, type 255.255.255.0.
6. Click the Use the following DNS server addresses option. In the Preferred DNS server box, type 10.0.0.30.
7. Click OK, and then click OK to close the Local Area Connection Properties dialog box.

Next, join the federation account partner (ADFS-ACCOUNT) computer to the TreyResearch domain:To join ADFS-ACCOUNT to TREYRESEARCH domain
1. Log on to ADFS-ACCOUNT as a member of the local administrators group.
2. Click Start, right-click My Computer, and then click Properties.
3. Click Computer Name tab, and then click Change.
4. In the Computer Name Changes dialog box, click Domain, and then type treyresearch.net.
5. Click More, and then type treyresearch.net in Primary DNS suffix of this computer box.
6. Click OK twice.
7. When a Computer Name Changes dialog box appears prompting you for administrative credentials, provide the credentials, and then click OK.
8. When a Computer Name Changes dialog box appears welcoming you to the cpandl.com domain, click OK.
9. When a Computer Name Changes dialog box appears telling you that the computer must be restarted, click OK, and then click Close.

Next, add the application server role on the ADFS-ACCOUNT computer.To add the application server role
1. Log on to ADFS-ACCOUNT as TREYRESEARCH\Administrator. The Manage Your Server window appears.
2. Click Add or remove a role.
3. On the Preliminary Steps page of the Configure your Server Wizard, click Next.
4. Click Application Server (IIS, ASP.NET), and then click Next.
5. Select the Enable ASP.NET check box, and then click Next twice.
6. When asked for files from the Windows Server 2003 product CD, insert it into the CD drive of the computer.
7. Click Finish to complete the installation.

Finally, add the ADFSADMIN user account to the local Administrators group on ADFS-ACCOUNT.To add ADFSADMIN to the Administrators group
1. Log on to ADFS-RESOURCE as cpandl\administrator.
2. Click Start, click Control Panel, double-click Administrative Tools, and then double-click Computer Management.
3. Expand System Tools, expand Local Users and Groups, and then click Groups.
4. Right-click Administrators, and then click Add to Group.
5. Click Add.
6. In the Select Users, Computers, or Groups window, type cpandl\adfsadmin, and then click OK.
7. Click OK to close the Administrators properties sheet.

Configure the Windows Server 2008–based AD FS account partner

First, install Windows Server 2008 Enterprise as a stand-alone server on ADFS-ACCOUNT.Important
Windows Server 2008 Enterprise is required for the federation servers.To install Windows Server 2008 Enterprise
1. Start your computer by using the Windows Server 2008 product CD.
2. When prompted for the installation type, choose Custom Installation.
3. When prompted for a computer name, type ADFS-ACCOUNT.
4. Follow the rest of the instructions that appear on your screen to finish the installation.

In this step configure TCP/IP properties so that the ADFS-ACCOUNT computer has a static IP address of 10.0.0.31.To configure TCP/IP properties on the ADFS-ACCOUNT computer
1. Log on to ADFS-ACCOUNT with the ADFS-ACCOUNT\Administrator account or another user account in the local Administrators group.
2. Click Start, click Network, click Network and Sharing Center, click Manage Network Connections, right-click Local Area Connection, and then click Properties.
3. On the Networking tab, click Internet Protocol Version 4 (TCP/IPv4), and then click Properties.
4. Select the Use the following IP address option. In IP address, type 10.0.0.31, in Subnet mask, type 255.255.255.0.
5. Select the Use the following DNS server addresses option. In Preferred DNS server, type 10.0.0.30.
6. Click OK, and then click Close to close the Local Area Connection Properties dialog box.

Next, join the ADFS-ACCOUNT computer to the TREYRESEARCH domain:To join ADFS-ACCOUNT to the treyresearch.net domain
1. Click Start, right-click Computer, and then click Properties.
2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
3. Click Change settings (at the right side), and then click Change.
4. In the Computer Name/Domain Changes dialog box, select the Domain option, and then type treyresearch.net.
5. Click More, and type treyresearch.net in Primary DNS suffix of this computer box.
6. Click OK, and then click OK again.
7. When a Computer Name/Domain Changes dialog box appears prompting you for administrative credentials, provide the credentials for TREYRESEARCH\Administrator, and click OK.
8. When a Computer Name/Domain Changes dialog box appears welcoming you to the treyresearch.net domain, click OK.
9. When a Computer Name/Domain Changes dialog box appears telling you that the computer must be restarted, click OK, and then click Close.
10. Click Restart Now.

Finally, add the ADFSADMIN user account to the local Administrators group on ADFS-ACCOUNT.To add ADFSADMIN to the Administrators group
1. Log on to ADFS-ACCOUNT with the TREYRESEARCH\Administrator account or another user account in the local Administrators group.
2. To open Server Manager, click Start, point to Administrative Tools, and then click Server Manager.
3. Expand Configuration, expand Local Users and Groups, and then click Groups.
4. Double-click Administrators, click Add, type TREYRESEARCH\ADFSADMIN, click OK, and then click OK again.

Configure the AD RMS-enabled client computer (ADRMS-CLNT2)

To configure the ADRMS-CLNT2 client computer in the TREYRESEARCH domain, you must install Windows Vista, configure TCP/IP properties, and then join the computer to the TREYRESEARCH domain. You must also install an AD RMS-enabled application and configure this computer for AD RMS federation support. In this example, Microsoft Office Word 2007 Enterprise Edition is installed on the client.To install Windows Vista
1. Start your computer by using the Windows Vista product CD.
2. Follow the instructions that appear on your screen, and when prompted for a computer name, type ADRMS-CLNT2.

Next, configure TCP/IP properties so that ADRMS-CLNT2 has a static IP address of 10.0.0.32. In addition, configure the DNS server of TREY-DC (10.0.0.30).To configure TCP/IP properties
1. Log on to ADRMS-CLNT2 with the ADRMS-CLNT2\Administrator account or another user account in the local Administrators group.
2. Click Start, click Network, and then click Network and Sharing Center.
3. Click Manage Network Connections, right-click Local Area Connection, and then click Properties.
4. On the Networking tab, click Internet Protocol Version 4 (TCP/IPv4), and then click Properties.
5. Select the Use the following IP address option. In IP address, type 10.0.0.32, in Subnet mask, type 255.255.255.0.
6. Select the Use the following DNS server addresses option. In Preferred DNS server, type 10.0.0.30.
7. Click OK, and then click Close to close the Local Area Connection Properties dialog box.

Next, join the ADRMS-CLNT2 to the TREYRESEARCH domain.To join ADRMS-CLNT2 to the TREYRESEARCH domain
1. Click Start, right-click Computer, and then click Properties.
2. Under Computer name, domain, and workgroup settings, click Change settings.
3. On the Computer Name tab, click Change.
4. In the Computer Name/Domain Changes dialog box, select the Domain option, and then type treyresearch.net.
5. Click More, and in the Primary DNS suffix of this computer box, type treyresearch.net.
6. Click OK, and click OK again.
7. When a Computer Name/Domain Changes dialog box appears prompting you for administrative credentials, provide the credentials for treyresearch\administrator, and then click OK.
8. When a Computer Name/Domain Changes dialog box appears welcoming you to the treyresearch.net domain, click OK.
9. When a Computer Name/Domain Changes dialog box appears telling you that the computer must be restarted, click OK, and then click Close.
10. In the System Settings Change dialog box, click Yes to restart the computer.

Next, we need to configure ADRMS-CLNT2 for federation support with AD RMS. This registry entry assigns the AD FS home realm for AD RMS.To configure ADRMS-CLNT2 for federation support
1. Log on to ADRMS-CLNT2 with the TREYRESEARCH\Administrator account or another user account in the local Administrators group.
2. Click Start, type regedit.exe, and then press Enter.
3. Expand HKEY_LOCAL_MACHINE, expand Software, and then expand Microsoft.
4. Right-click Microsoft, point to New, click Key, type MSDRM and then press Enter.
5. Right-click MSDRM, point to New, click Key, type Federation and then press Enter.
6. Right-click Federation, point to New, click String Value, type FederationHomeRealm, and then press ENTER.
7. Double-click FederationHomeRealm, type urn:federation:treyresearch.net, and then click OK.

Finally, install Microsoft Office Word 2007 Enterprise Edition on ADRMS-CLNT2.To install Microsoft Office Word 2007 Enterprise
1. Double-click setup.exe from the Microsoft Office 2007 Enterprise product CD.
2. Click Customize as the installation type, set the installation type to Not Available for all applications except Microsoft Office Word 2007 Enterprise, and then click Install Now. This might take several minutes to complete.
*Important
Only the Ultimate, Professional Plus, and Enterprise editions of Microsoft Office 2007 allow you to create rights-protected content. All editions will allow you to consume rights-protected content.

Step 3: Installing and Configuring AD FS


Now that you have configured the computers that will be used as federation servers, you are ready to install Active Directory Federation Services (AD FS) components on each of the computers. This section includes the following procedures:
Install the Federation Service on ADFS-RESOURCE and ADFS-ACCOUNT
Configure ADFS-ACCOUNT to work with AD RMS
Configure ADFS-RESOURCE to work with AD RMS

Install the Federation Service on ADFS-RESOURCE and ADFS-ACCOUNT

Use one of the following sections to install the Federation Service component of AD FS on the ADFS-RESOURCE computer and the ADFS-ACCOUNT computer depending on the requirements in your organization. After the Federation Service is installed on a computer, that computer becomes a federation server.
Install Federation Service on a Windows Server 2003 R2 Enterprise Edition–based server
Install Federation Service role service on a Windows Server 2008 Enterprise-based server

Install Federation Service on a Windows Server 2003 R2 Enterprise Edition–based server

If you are running Windows Server 2003 R2 Enterprise Edition on ADFS-RESOURCE and ADFS-ACCOUNT, use the following procedure to add the federation service. You must have a Secure Sockets Layer (SSL) certificate installed on the computer before adding the federation service.To install the Federation Service on a Windows Server 2003 R2 Enterprise Edition–based computer
1. Log on to ADFS-RESOURCE with the CPANDL\ADFSADMIN account.
2. Click Start, point to Control Panel, and then click Add or Remove Programs.
3. In Add or Remove Programs, click Add/Remove Windows Components.
4. In the Windows Components Wizard, click Active Directory Services, and then click Details.
5. In the Active Directory Services dialog box, click Active Directory Federation Services (ADFS), and then click Details.
6. In the Active Directory Federation Services (ADFS) dialog box, select the Federation Service check box, and then click OK. If Microsoft ASP.NET 2.0 was not previously enabled, click Yes to enable it, and then click OK.
7. In the Active Directory Services dialog box, click OK.
8. In the Windows Components Wizard, click Next.
9. On the Federation Service page, click the Select token certificate option, and select the certificate that should be used as the token signing certificate.
10. Under Trust policy, click Create a new trust policy, and then click Next.
11. If you are prompted for the location of the installation files, insert the Windows Server 2003 R2 Enterprise Edition product disc, and then click OK.
12. On the Completing the Windows Components Wizard page, click Finish.
13. Log on to ADFS-ACCOUNT as TREYRESEARCH\ADFSADMIN.
14. Repeat steps 2–12 for the ADFS-ACCOUNT computer using the TREYRESEARCH\ADFSADMIN user account.

Install Federation Service role service on a Windows Server 2008 Enterprise–based server

If you are running Windows Server 2008 Enterprise on ADFS-RESOURCE and ADFS-ACCOUNT, use the following procedure to add the Federation Service role service by using Server Manager:To add the Federation Service role service on a Windows Server 2008 Enterprise–based computer
1. Log on to ADFS-RESOURCE with the CPANDL\ADFSADMIN.
2. Click Start, point to Administrative Tools, and then click Server Manager.
3. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
4. Click Add Roles.
5. On the Before You Begin page, click Next.
6. On the Select Server Roles page, click Active Directory Federation Services.
7. Click Next.
8. On the Introduction to AD FS page, click Next.
9. On the Select Role Services page, select the Federation Service check box. If you are prompted to install additional role services, click Add Required Role Services, and then click Next.
10. Select the Choose an existing certificate for SSL encryption option, click the appropriate certificate, and then click Next.
11. On the Choose a Token-Signing Certificate page, select the Choose an existing token-signing certificate option, click the appropriate certificate, and then click Next.
12. Select the Create a new trust policy option, and then click Next.
13. Read the Introduction to Web Server (IIS) page, and then click Next.
14. Keep the Web server default check box selections, and then click Next
15. Click Install.
16. When the installation has completed, click Close.
17. Log on to ADFS-ACCOUNT as TREYRESEARCH\ADFSADMIN.
18. Repeat steps 2–16 for the ADFS-ACCOUNT computer using the TREYRESEARCH\ADFSADMIN user account.

Configure ADFS-ACCOUNT to work with AD RMS

The ADFS-ACCOUNT computer is a member of the TREYRESEARCH domain and forwards AD RMS requests to the CPANDL domain. In this section, you configure the AD FS trust policy, create a custom claim for the ProxyAddresses Active Directory attribute, add an Active Directory Account Store, and add and configure a resource partner.
First, configure the ADFS-ACCOUNT computer trust policy for the federation service in the TREYRESEARCH domain.To configure the trust policy on the AD FS account partner (ADFS-ACCOUNT)
1. Log on to ADFS-ACCOUNT with the TREYRESEARCH\adfsadmin account or another user account in the local Administrators group.
2. Click Start, point to Administrative Tools, and then click Active Directory Federation Services.
3. Expand Federation Service, right-click Trust Policy, and then click Properties.
4. In the Federation Service URI box, type urn:federation:treyresearch.net.Note
The Federation Service URI value is case sensitive.
5. In the Federation Service endpoint URL box, confirm that https://ADFS-ACCOUNT.treyresearch.net/adfs/ls/ is shown.
6. On the Display Name tab, in Display name for this trust policy, type Trey Research, and then click OK.

Next, create a custom claim that will be used with AD RMS.To create a custom claim
1. In the Active Directory Federation Services console, expand Federation Service, expand Trust Policy, and then expand My Organization.
2. Right-click Organization Claims, point to New, and then click Organization Claim.
3. In the Claim name box, type ProxyAddresses.Note
The claim name value is case-sensitive.
4. Select the Custom claim option, and then click OK.
*Important
Great care should be taken when allowing proxy addresses through a federated trust. If proxy addresses through federation are allowed, it is possible for a malicious user to spoof an authorized user's credentials and access the user's rights-protected content. If proxy addresses through federation is a requirement of your organization, you should implement a claims transformation module that will examine a proxy address from a federated user and make sure that it matches the forest in which the request originated. The option to allow a proxy address from a federated user is turned off by default in the Active Directory Rights Management Services console.
Next, add an Active Directory account store to the Federation Service for the TREYRESEARCH domain.To add an Active Directory account store to ADFS-ACCOUNT
1. In the Active Directory Federation Services console, expand Federation Service, expand Trust Policy, and then expand My Organization.
2. Right-click Account Stores, point to New, and then click Account Store.
3. On the Welcome to the Add Account Store Wizard page, click Next.
4. On the Account Store Type page, click the Active Directory Domain Services option, and then click Next. Note
On Windows Server 2003 R2 Enterprise Edition this option is called Active Directory.
5. On the Enable this Account Store page, select the Enable this account store check box, and then click Next.
6. On the Completing the Add Account Store Wizard page, click Finish.
7. Double-click the E-mail organization claim, select the Enabled check box, type mail in the LDAP attribute box, and then click OK.
8. Right-click the Active Directory account store, point to New, and then click Custom claim extraction.
9. In the Attribute box, type ProxyAddresses, and then click OK.

Finally, add a resource partner to the Federation Service in the TREYRESEARCH domain.To add a resource partner to the TREYRESEARCH domain
1. In the Active Directory Federation Services console, expand Federation Service, expand Trust Policy, and then expand Partner Organizations.
2. Right-click Resource Partners, point to New, and then click Resource Partner.
3. On the Welcome to the Add Resource Partner Wizard page, click Next.
4. Select the No option on the Import Policy File page, and then click Next.
5. On the Resource Partner Details page, in the Display name box, type CP&L Enterprises.
6. In the Federation Service URI box, type urn:federation:cpandl.com.Note
The Federation Service URL value is case sensitive.
7. In the Federation Service endpoint URL box, type https://adfs-resource.cpandl.com/adfs/ls/, and then click Next.
8. On the Federation Scenario page, click the Federated Web SSO option, and then click Next.
9. Select the UPN Claim and E-mail Claim check boxes, and then click Next.
10. Click the Pass all UPN suffixes through unchanged option, and then click Next.
11. Click the Pass all E-mail suffixes through unchanged option, and then click Next.
12. Ensure that the Enable this resource partner check box is checked, and then click Next.
13. Click Finish.
14. Right-click the new CP&L Enterprises resource partner, point to New, and then click Outgoing Custom Claim Mapping.
15. In the Outgoing custom claim name box, type ProxyAddresses, and then click OK.
16. Close the Active Directory Federation Services console.

Configure ADFS-RESOURCE to Work with AD RMS

The ADFS-RESOURCE computer is a member of the CPANDL domain and receives AD RMS requests from the TREYRESEARCH domain. In this section, you configure the AD FS trust policy, create a custom claim for the ProxyAddresses Active Directory attribute, add an Active Directory Account Store, add AD RMS as a Claims-aware application, and configure a resource partner.
First, configure the ADFS-RESOURCE computer trust policy for the federation service in the CPANDL domain.To configure the trust policy on the AD FS resource partner (ADFS-RESOURCE)
1. Log on to ADFS-RESOURCE with the CPANDL\ADFSADMIN account or another user account in the local Administrators group.
2. Click Start, point to Administrative Tools, and then click Active Directory Federation Services.
3. Expand Federation Service, right-click Trust Policy, and then click Properties.
4. In the Federation Service URI box, type urn:federation:cpandl.com.Note
The Federation Service URI value is case sensitive.
5. In the Federation Service endpoint URL box, confirm that https://ADFS-RESOURCE.cpandl.com/adfs/ls/ is shown.
6. On the Display Name tab, in Display name for this trust policy, type CP&L Enterprises, and then click OK.

Next, create a custom claim that will be used with AD RMS.To create a custom claim
1. In the Active Directory Federation Services console, expand Federation Service, expand Trust Policy, and then expand My Organization.
2. Right-click Organization Claims, point to New, and then click Organization Claim.
3. In the Claim name box, type ProxyAddresses.Note
The claim name value is case-sensitive.
4. Click the Custom claim option, and then click OK.

Next, add an Active Directory account store to the Federation Service for the CPANDL domain.To add an Active Directory account store to ADFS-RESOURCE
1. In the Active Directory Federation Services console, expand Federation Service, expand Trust Policy, and then expand My Organization.
2. Right-click Account Stores, point to New, and then click Account Store.
3. On the Welcome to the Add Account Store Wizard page, click Next.
4. On the Account Store Type page, select the Active Directory Domain Services option, and then click Next. Note
On Windows Server 2003 R2 Enterprise Edition, this option is called Active Directory.
5. On the Enable this Account Store page, select the Enable this account store check box, and then click Next.
6. On the Completing the Add Account Store Wizard page, click Finish.
7. Double-click the E-mail organization claim, select the Enabled check box, type mail in the LDAP attribute box, and then click OK.
8. Right-click the Active Directory account store, point to New, and then click Custom claim extraction.
9. In the Attribute box, type ProxyAddresses, and then click OK.

Next, add the AD RMS certification pipeline as a claims-aware application.To add the AD RMS certification pipeline as a claims-aware application
1. In the Active Directory Federation Services console, expand Federation Service, expand Trust Policy, and then expand My Organization.
2. Right-click Applications, point to New, and then click Application.
3. On the Welcome to the Add Application Wizard page, click Next.
4. On the Application Type page, select the Claims-aware application option, and then click Next.
5. In the Application display name box, type AD RMS Certification.
6. In the Application URL box, type https://adrms-srv.cpandl.com/_wmcs/certificationexternal/, and then click Next.Note
The application URL is case sensitive and the name of the AD RMS extranet cluster should match the return URL value of the ADRMS-SRV computer exactly. If the values do not match, AD FS functionality will not work.
7. On the Accepted Identity Claims page, select the User principal name (UPN) and E-mail check boxes, and then click Next.
8. On the Enable this Application page, select the Enable this application check box, and then click Next.
9. On the Completing the Add Application Wizard page, click Finish.
10. In the task pane, double-click ProxyAddresses, select the Enabled check box, and then click OK.

Use the following procedure to add the AD RMS licensing pipeline as a claims-aware application.To add AD RMS licensing as a claims-aware application
1. In the Active Directory Federation Services console, expand Federation Service, expand Trust Policy, and then expand My Organization.
2. Right-click Applications, point to New, and then click Application.
3. On the Welcome to the Add Application Wizard page, click Next.
4. On the Application Type page, select the Claims-aware application option, and then click Next.
5. In the Application display name box, type AD RMS Licensing.
6. In the Application URL box, type https://adrms-srv.cpandl.com/_wmcs/licensingexternal/, and then click Next.Note
The application URL is case sensitive and the computer name in the URL should match the return URL value of the ADRMS-SRV computer exactly. If the values do not match, AD FS functionality will not work.
7. On the Accepted Identity Claims page, select the User principal name (UPN) and E-mail check boxes, and then click Next.
8. On the Enable this Application page, click the Enable this application check box, and then click Next.
9. On the Completing the Add Application Wizard page, click Finish.
10. In the task pane, double-click ProxyAddresses, click the Enabled check box, and then click OK.

Next, add an account partner to ADFS-RESOURCE. This account partner receives requests from the ADFS-ACCOUNT computer in the TREYRESEARCH domain.To add an account partner to ADFS-RESOURCE
1. In the Active Directory Federation Services console, expand Federation Service, expand Trust Policy, and then expand Partner Organizations.
2. Right-click Account Partners, point to New, and then click Account Partner.
3. On the Welcome to the Add Account Partner Wizard page, click Next.
4. On the Import Policy File page, click the No option, and then click Next.
5. On the Resource Partner Details page , in the Display name box, type Trey Research.
6. In the Federation Service URI box, type urn:federation:treyresearch.net.
7. In the Federation Service endpoint URL box, type https://adfs-account.treyresearch.net/adfs/ls/, and then click Next.
8. On the Account Partner Verification page, type the path where the token signing certificate is stored, and then click Next.
9. Select the Federated Web SSO option, and then click Next.
10. Select the UPN Claim and E-mail Claim check boxes, and then click Next.
11. On the Accepted UPN Suffixes page, type treyresearch.net, click Add, and then click Next.
12. On the Accept E-mail Suffixes page, type treyresearch.net, click Add, and then click Next.
13. Verify that the Enable this account partner check box is selected, and then click Next.
14. Click Finish.
15. Right-click the Trey Research account partner, point to New, and then click Incoming Custom Claim Mapping.
16. In the Incoming custom claim name box, type ProxyAddresses, and then click OK.
17. Close the Active Directory Federation Services console.


Step 4: Configuring ADRMS-SRV to Work with AD FS


Windows Server 2008 includes the option to install identity federation support for AD RMS as a role service through Server Manager. This step of the guide covers the following tasks:
Grant security audit privileges to the AD RMS service account
Add the AD RMS extranet cluster URLs
Add the AD RMS Identity Federation Support role service
Enable Identity Federation Support in the Active Directory Rights Management Services console

Grant security audit privileges to the AD RMS service account

The AD RMS service account must be able to generate security audit events when using AD FS.To grant security audit privileges to the AD RMS service account
1. Log on to ADRMS-SRV with the cpandl\Administrator account.
2. Click Start, point to Administrative Tools, and then click Local Security Policy.
3. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
4. Expand Local Policies, and then click User Rights Assignment.
5. Double-click Generate security audits.
6. Click Add User or Group.
7. Type cpandl\adrmssrvc, and then click OK.
8. Click OK to close the Generate security audits properties sheet.

Add the AD RMS extranet cluster URLs

AD RMS-enabled clients consuming rights-protected content through a federated trust use the AD RMS extranet cluster URLs to create a rights account certificate.Caution
The AD RMS cluster URLs must be added before the Identity Federation Support role service is added by using Server Manager. If the cluster URLs are not added, you must edit the web.config files in the certificationexternal and licensingexternal directories manually.To add the AD RMS extranet cluster URLs
1. Log on to ADRMS-SRV with the CPANDL\ADRMSADMIN account.
2. Open the Active Directory Rights Management Services console. Click Start, point to Administrative Tools, and then click Active Directory Rights Management Services.
3. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
4. Right-click adrms-srv.cpandl.com, and then click Properties.
5. Click the Cluster URLs tab, and then select the Extranet URLs check box.
6. For Licensing, click https://, and then type adrms-srv.cpandl.com.
7. For Certification, click https://, and then type adrms-srv.cpandl.com.
8. Click OK.

Add the AD RMS Identity Federation Support role service

Next, add the Identity Federation Support role service through Server Manager.To add the Identity Federation Support Role Service
1. Log on to ADRMS-SRV with the CPANDL\ADRMSADMIN account.
2. Click Start, point to Administrative Tools, and then click Server Manager.
3. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
4. In the Roles Summary box, click Active Directory Rights Management Services, and then click Add Role Services.
5. Select the Identity Federation Support check box. Ensure that the Claims-aware Agent is listed as a required role service, and then click Add Required Role Services.
6. Click Next.
7. On the Configure Identity Federation Support page, type adfs-resource.cpandl.com, click Validate, and then click Next.
8. On the Introduction to AD FS page, click Next.
9. On the AD FS Role Service page, confirm that Claims-aware Agent is selected, and then click Next.
10. Click Install to add the Identity Federation Support role service to the ADRMS-SRV computer.
11. Click Finish.

Enable Identity Federation Support in the Active Directory Rights Management Services console

Once enabled, Identity Federation Support allows user accounts to use credentials established by a federated trust relationship through Active Directory Federation Services (AD FS) as a basis for obtaining a rights account certificate from an AD RMS cluster.To enable AD RMS identity federation support in the Active Directory Rights Management Services console
1. Log on to ADRMS-SRV with the CPANDL\ADRMSADMIN account.
2. Open the Active Directory Rights Management Services console and expand the AD RMS cluster.
3. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
4. In the console tree, expand Trust Policies, and then click Federated Identity Support.
5. In the Actions pane, click Enable Federated Identity Support.
6. In the Actions pane, click Properties.
7. On the Active Directory Federation Service Policies tab, in Federated Identity Certificate validity period, type 7. This is the number of days that federated rights account certificates are to be valid.
8. Click OK.


Step 5: Verifying AD RMS Functionality


The AD RMS client is included in the default installation of Windows Vista and Windows Server 2008. Previous versions of the client are available for download for some earlier versions of the Windows operating systems. For more information, see the Windows Server 2003 Rights Management Services page in the Microsoft Windows Server TechCenter (http://go.microsoft.com/fwlink/?LinkId=68637).
Before you can publish or consume rights-protected content on Windows Vista, you must add the AD RMS cluster URL, the ADFS-RESOURCE URL, and the ADFS-ACCOUNT URL to the Internet Explorer Local Intranet security zone of the ADRMS-CLNT2 computer. This is required to ensure that your credentials are automatically passed from Microsoft Office Word to the AD RMS Web services.To add AD RMS cluster URL to the Internet Explorer Local Intranet security zone
1. Log on to ADRMS-CLNT2 as Terence Philip (TREYRESEARCH\tphilip).
2. Click Start, click Control Panel, click Network and Internet, and then click Internet Options.
3. Click the Security tab, and then click Local Intranet.
4. Click Sites, and then click Advanced.
5. In the Add this website to the zone box, do the following:
a. Type https://adrms-srv.cpandl.com, and then click Add.
b. Type https://adfs-resource.cpandl.com, and then click Add.
c. Type https://adfs-account.treyresearch.net, and then click Add.

To verify the functionality of the AD RMS deployment, you log on as Nicole Holliday, create a Microsoft Word 2007 document, and then restrict permissions on it so that Terrence Philip is able to read the document but is unable to change, print, or copy it. You then log on as Terence Philip, verifying that Terence Philip can read the document but do nothing else with it.To restrict permissions on a Microsoft Word document
1. Log on to ADRMS-CLNT as Nicole Holliday (CPANDL\nhollida).
2. Click Start, point to All Programs, point to Microsoft Office, and then click Microsoft Office Word 2007.
3. Type Only Terence Philip can read this document, but cannot change, print, or copy it. Click Microsoft Office Button, point to Prepare, point to Restrict Permission, and then click Restricted Access.
4. Click the Restrict permission to this document check box.
5. In the Read text box, type TPHILIP@TREYRESEARCH.NET, and then click OK to close the Permission dialog box.
6. Click the Microsoft Office Button, click Save As, and then save the file as \\adrms-db\public\ADRMS-TST.docx
7. Log off as Nicole Holliday.

Finally, log on as Terence Philip on ADRMS-CLNT2 in the TREYRESEARCH.NET domain and attempt to open the document, ADRMS-TST.docx.To view a protected document
1. Log on to ADRMS-CLNT2 as Terence Philip (TREYRESEARCH\tphilip).
2. Click Start, point to All Programs, point to Microsoft Office, and then click Microsoft Office Word 2007.
3. Click the Microsoft Office Button, click Open, and then type \\ADRMS-DB\PUBLIC \ADRMS-TST.docx. If you are prompted for credentials, use CPANDL\Administrator.
The following message appears: "Permission to this document is currently restricted. Microsoft Office must connect to https://adrms-srv.cpandl.com/_wmcs/licensing to verify your credentials and download your permissions."
4. Click OK.
The following message appears: "Verifying your credentials for opening content with restricted permissions".
5. When the document opens, click Microsoft Office Button. Notice that the Print option is not available.
6. Click View Permission in the message bar. You should see that Terence Philip has been restricted to being able only to read the document.
7. Click OK to close the My Permissions dialog box, and then close Microsoft Word.

You have successfully deployed and demonstrated the functionality of using identity federation with AD RMS, using the simple scenario of applying restricted permissions to a Microsoft Word 2007 document. You can also use this deployment to explore some of the additional capabilities of AD RMS through additional configuration and testing.

No comments: