This registry key is only needed if the claims provider server is different from the claims provider server used by Microsoft Dynamics CRM Server; for example, the Microsoft Dynamics CRM client authenticates across realms to a different domain. a. With Administrator privileges, open the Registry Editor. b. Open the registry key
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\MSCRMClient. c. Create the registry string HomeRealmUrl. d. Enter the value data of the federated AD FS. This URL will end in
/adfs/services/trust/mex. For example, https://adfs.contoso.com/adfs/services/trust/mex. e. Close the Registry Editor. f. Configure Dynamics CRM for Outlook. More information: Set up CRM for Outlook
You should now be able to connect Dynamics CRM for Outlook to Microsoft Dynamics CRM
Server by using claims-based authentication.
Use an administrative template (.adm) file
Modify the following sample data to create an .adm file to use group policy to publish the
HomeRealmUrl registry setting.
CLASS MACHINECATEGORY "Microsoft Dynamics CRM" KEYNAME
"Software\Policies\Microsoft\MSCRMClient" POLICY "Home Realm URL" EXPLAIN "Allow
Administrator to specify the Home Realm URL for federated domains." PART "Specify
Home Realm URL (example: https://adfs.contoso.com/adfs/services/trust/mex" EDITTEXT
REQUIREDVALUENAME "HomeRealmUrl" END PART END POLICYEND CATEGORY
For more information, see Administrative Template File Format .
See Also
Install CRM for Outlook
Configure IFD for Microsoft Dynamics CRM
Additional considerations for claims-based authentication deployment
The following section covers additional considerations for your claims-based authentication deployment.
In This Section
Manually updating a claims provider
Claims-based authentication and security token expiration
System time synchronization and claims-based authentication
41
