Microsoft Dynamics CRM 2011 Installing Guide

Version 5.9.0

This document is provided "as-is". Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. You bear the risk of using it. Some examples depicted herein are provided for illustration only and are fictitious. No real association or connection is intended or should be inferred. This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes. 2013 Microsoft Corporation. All rights reserved. Microsoft, Active Directory, ActiveX, Azure, BizTalk, JScript, Microsoft Dynamics, Outlook, SharePoint, SQL Server, Visual Basic, Visual Studio, Windows, Windows Server, and Windows Vista are trademarks of the Microsoft group of companies. All other trademarks are property of their respective owners.

Contents
Microsoft Dynamics CRM 2011 Installing Guide ........................................................................... 13 In This Section ............................................................................................................................ 13 Send us your comments about this document (Install Guide) ...................................................... 13 Microsoft Dynamics CRM Server 2011 Installation Instructions ................................................... 14 Components installed during Microsoft Dynamics CRM Server Setup ...................................... 14 Microsoft Dynamics CRM Server 2011 installed configuration components ......................... 14 Other software components installed during setup .............................................................. 18 See Also ...................................................................................................................................... 20 Microsoft Dynamics CRM Server 2011 installation ....................................................................... 20 Microsoft Dynamics CRM installation files ................................................................................ 20 See Also ...................................................................................................................................... 21 Install Microsoft Dynamics CRM 2011 Front End Server and Back End Server roles .................... 21 In This Topic ............................................................................................................................... 22 Install Back End Server role ........................................................................................................ 22 Install Front End Server role....................................................................................................... 26 Create the Microsoft Dynamics CRM organization.................................................................... 29 See Also ...................................................................................................................................... 30 Install Microsoft Dynamics CRM 2011 Server on a server without Microsoft Dynamics CRM installed ...................................................................................................................................... 30 See Also ...................................................................................................................................... 36 Install Microsoft Dynamics CRM Reporting Extensions ................................................................ 36 See Also ...................................................................................................................................... 39 Microsoft Dynamics CRM Report Authoring Extension Installation Instructions ......................... 39 See Also ...................................................................................................................................... 41 Upgrade from Microsoft Dynamics CRM 4.0................................................................................. 41 Upgrade options......................................................................................................................... 41 See Also ...................................................................................................................................... 42 Microsoft Dynamics CRM Server 2011 upgrade preparations ...................................................... 42 Software prerequisites ............................................................................................................... 42 See Also ...................................................................................................................................... 43

Upgrade from Microsoft Dynamics CRM 4.0 Server 64-bit editions ............................................. 43 Tasks to perform before the upgrade ........................................................................................ 44 To run the upgrade, follow these steps ..................................................................................... 44 See Also ...................................................................................................................................... 47 Upgrade from Microsoft Dynamics CRM 4.0 Server 32-bit editions ............................................. 47 Migrate from 32-bit versions of Microsoft Dynamics CRM 4.0 Server to Microsoft Dynamics CRM 2011 Server .................................................................................................................... 47 Migrate by using a new instance of SQL Server ..................................................................... 48 Migrate by using the same instance of SQL Server ................................................................ 49 See Also ...................................................................................................................................... 50 Migrate from Microsoft Dynamics CRM 3.0 Server to Microsoft Dynamics CRM 2011 Server .... 50 See Also ...................................................................................................................................... 51 Upgrade Microsoft Dynamics CRM Connector for SQL Server Reporting Services....................... 51 See Also ...................................................................................................................................... 52 After the upgrade .......................................................................................................................... 52 Post-upgrade steps for servers .................................................................................................. 52 Verify intranet Web addresses for in-place or connect to existing deployment upgrades ... 52 Post-upgrade steps for clients ................................................................................................... 53 See Also ...................................................................................................................................... 53 Troubleshooting installation and upgrade .................................................................................... 54 Log files ...................................................................................................................................... 54 See Also ...................................................................................................................................... 54 Server installation and upgrade issues .......................................................................................... 54 In This Topic ............................................................................................................................... 54 Timeout expired error message during organization upgrade .................................................. 54 Clients cannot connect to Microsoft Dynamics CRM Web application ..................................... 55 Microsoft Dynamics CRM Server 2011 cannot connect to Microsoft SQL Server ..................... 55 Troubleshooting WIF installation failures .................................................................................. 55 Claims-based authentication issues ........................................................................................... 55 'Login failed for DomainName\ServerName$" error message after Microsoft Dynamics CRM Server 2011 install, repair, or configure ................................................................................. 56 See Also ...................................................................................................................................... 56 Install Microsoft Dynamics CRM Server 2011 on multiple computers ......................................... 56 In This Topic ............................................................................................................................... 56 Multiple-server configuration overview .................................................................................... 57

Step 1: Enable network load balancing ...................................................................................... 58 Step 2: Configure Active Directory ............................................................................................. 58 Step 3: Install Microsoft Dynamics CRM servers ....................................................................... 60 Step 4: Configure NLB for the deployment ................................................................................ 61 Configure domain names for IFD ............................................................................................ 62 Step 5: Verify and monitor the cluster installation .................................................................... 63 See Also ...................................................................................................................................... 63 Install Microsoft Dynamics CRM Server 2011 to use a Microsoft SQL Server cluster environment .................................................................................................................................................... 63 Base configuration ..................................................................................................................... 64 See Also ...................................................................................................................................... 64 Option 1: Install a new Microsoft Dynamics CRM Server 2011 deployment ................................ 64 Step 1: Create the SQL Server cluster ........................................................................................ 64 Step 2: Install Microsoft Dynamics CRM Server 2011 ................................................................ 65 See Also ...................................................................................................................................... 65 Option 2: Rehome or configure an existing Microsoft Dynamics CRM Server 2011 deployment that connects to a SQL Server cluster that stores only the organization database ................... 66 See Also ...................................................................................................................................... 67 Option 3: Rehome or configure an existing Microsoft Dynamics CRM Server 2011 deployment that connects to a SQL Server cluster that stores both the configuration and organization databases ................................................................................................................................... 67 See Also ...................................................................................................................................... 69 Configure an organization database for SQL Server 2008 database mirroring ............................. 69 See Also ...................................................................................................................................... 70 Configure a Microsoft Dynamics CRM organization for database mirroring ................................ 70 See Also ...................................................................................................................................... 74 Monitor and test for failover ......................................................................................................... 74 See Also ...................................................................................................................................... 75 Set configuration and organization databases for SQL Server 2012 AlwaysOn failover ............... 75 Prerequisites ........................................................................................................................... 76 Enable SQL Server 2012 AlwaysOn ......................................................................................... 77 Create the availability group .................................................................................................. 77 Create the SQL logins for the Microsoft Dynamics CRM security groups on all secondary replicas ................................................................................................................................ 79

Update the configuration database connection string in the Windows registry ................... 80 Update the connection string in the configuration database ................................................ 81 Restart IIS and Microsoft Dynamics CRM services ................................................................. 81 Monitor the availabity group and test for failover ................................................................. 82 Known issues .......................................................................................................................... 83 Some Deployment Manager organization features do not work after failover ................. 83 See Also ...................................................................................................................................... 83 Microsoft Dynamics CRM 2011 E-mail Router Installation Instructions ....................................... 84 In This Section ............................................................................................................................ 84 See Also ...................................................................................................................................... 84 Overview........................................................................................................................................ 85 See Also ...................................................................................................................................... 85 E-mail Router ................................................................................................................................. 85 See Also ...................................................................................................................................... 86 Install E-mail Router and Rule Deployment Wizard ...................................................................... 86 Install the E-mail Router............................................................................................................. 87 Minimum permissions required to run the E-mail Router and the Rule Deployment Wizard .. 89 See Also ...................................................................................................................................... 89 Upgrade the E-mail Router ............................................................................................................ 90 In This Topic ............................................................................................................................... 90 Upgrading both the E-mail Router and Microsoft Dynamics CRM ............................................ 90 Back up and use E-mail Router state files and Smart Matching settings................................... 91 Upgrade the E-mail Router to Microsoft Dynamics CRM 2011 ................................................. 93 See Also ...................................................................................................................................... 94 Configure the E-mail Router .......................................................................................................... 94 In This Topic ............................................................................................................................... 94 E-mail Router Configuration Manager ....................................................................................... 95 Configuration profiles ............................................................................................................. 96 Authentication types .............................................................................................................. 96 Access credentials................................................................................................................... 97 Deployments........................................................................................................................... 99 Microsoft Dynamics CRM Server......................................................................................... 99 One deployment type at a time ........................................................................................ 100 Obtaining user e-mail credentials from Microsoft Dynamics CRM................................... 100 Access Credentials ............................................................................................................. 100

Configuring E-mail Routing for Multiple Configurations and Deployments ......................... 101 Keep user credentials secure ................................................................................................... 101 HTTPS option ........................................................................................................................ 102 HTTP option .......................................................................................................................... 102 Managing certificates to use the E-mail Router with HTTPS ................................................ 102 Set email access type ............................................................................................................... 103 Connect the E-mail Router to Microsoft Dynamics CRM Online .......................................... 103 Deploy inbox rules ................................................................................................................... 104 Create the rule manually ...................................................................................................... 105 Set up a forward mailbox ......................................................................................................... 106 Complete the forward mailbox............................................................................................. 107 See Also .................................................................................................................................... 108 Install E-mail Router on multiple computers .............................................................................. 108 In This Topic ............................................................................................................................. 108 Step 1: Establish the cluster ..................................................................................................... 108 Step 2: Install the E-mail Router to the active primary node in the cluster ............................ 109 Step 3: Install the E-mail Router to the passive node in the cluster ........................................ 110 Step 4: Create the generic resource service for the cluster .................................................... 111 Step 5: Verify and monitor the cluster ..................................................................................... 112 See Also .................................................................................................................................... 112 Troubleshooting E-mail Router issues ......................................................................................... 112 In This Section .......................................................................................................................... 112 See Also .................................................................................................................................... 112 E-mail Router installation issues ................................................................................................. 112 Logging (E-mail Router) ............................................................................................................ 113 See Also .................................................................................................................................... 113 Incoming e-mail configuration issues .......................................................................................... 114 In This Topic ............................................................................................................................. 114 Login timeout error .................................................................................................................. 114 Unauthorized access to the mailbox ........................................................................................ 115 Mailbox not found (access test fails) ....................................................................................... 116 Mailbox not found (access test succeeds) ............................................................................... 118 The E-mail Router service configuration parameter "EmailUser" is missing ........................... 119 SSL/TLS error from E-mail Router Configuration Manager test access ................................... 119 POP3 issues .............................................................................................................................. 120 Error connecting the E-mail Router a POP3 mailbox............................................................ 120 Issues with using a POP3 e-mail account.............................................................................. 120

See Also .................................................................................................................................... 120 Outgoing e-mail configuration issues .......................................................................................... 120 Test Access error ...................................................................................................................... 121 Load Data error ........................................................................................................................ 121 See Also .................................................................................................................................... 122 Users do not receive Microsoft Dynamics CRM e-mail messages .............................................. 122 See Also .................................................................................................................................... 123 Test Access feature...................................................................................................................... 123 Test Access error ...................................................................................................................... 123 Error message when you send an email message by using the Microsoft Dynamics CRM web application ............................................................................................................................ 124 See Also .................................................................................................................................... 124 Microsoft Dynamics CRM 2011 for Outlook Installation Instructions......................................... 124 In This Section .......................................................................................................................... 125 See Also .................................................................................................................................... 126 Installing on a computer that does not have Microsoft Dynamics CRM for Outlook installed .. 126 Task 1: Install Microsoft Dynamics CRM for Outlook .............................................................. 126 Task 2: Configure Microsoft Dynamics CRM for Outlook ........................................................ 128 Task 3: Configure user email settings ...................................................................................... 130 User and queue email configuration .................................................................................... 130 Incoming email messaging options ...................................................................................... 131 Outgoing email messaging options ...................................................................................... 131 See Also .................................................................................................................................... 132 Upgrade Microsoft Dynamics CRM 4.0 for Outlook to Microsoft Dynamics CRM 2011 for Outlook .................................................................................................................................................. 132 Notes about upgrading Microsoft Dynamics CRM for Outlook ............................................ 132 Cross-architecture upgrade of Microsoft Dynamics CRM for Outlook................................. 133 Task 1: Install Microsoft Dynamics CRM 2011 for Outlook ..................................................... 133 Task 2: Configure Microsoft Dynamics CRM for Outlook ........................................................ 134 See Also .................................................................................................................................... 137 Troubleshooting Microsoft Dynamics CRM for Outlook installation, configuration and upgrade .................................................................................................................................................. 138 Troubleshooting installation and configuration tips and known issues .................................. 138 Microsoft Dynamics CRM Online with Office 365 ................................................................ 138 Log files .................................................................................................................................... 138

Event Viewer ............................................................................................................................ 139 Disable the CRM for Outlook button on the Web application................................................. 140 See Also .................................................................................................................................... 140 Install Microsoft Dynamics CRM for Outlook by using Microsoft System Center Configuration Manager 2007 .......................................................................................................................... 140 In This Topic ............................................................................................................................. 141 Prerequisites ............................................................................................................................ 141 Prepare System Center Configuration Manager .................................................................. 141 Distribute prerequisite software for Microsoft Dynamics CRM for Outlook ....................... 141 Use Microsoft System Center Configuration Manager 2007 to distribute Microsoft Dynamics CRM for Outlook ................................................................................................................... 141 Part 1: Start the Distribute Software to Collection Wizard...................................................... 142 Part 2: Continue the Distribute Software to Collection Wizard ............................................... 143 Part 3: Complete the Distribute Software to Collection Wizard .............................................. 144 Inspect the distribution package.............................................................................................. 145 See Also .................................................................................................................................... 146 Installing Microsoft Dynamics CRM for Outlook with Roaming User Profiles, Windows Server Remote Desktop Services, or Citrix Presentation Server ......................................................... 147 Roaming User Profiles .......................................................................................................... 147 Windows Server Remote Desktop Services .......................................................................... 147 Citrix XenApp ........................................................................................................................ 148 Disable the Get CRM for Outlook button................................................................................. 148 See Also .................................................................................................................................... 151 Install Microsoft Dynamics CRM 2011 for Outlook without an Internet connection ................. 151 Step 1: Create the Redist folder structure ............................................................................... 152 Step 2: Create the subfolders under the Redist folder ............................................................ 152 Step 3: Download the prerequisite files .................................................................................. 153 See Also .................................................................................................................................... 155 Microsoft Dynamics CRM 2011 Language Pack Installation Instructions ................................... 155 Overview -- Language Pack Installation ................................................................................... 156 In This Section .......................................................................................................................... 156 See Also .................................................................................................................................... 156 Install and deploy a Language Pack ............................................................................................. 156 In This Topic ............................................................................................................................. 156 Step1: Install the Language Pack in the deployment ............................................................... 156 Step 2: Provision the Language Pack in your Microsoft Dynamics CRM deployment ............. 157

Step 3: Select the language to display the user interface and help......................................... 158 See Also .................................................................................................................................... 159 Upgrade and deploy a Language Pack......................................................................................... 159 See Also .................................................................................................................................... 159 Language Pack installation issues ................................................................................................ 160 You receive a "Setup could not install Language Pack Name" error message ........................ 160 See Also .................................................................................................................................... 160 Microsoft Dynamics CRM 2011 Uninstall, Repair, and Change Instructions............................... 160 In This Section .......................................................................................................................... 161 See Also .................................................................................................................................... 161 Uninstall, change, or repair Microsoft Dynamics CRM Server 2011 ........................................... 161 Components not removed during a Microsoft Dynamics CRM Server 2011 uninstall ......... 162 See Also .................................................................................................................................... 163 Uninstall or repair Microsoft Dynamics CRM Reporting Extensions ........................................... 163 See Also .................................................................................................................................... 164 Uninstall or repair Microsoft Dynamics CRM Report Authoring Extension ................................ 164 See Also .................................................................................................................................... 164 Uninstall, change, or repair E-mail Router .................................................................................. 165 See Also .................................................................................................................................... 166 Uninstall or repair Microsoft Dynamics CRM for Outlook .......................................................... 166 Files not removed during a Microsoft Dynamics CRM for Outlook uninstall .......................... 168 See Also .................................................................................................................................... 168 Uninstall or repair a Language Pack ............................................................................................ 168 See Also .................................................................................................................................... 169 Use the Command Prompt to Install Microsoft Dynamics CRM 2011 ........................................ 170 General procedures ................................................................................................................. 170 In This Section .......................................................................................................................... 171 See Also .................................................................................................................................... 172 Install Microsoft Dynamics CRM Server 2011 ............................................................................. 172 Parameters ............................................................................................................................... 172 See Also .................................................................................................................................... 173 Microsoft Dynamics CRM 2011 Server XML configuration file ................................................... 173

See Also .................................................................................................................................... 185 Sample server XML configuration file ......................................................................................... 186 See Also .................................................................................................................................... 187 Sample server XML configuration file for installing with pre-created groups ............................ 187 See Also .................................................................................................................................... 188 Install Microsoft Dynamics CRM Server 2011 roles .................................................................... 188 Parameters ........................................................................................................................... 189 Server role XML configuration file ........................................................................................... 189 See Also .................................................................................................................................... 191 Sample XML configuration file that installs only the WebApplicationServer role ...................... 191 See Also .................................................................................................................................... 192 Sample XML configuration file that installs only the HelpServer role......................................... 192 Change the Microsoft Dynamics CRM HelpServer URL ........................................................ 193 See Also .................................................................................................................................... 194 Install Microsoft Dynamics CRM Reporting Extensions (2) ......................................................... 194 Microsoft Dynamics CRM Reporting Extensions requirements ............................................... 194 Command example .................................................................................................................. 195 See Also .................................................................................................................................... 195 Microsoft Dynamics CRM Reporting Extensions XML configuration file .................................... 195 See Also .................................................................................................................................... 197 Sample Microsoft Dynamics CRM Reporting Extensions XML configuration file........................ 197 Logging .................................................................................................................................. 198 See Also .................................................................................................................................... 198 Command example Microsoft Dynamics CRM Report Authoring Extension .............................. 198 See Also .................................................................................................................................... 199 Microsoft Dynamics CRM Report Authoring Extension XML configuration file .......................... 199 See Also .................................................................................................................................... 200 Sample Microsoft Dynamics CRM Report Authoring Extension XML configuration file ............. 200 See Also .................................................................................................................................... 201 Install Microsoft Dynamics CRM for Outlook using a Command Prompt ................................... 201 In This Topic ............................................................................................................................. 201 Step 1: Install files .................................................................................................................... 202

Command examples for Microsoft Dynamics CRM for Outlook installation ....................... 202 Parameters for Microsoft Dynamics CRM for Outlook installation .................................. 202 Sample Microsoft Dynamics CRM for Outlook XML configuration file for installation ........ 204 Step 2: Configure Microsoft Dynamics CRM for Outlook by using an XML configuration file. 205 Command examples for Microsoft Dynamics CRM for Outlook configuration ....................... 205 Microsoft Dynamics CRM for Outlook XML configuration file elements ................................. 206 User credentials are required when you run the Configuration Wizard ................................. 208 Sample Microsoft Dynamics CRM for Outlook XML configuration file for configuration........ 208 See Also .................................................................................................................................... 210 Install Microsoft Dynamics CRM E-mail Router........................................................................... 210 E-mail Router XML configuration file ....................................................................................... 211 Sample Microsoft Dynamics CRM E-mail Router XML configuration file ................................ 213 See Also .................................................................................................................................... 213 Microsoft Dynamics CRM Server 2011 installation troubleshooting .......................................... 213 Setup fails or client receives an unhandled exception when trying to connect after you install Microsoft Dynamics CRM Server 2011 ................................................................................. 214 You Receive an Unknown Error (0x80005000) error message during a quiet-mode installation .............................................................................................................................................. 216 See Also .................................................................................................................................... 216 Microsoft Dynamics CRM 2011 Post-Installation and Configuration Guidelines ........................ 216 In This Topic ............................................................................................................................. 216 Make Microsoft Dynamics CRM client-to-server network communications more secure...... 217 Configuring Microsoft Dynamics CRM for HTTPS ................................................................. 217 Configure a Microsoft Dynamics CRM Internet-facing deployment ........................................ 218 Add or remove sample data..................................................................................................... 218 Configuration guidelines for new deployments....................................................................... 218 Install a solution from the Microsoft Dynamics Marketplace ................................................. 218 Instructions for removing the Resource Center....................................................................... 218 See Also .................................................................................................................................... 221

Microsoft Dynamics CRM 2011 Installing Guide

This guide is part of the Microsoft Dynamics CRM 2011 Implementation Guide, which consists of the following three documents: Microsoft Dynamics CRM 2011 Planning Guide: Use this guide to determine what you have to plan for Microsoft Dynamics CRM. This guide focuses on supported topologies, system requirements, and technical considerations to address before installation. Microsoft Dynamics CRM 2011 Installing Guide: Use this guide to learn about how you install Microsoft Dynamics CRM applications. This guide includes step-by-step instructions for running Setup, command-line installation instructions, and guidance about how to remove Microsoft Dynamics CRM. Microsoft Dynamics CRM 2011 Operating and Maintaining Guide: You can read this guide to learn how to back up, restore, and perform system recovery for Microsoft Dynamics CRM data. Also, this guide has troubleshooting steps for known issues. IT Pros can use the resources and topics in this guide to help them install and configure onpremises deployment of Microsoft Dynamics CRM 2011. Addtionally, some topics also include information for Microsoft Dynamics CRM Online.

In This Section
Microsoft Dynamics CRM Server 2011 Installation Instructions Microsoft Dynamics CRM 2011 E-mail Router Installation Instructions Microsoft Dynamics CRM 2011 for Outlook Installation Instructions Microsoft Dynamics CRM 2011 Language Pack Installation Instructions Use the Command Prompt to Install Microsoft Dynamics CRM 2011 Microsoft Dynamics CRM 2011 Post-Installation and Configuration Guidelines

Send us your comments about this document (Install Guide)

If you have a question or comment about this document, click to send an e-mail message to the Microsoft Dynamics CRM content team. 13

If your question is about Microsoft Dynamics CRM products, and not about the content of this book, search the Microsoft Help and Support Center or the Microsoft Knowledge Base.

Microsoft Dynamics CRM Server 2011 Installation Instructions

This section explains how to install Microsoft Dynamics CRM Server 2011. In addition, there is installation troubleshooting information and procedures to uninstall Microsoft Dynamics CRM Server 2011. Important For up-to-date information, see the Microsoft Dynamics CRM 2011 and Microsoft Dynamics CRM Online Readme.

Components installed during Microsoft Dynamics CRM Server Setup

This section describes what is installed during Microsoft Dynamics CRM Server Setup.

Microsoft Dynamics CRM Server 2011 installed configuration components

When you install Microsoft Dynamics CRM Server 2011, Setup creates the default folders listed in the following table.

Folder

Comments

SystemDrive:\Program Files\Microsoft Dynamics Microsoft Dynamics CRM Server 2011 CRM\ program files SystemDrive:\Program Files\Microsoft Dynamics Contains a Microsoft Dynamics CRM CRM\LangPacks\<LanguageID>\Reports\MSCRM subfolder that contains an .rdl file for each default report SystemDrive:\Program Files\Microsoft Dynamics Location of Language Pack installations. Language Packs are downloaded and installed CRM\LangPacks separately

14

Folder

Comments

SystemDrive:\Program Files\Microsoft Dynamics Stores trace file logs when tracing is enabled CRM\Trace SystemDrive:\Program Files\Microsoft Dynamics Microsoft Dynamics CRM website and Web CRM\CRMWeb services SystemDrive:\Program Files\Microsoft Dynamics Microsoft Dynamics CRM report services CRM\CRMWeb\CRMReports

The following Web components are added.

Component Application Pool

Name CRMAppPool

Description Microsoft Dynamics CRM Server Setup creates a separate application pool for the Microsoft Dynamics CRM application. Microsoft Dynamics CRM Server Setup creates a separate application pool for the Deployment Web Service. Web site for Microsoft Dynamics CRM. Facilitates the implementation of xRM deployments. Services the Microsoft Dynamics CRM Help system for the application.

Application Pool

CRMDeploymentServiceAppPool

Site

Microsoft Dynamics CRM

Applications

XRMDeployment

Applications

Help

15

The following Active Directory groups are added. When the Active Directory domain is set to Native Mode, this group must be of the type Domain Local Security or Universal Security.

Group PrivReportingGroup

Description Privileged Microsoft Dynamics CRM user group for reporting functions. This group is created during Microsoft Dynamics CRM Server Setup and configured during Microsoft Dynamics CRM Reporting Extensions Setup. Privileged Microsoft Dynamics CRM user group for special administrative functions; including CRMAppPool identity (domain user or Network Service). The users who configure Microsoft Dynamics CRM Server 2011 must be added to this group. All server processes/service accounts that require access to SQL Server; including CRMAppPool identity (domain user or Network Service). Members of this group have db_owner permission on the Microsoft Dynamics CRM databases. All Microsoft Dynamics CRM users are included in this group. This group is updated automatically as users are added and removed from Microsoft Dynamics CRM. By default, all Microsoft Dynamics CRM Reporting Services reports grant Browse permission to this group.

PrivUserGroup

SQLAccessGroup

ReportingGroup

The following services are added.

Service Microsoft Dynamics CRM Asynchronous

Description Services asynchronous processes such as bulk 16

Service Processing Service Microsoft Dynamics CRM Asynchronous Processing Service (maintenance)

Description e-mail and workflow. Services asynchronous maintenance such as encryption key generation for authentication and database deletion clean up. Handles the uncompressing of zipped files for data import. This service is installed as part of the Web Application Server role. The Sandbox Processing Service server role enables an isolated environment to allow for the execution of custom code, such as plug-ins.

Microsoft Dynamics CRM Unzip Service

Microsoft Dynamics CRM Sandbox Processing Service

The following SQL Server components are added.

Componen Name t Databases MSCRM_CONFIG OrganizationName_MSCRM

Description

Microsoft SQL Server Setup creates the SystemDrive:\Program Files\Microsoft SQL Server\MSSQL<ver>\MSSQL\Dat a\ folder and Microsoft Dynamics CRM Server Setup installs the Microsoft Dynamics CRM configuration database and organization databases in it. Microsoft Dynamics CRM Server Setup creates three SQL Server jobs that are used for maintenance.

SQL Server Jobs

OrganizationName_MSCRM.CreateAuditPartiti on MSCRM_CONFIG.HardDelete MSCRM_CONFIG.SiteWideCleanup

17

Componen Name t Logins PrivReportingGroup ReportingGroup SQLAccessGroup MSCRMSqlLogin

Description

Microsoft Dynamics CRM Server Setup creates SQL Server logins for the PrivReportingGroup, ReportingGroup, and SQLAccessGroup Active Directory groups that are created. MSCRMSqlLogin is used for time zone conversions when you use dashboards and charts, and do queries using Advanced Find. When Microsoft SQL Server is enabled to use common language runtime (CLR), this can significantly improve performance for those features. Note By default, CLR is not enabled in Microsoft SQL Server. For more information about how to enable CLR, see Enabling CLR Integration.

Other software components installed during setup

If not already installed, the following components are installed for a Full Server during Microsoft Dynamics CRM Server Setup: Microsoft SQL Reporting Service Report Viewer Control Microsoft SQL Server Native Client Microsoft Application Error Reporting Tool Microsoft Visual C++ Runtime Library 18

Windows Identity Foundation (WIF) Framework

Windows Server 2008 Web Server Role Indexing Service Microsoft .NET Framework 4, which includes the following components: Note The installation of Microsoft .NET Framework may require you to restart your computer before you can continue to run Microsoft Dynamics CRM Setup. Microsoft .NET Framework (required by Microsoft Dynamics CRM Server 2011) Windows Workflow Foundation (required by Microsoft Dynamics CRM Server 2011) Windows Presentation Foundation Windows Communication Foundation (WCF) (required by Microsoft Dynamics CRM Server 2011) Microsoft Chart Controls for Microsoft .NET Framework Windows Azure AppFabric SDK V1.0 Windows PowerShell Microsoft URL Rewrite Module for IIS File Server Resource Manager The following topics describe step-by-step procedures to install Microsoft Dynamics CRM Server 2011 or upgrade from an earlier version. In This Section
Microsoft Dynamics CRM Server 2011 installation Upgrade from Microsoft Dynamics CRM 4.0 Troubleshooting installation and upgrade Install Microsoft Dynamics CRM Server 2011 on multiple computers Install Microsoft Dynamics CRM Server 2011 to use a Microsoft SQL Server cluster environment Configure an organization database for SQL Server 2008 database mirroring

19

See Also
Microsoft Dynamics CRM 2011 Installing Guide Microsoft Dynamics CRM Server 2011 Installation Instructions

Microsoft Dynamics CRM Server 2011 installation

This section covers procedures to install Microsoft Dynamics CRM Server 2011 on a computer that does not already have Microsoft Dynamics CRM installed.

Follow these steps to install Microsoft Dynamics CRM Server 2011: 1. Verify that you have completed the necessary planning and that you have the required hardware and software components installed and running. For more information see the Microsoft Dynamics CRM 2011 Planning Guide. 2. Run Microsoft Dynamics CRM Server Setup. 3. Run Microsoft Dynamics CRM Reporting Extensions Setup. If Microsoft Dynamics CRM Server 2011 and Microsoft Dynamics CRM Reporting Extensions are installed on the same computer, a check box for invoking the Microsoft Dynamics CRM Reporting Extensions Setup will appear during Microsoft Dynamics CRM Server Setup. 4. If you want to configure Microsoft Dynamics CRM Server 2011 for Internet access, start Deployment Manager and run the Configure Claims-Based Authentication Wizard and then the Internet-Facing Deployment Configuration Wizard. For more information see the Deployment Manager Help. 5. If one or more Microsoft Dynamics CRM users will have their e-mail configured to use the E-mail Router or a forward mailbox, you must install E-mail Router to enable Microsoft Dynamics CRM e-mail message tracking. For more information, see Microsoft Dynamics CRM 2011 E-mail Router Installation Instructions in this guide.

Microsoft Dynamics CRM installation files

Use the following files on the CD/DVD drive or where the Microsoft Dynamics CRM installation files are located:

20

Setup file SetupServer.exe for Microsoft Dynamics CRM Server 2011 SetupSrsDataConnector.exe for the Microsoft Dynamics CRM Reporting Extensions Setupclient.exe for Microsoft Dynamics CRM for Outlook

Location ..\Server\amd64

..\Server\amd64\SrsDataConnector

..\Client\amd64 for 64-bit ..\Client\i386 for 32-bit

SetupEmailRouter.exe for Microsoft Dynamics CRM E-mail Router

..\EmailRouter\amd64 for 64-bit ..\EmailRouter\i386 for 32-bit

See Also
Microsoft Dynamics CRM Server 2011 Installation Instructions Install Microsoft Dynamics CRM 2011 Server on a server without Microsoft Dynamics CRM installed

Install Microsoft Dynamics CRM 2011 Front End Server and Back End Server roles
The following procedure installs Microsoft Dynamics CRM 2011 Front End Server and Back End Server roles on two separate servers that do not already have Microsoft Dynamics CRM Server installed. We recommend this configuration instead of a single Full Server deployment because it helps improve security and performance by isolating specific Microsoft Dynamics CRM Server services on each computer. As part of this procedure, the Microsoft Dynamics CRM Reporting Extensions are installed on the server where the Back End Server roles are installed, and the Deployment Tools are installed on the server where the Front End Server roles are installed. For more information about server roles, see Microsoft Dynamics CRM 2011 Server roles. A backend and frontend deployment configuration requires two separate computers running Windows Server. This example uses two computers that are named CRMbackend and CRMfrontend. 21

Important After Setup is completed you must either import or create at least one organization to be able to connect a client to the Microsoft Dynamics CRM deployment.

Installing on Windows Server 2012. If you are installing Microsoft Dynamics CRM Server 2011 on Windows Server 2012 you must download the latest Setup update and apply Microsoft Dynamics CRM 2011 Update Rollup 13 after Setup is finished. For more information, see Supported Windows Server 2012 editions. In this example, the Back End Server role will be installed before the Front End Server role.

In This Topic
Install Back End Server role Install Front End Server role Create the Microsoft Dynamics CRM organization

Install Back End Server role

On the computer named CRMbackend complete the following procedure.

1. Meet all requirements specified in Microsoft Dynamics CRM 2011 System Requirements and Required Components in the Planning Guide. 2. Log on to the domain as a user who has administrator-level privileges where Microsoft Dynamics CRM will be installed and who is a member of the Administrators group on the local computer. You cannot install the application as a member from a trusted domain. 3. Locate the Microsoft Dynamics CRM installation files. The Microsoft Dynamics CRM Server 2011 download packages can be located on the Microsoft Download Center. 4. In the folder where the Microsoft Dynamics CRM files are located, move to the Server\amd64 folder, and then double-click SetupServer.exe. 5. On the Welcome to Microsoft Dynamics CRM Setup page, we recommend that you click Get updates for Microsoft Dynamics CRM, to make sure that Setup has the most recent installation files. Click Next. 22

6. On the Product Key Information page, type your product key in the Product key boxes, and then click Next. 7. On the License Agreement page, review the information and if you accept the license agreement, click I accept this license agreement, and then click I Accept. 8. If Setup detects that components are missing, the Install Required Components page appears. If you have already installed the required components, this page will not appear. If you have not installed the required components listed, you can install them now. Click Install. When the components are installed, the status column will change from Not Installed to Installed, and you can click Next to continue. Note If you are prompted to restart the computer, do so, and then start Setup again. 9. On the Select Installation Location page, accept the default location or enter a different file installation location, and then click Next. 10. On the Specify Server roles page, select all the Back End Server roles. Leave the rest blank.

23

11. On the Specify Deployment Options page, in the Enter or select the name of the computer that is running SQL Server to use with the deployment box, type or select the instance of Microsoft SQL Server that will be used to store the Microsoft Dynamics CRM database (MSCRM_CONFIG). 12. On the Select the Organizational Unit page, click Browse to display your Active Directory structure. Select the location where you want the Microsoft Dynamics CRM organizational unit to be installed into, click OK, and then click Next. Microsoft Dynamics CRM security groups are created in this organizational unit. 13. On the Specify Service Accounts page, select the security accounts for the Microsoft Dynamics CRM services, and then click Next. The services are described below. For more information, see Minimum permissions required for Microsoft Dynamics CRM Setup, services, and components in Security considerations for Microsoft Dynamics CRM in the Planning Guide. Sandbox Processing Service. Enables an isolated environment to allow for the 24

execution of custom code, such as plug-ins. This isolated environment reduces the possibility of custom code affecting the operation of the organizations in the Microsoft Dynamics CRM deployment. Asynchronous Processing Service. Processes queued asynchronous events, such as bulk email or data import. We strongly recommend that you select a low-privilege domain account that is dedicated to running these services and is not used for any other purpose. Additionally, the user account that is used to run a Microsoft Dynamics CRM service cannot be a Microsoft Dynamics CRM user. This domain account must be a member of the Domain Users group. Additionally, if the Asynchronous Service and Sandbox Processing Service roles are installed, such as in a Full Server or a Back End Server installation, the domain account must be a member of the Performance Log Users security group. If you select to run the ASP.NET service under a domain user account that is not a domain administrator or a local administrator, you must set a local security policy after you install Microsoft Dynamics CRM Server 2011 for the ASP.NET service to work correctly. Also, depending on the password policies that you have implemented for your organization, the password for the user may expire. For more information, see How to use the ASP.NET utility to encrypt credentials and session state connection strings . 14. On the Select Microsoft Update OptIn page, you must select either of the following options. For more information about the legal terms and privacy with Microsoft Update licensing, see Windows Update FAQ. Use Microsoft Update when I check for updates (recommended). By selecting this option, Microsoft Dynamics CRM Server will use the Microsoft Update settings on the computer. I dont want to use Microsoft update. You should only select this option if the computer uses another method to install updates such as by using Windows Server Update Services (WSUS). 15. The System Checks page appears. This page is a summary of all requirements and recommendations for a successful installation. Errors must be resolved before installation can continue. If no errors, or only warnings appear, you can continue with the installation. To do this, click Next. 16. The Service Disruption Warning page appears. This page lists all services that will be stopped or restarted during Setup. 17. Review the Ready to Install Microsoft Dynamics CRM page, and then click Back to correct any warnings. When you are ready to continue, click Install.

25

18. When the Setup program is finished, click Finish. 19. Run Microsoft Dynamics CRM Reporting Extensions Setup. For more information, see Install Microsoft Dynamics CRM Reporting Extensions. Important Microsoft Dynamics CRM Reporting Reporting Extensions for SQL Server Reporting Services are required to complete the Front End Server and Back End Server deployment of Microsoft Dynamics CRM Server 2011. 20. When the Microsoft Dynamics CRM Reporting Extensions Setup has finished, complete the next procedure to install the Front End Server role.

Install Front End Server role

On the computer named CRMfrontend, follow these steps.

1. Log on to the domain as a user who has administrator-level privileges where Microsoft Dynamics CRM will be installed and who is a member of the Administrators group on the local computer. You cannot install the application as a member from a trusted domain. 2. In the folder where the Microsoft Dynamics CRM files are located, move to the Server\amd64 folder, and then double-click SetupServer.exe. 3. On the Welcome to Microsoft Dynamics CRM Setup page, we recommend that you click Get updates for Microsoft Dynamics CRM, to make sure that Setup has the most recent installation files. Click Next. 4. On the Product Key Information page, type your product key in the Product key boxes, and then click Next. 5. On the License Agreement page, review the information and, if you accept the license agreement, click I accept this license agreement, and then click I Accept. 6. If Setup detects that components are missing, the Install Required Components page appears. If you have already installed the required components, this page will not appear. If you have not installed the required components listed, you can install them now. Click Install. When the components are installed, the status column will change from Not Installed to Installed, and you can click Next to continue. 26

Note If you are prompted to restart the computer, do so, and then start Setup again. 7. On the Select Installation Location page, accept the default location or enter a different file installation location, and then click Next. 8. On the Specify Server roles page, select all the Front End Server and Deployment Administration Server roles. Leave the rest blank.

9. On the Specify Deployment Options page, click Connect to, and if necessary, upgrade an existing deployment, and then in the Enter or select the name of the computer that is running SQL Server to use with the deployment box, type or select the instance of SQL Server that you entered previously, and then click Next. 10. On the Select the Organizational Unit page, click Browse to display your Active Directory structure. Select the location where you want the Microsoft Dynamics CRM organizational unit to be installed, click OK, and then click Next. We recommend that 27

you select the same organization unit that you selected in the previous step. 11. On the Specify Service Accounts page, select the security accounts for the Microsoft Dynamics CRM services, and then click Next. The services are described below. For more information, see Minimum permissions required for Microsoft Dynamics CRM Setup, services, and components in Security considerations for Microsoft Dynamics CRM in the Planning Guide. Application Service. This service runs the Microsoft Dynamics CRM web application that is used to connect users to CRM data. Deployment Web Service . Manages the deployment by using the methods described in the Microsoft Dynamics CRM SDK, such as create an organization or remove a Deployment Administrator role from a user. Important We strongly recommend that you select a low-privilege domain account that is dedicated to running these services and is not used for any other purpose. Additionally, the user account that is used to run a Microsoft Dynamics CRM service cannot be a Microsoft Dynamics CRM user. This domain account must be a member of the Domain Users group. Additionally, if the Asynchronous Service and Sandbox Processing Service roles are installed, such as in a Full Server or a Back End Server installation, the domain account must a member of the Performance Log Users security group. If you select to run the ASP.NET service under a domain user account that is not a domain administrator or a local administrator, you must set a local security policy after you install Microsoft Dynamics CRM Server 2011 for the ASP.NET service to work correctly. Also, depending on the password policies that you have implemented for your organization, the password for the user may expire. For more information, see How to use the ASP.NET utility to encrypt credentials and session state connection strings. 12. On the Select a Web Site page, click Create a new Web site or click Select a Web Site and select a website from the list. By default, Setup will use the default website. Important We strongly recommend that you verify the status of the existing website before you specify Setup to use an existing website. We strongly recommend that the website you select is configured for SSL. For more information, see the IIS documentation. During the installation, Setup can bind the Microsoft 28

Dynamics CRM application to the HTTPS website. If you select a network port other than a default port, ensure that the firewall does not block the port. When you select the Create a new Web site option, Setup creates a new website for Microsoft Dynamics CRM Server 2011. You can specify the following option: Port Number. Type the TCP port number that Microsoft Dynamics CRM clients will use to connect to the Microsoft Dynamics CRM Server 2011. The default port number is 5555. 13. Click Next. 14. On the Specify E-mail Router Settings page, in the E-mail Router server name box, type the name of the computer where the E-mail Router will be installed. This computer will route Microsoft Dynamics CRM email messages. If you will not install the E-mail Router you can leave this box blank. However, if you install the E-mail Router later you must add the computer where the E-mail Router service is running when you use Local System, or if you use a domain user account, the account, to the PrivUserGroup security group. Click Next. 15. The System Checks page appears. This page is a summary of all requirements and recommendations for a successful installation. Errors must be resolved before installation can continue. If no errors, or only warnings appear, you can continue with the installation. To do this, click Next. 16. The Service Disruption Warning page appears. This page lists all services that will be stopped or restarted during Setup. 17. Review the Ready to Install Microsoft Dynamics CRM page, and then click Back to correct any warnings. When you are ready to continue, click Install. 18. When the Setup program is finished, click Finish.

Create the Microsoft Dynamics CRM organization

After Microsoft Dynamics CRM Server Setup program is finished installing the Back End Server, Front End Server, Deployment Administration Server roles, and Microsoft Dynamics CRM Reporting Extensions, you must create at least one organization to make the deployment available for users. If you have a previous deployment of Microsoft Dynamics CRM 2011 or Microsoft Dynamics CRM 4.0, you can import the database into the deployment. For more information, see the Microsoft Dynamics CRM Deployment Manager Help.

29

1. On the computer named CRMfrontend where the Deployment Administration Server role is installed, start Microsoft Dynamics CRM Deployment Manager. 2. Right-click Organizations, and then click New Organization. Complete the New Organization Wizard. For more information, see the Deployment Manager Help.

See Also
Microsoft Dynamics CRM Server 2011 Installation Instructions Install Microsoft Dynamics CRM 2011 Server on a server without Microsoft Dynamics CRM installed

Install Microsoft Dynamics CRM 2011 Server on a server without Microsoft Dynamics CRM installed

To install the Microsoft Dynamics CRM Server 2011 software, follow these steps: 1. Meet all requirements specified in Microsoft Dynamics CRM 2011 System Requirements and Required Components in the Planning Guide. Important Installing on Windows Server 2012 If you are installing Microsoft Dynamics CRM Server 2011 on Windows Server 2012 you must download the latest Setup update and apply Microsoft Dynamics CRM 2011 Update Rollup 13 after Setup is finished. For more information, see Supported Windows Server 2012 editions. 2. Log on to the domain as a user who has administrator-level privileges where Microsoft Dynamics CRM will be installed and who is a member of the Administrators group on the local computer. You cannot install the application as a member from a trusted domain. 3. See the Microsoft Dynamics CRM 2011 and Microsoft Dynamics CRM Online Readme file to determine the location of the Microsoft Dynamics CRM installation files. 30

4. In the folder where the Microsoft Dynamics CRM files are located, move to the Server\amd64 folder, and then double-click SetupServer.exe. 5. On the Welcome to Microsoft Dynamics CRM Setup page, we recommend that you click Get updates for Microsoft Dynamics CRM, to make sure that Setup has the most recent installation files. Click Next. 6. On the Product Key Information page, type your product key in the Product key boxes, and then click Next. 7. On the License Agreement page, review the information and if you accept the license agreement, click I accept this license agreement, and then click I Accept. 8. If Setup detects that components are missing, the Install Required Components page appears. If you have already installed the required components, this page will not appear. If you have not installed the required components listed, you can install them now. Click Install. When the components are installed, the status column will change from Not Installed to Installed, and you can click Next to continue. Note If you are prompted to restart the computer, do so, and then start Setup again. 9. On the Select Installation Location page, accept the default location or enter a different file installation location, and then click Next. 10. If you are installing Microsoft Dynamics CRM Server 2011, the Specify Server Roles page appears. By default, Full Server is selected and will install all server roles on the computer. Alternatively, you can select a predefined group of server roles or one or more individual server roles. Notice that all server roles must be deployed on the network in the same Active Directory domain for Microsoft Dynamics CRM to operate correctly. For more information, see Planning Deployment in the Planning Guide. Click Next. Important When you select a server role other than Full Server, Microsoft Dynamics CRM Server Setup does not create an organization database during the installation. If the deployment does not have an organization database, you must use Deployment Manager to create a new organization. For information about how to create a new organization, see the Deployment Manager Help. 11. On the Specify Deployment Options page, if Setup detects an existing deployment, you can select whether you want to create a new deployment or connect to an existing deployment. In the Enter or select the name of the computer that is running SQL Server to use with the deployment box, type or select the instance of SQL Server that 31

will be used to store the Microsoft Dynamics CRM database (MSCRM_CONFIG). Important When you select Create a new deployment, Setup creates a new organization database using the name that you specified and a configuration database by using the name MSCRM_CONFIG. An error message will appear if an MSCRM_CONFIG database already exists. You must delete this database to create a new MSCRM_CONFIG database. Only one deployment is supported for each instance of SQL Server. Currently, you cant specify a Microsoft SQL Server 2012 Availability Group listener during Microsoft Dynamics CRM Server Setup. To use SQL Server 2012 Availability Groups for high availability, complete the Microsoft Dynamics CRM Server installation by selecting the SQL Server 2012 primary replica. After Setup is complete, follow the procedure in the Set configuration and organization databases for SQL Server 2012 AlwaysOn failover topic. When you select Connect to, and if necessary, upgrade an existing deployment, Setup requires that a configuration database (MSCRM_CONFIG) already exist on the computer that is running SQL Server. An error message will appear if an MSCRM_CONFIG database does not already exist. 12. On the Select the Organizational Unit page, click Browse to display your Active Directory structure. Select the location where you want the Microsoft Dynamics CRM organizational unit to be installed into, click OK, and then click Next. Microsoft Dynamics CRM security groups are created in this organizational unit. 13. On the Specify Service Accounts page, select the security accounts for the Microsoft Dynamics CRM services, and then click Next. The services are described below. For more information, see Minimum permissions required for Microsoft Dynamics CRM Setup, services, and components in Security considerations for Microsoft Dynamics CRM in the Planning Guide. Application Service. This service runs the Microsoft Dynamics CRM web application that is used to connect users to CRM data. Deployment Web Service . Manages the deployment by using the methods described in the Microsoft Dynamics CRM 2011 Deployment Software Development Kit, such as create an organization or remove a Deployment Administrator role from a user. Sandbox Processing Service. Enables an isolated environment to allow for the execution of custom code, such as plug-ins. This isolated environment reduces the 32

possibility of custom code affecting the operation of the organizations in the Microsoft Dynamics CRM deployment. Asynchronous Processing Service. Processes queued asynchronous events, such as bulk e-mail or data import. Important We strongly recommend that you select a low-privilege domain account that is dedicated to running these services and is not used for any other purpose. Additionally, the user account that is used to run a Microsoft Dynamics CRM service cannot be a Microsoft Dynamics CRM user. This domain account must be a member of the Domain Users group. Additionally, if the Asynchronous Service and Sandbox Processing Service roles are installed, such as in a Full Server or a Back End Server installation, the domain account must a member of the Performance Log Users security group. If you select to run the ASP.NET service under a domain user account that is not a domain administrator or a local administrator, you must set a local security policy after you install Microsoft Dynamics CRM Server 2011 for the ASP.NET service to work correctly. Also, depending on the password policies that you have implemented for your organization, the password for the user may expire. For more information, see the Microsoft Knowledge Base (KB) article 329290, How to use the ASP.NET utility to encrypt credentials and session state connection strings. 14. On the Select a Web Site page, click Create a new Web site or click Select a Web Site and select a website from the list. By default, Setup will use the default website. Important We strongly recommend that you verify the status of the existing website before you specify Setup to use an existing website. We strongly recommend that the website you select is configured for SSL. For more information, see the IIS documentation. During the installation, Setup can bind the Microsoft Dynamics CRM application to the HTTPS website. If you select a network port other than a default port ensure that the firewall does not block the port. When you select the Create a new Web site option, Setup creates a new website for Microsoft Dynamics CRM Server 2011. You can specify the following option: Port Number. Type the TCP port number that Microsoft Dynamics CRM clients will use to connect to the Microsoft Dynamics CRM Server 2011. The default port 33

number is 5555. 15. Click Next. 16. On the Specify E-mail Router Settings page, in the E-mail Router server name box, type the name of the computer where the E-mail Router will be installed. This computer will route Microsoft Dynamics CRM e-mail messages. If you will not install the E-mail Router you can leave this box blank. However, if you install the E-mail Router later you must add the computer where the E-mail Router service is running when you use Local System, or if you use a domain user account, the account, to the PrivUserGroupP security group. Click Next. 17. On the Specify the Organization Name page, specify the following information. a. In the Display Name box, type the name of your organization. b. In the Name box, you can keep the name that is automatically generated or you can type a unique name that must be limited to 30 characters. Spaces and extended characters are not allowed. c. Under ISO currency code, click Browse, select the ISO currency code that you will use as the base currency for the organization in the list, and then click OK. You can change the currency's symbol, name, or precision. d. In the Base Language list, select the base language for the organization. In Microsoft Dynamics CRM 2011, only the base language of the first organization is tied to the language of the server installation. All other organizations can have different base languages, but you must first install Language Packs for the other language. For instructions about how to install Language Packs, see Microsoft Dynamics CRM 2011 Language Pack Installation Instructions in this guide. e. In the SQL collation list, keep the default selection or select a different database collation that the organization database will use to sort and compare data characters. The default SQL collation changes based on the base language selection. For more information, see SQL Server Collation Fundamentals. f. Click Next. Important After Setup is complete, you cannot change the database collation, base ISO currency code, or the organization unique name. However, you can change 34

the base currency name and base currency symbol. 18. On the Specify Reporting Services Server page, type the Report Server URL. Make sure that you use the Report Server URL, not the Report Manager URL. To verify that you are using the correct URL, in a browser, type the Report Server URL as the address. You should see a page titled <server>/ReportServer - /: with text that displays the version number: Microsoft SQL Server Reporting Services Version <version number>. Click Next. 19. On the Help Us Improve the Customer Experience page, select whether you want to participate in the Customer Experience Improvement Program, and then click Next. Note For more information, see Microsoft Customer Experience Improvement Program. 20. On the Select Microsoft Update OptIn page, you must select either of the following options. For more information about the legal terms and privacy with Microsoft Update licensing see Windows Update FAQ. Use Microsoft Update when I check for updates (recommended). By selecting this option, Microsoft Dynamics CRM Server will use the Microsoft Update settings on the computer. I dont want to use Microsoft update. You should only select this option if the computer uses another method to install updates such as by using Microsoft Windows Server Update Services (WSUS). 21. The System Checks page appears. This page is a summary of all requirements and recommendations for a successful installation. Errors must be resolved before installation can continue. If no errors, or only warnings appear, you can continue with the installation. To do this, click Next. 22. The Service Disruption Warning page appears. This page lists all services that will be stopped or restarted during Setup. 23. Review the Ready to Install Microsoft Dynamics CRM page, and then click Back to correct any warnings. When you are ready to continue, click Install. When Setup completes successfully, the Microsoft Dynamics CRM Server setup completed page appears. If the Reporting Server instance that you specified during this Setup points to the local computer where Microsoft Dynamics CRM is installed, Setup provides an option to invoke Microsoft Dynamics CRM Reporting Extensions Setup. 24. To install Microsoft Dynamics CRM Reporting Extensions on the computer now, select the Launch Microsoft Dynamics CRM Reporting Extensions Setup check box. Click Finish. 35

Important After you install Microsoft Dynamics CRM Server 2011, you must install the Microsoft Dynamics CRM Reporting Extensions to create, run, and schedule reports in Microsoft Dynamics CRM. For instructions, see Install Microsoft Dynamics CRM Reporting Extensions in this guide. You cannot install the Microsoft Dynamics CRM Reporting Extensions before you install or upgrade Microsoft Dynamics CRM Server 2011. By default, Setup turns on HTTP compression on the server that is running IIS where the Microsoft Dynamics CRM web application is installed. If you use another method to compress HTTP communications, you may want to turn this feature off. To do this, start Internet Services (IIS) Manager, click the Web site, double-click Compression, and then clear the compression check boxes. For an IFD deployment, after Microsoft Dynamics CRM Server Setup completes, you must configure claims-based authentication and the relying parties on the STS server. Then, run the Internet-Facing Deployment Configuration Wizard to complete the configuration. For more information about this configuration see Microsoft Dynamics CRM 2011 Post-Installation and Configuration Guidelines in this guide.

See Also
Microsoft Dynamics CRM Server 2011 installation Install Microsoft Dynamics CRM Reporting Extensions

Install Microsoft Dynamics CRM Reporting Extensions

Applies to: Microsoft Dynamics CRM 2011 Microsoft Dynamics CRM Reporting Extensions has the following requirements: You must complete Microsoft Dynamics CRM Server Setup before you run CRM Reporting Extensions Setup. You must run Microsoft Dynamics CRM Reporting Extensions Setup on a computer that has a supported version of Microsoft SQL Server Reporting Services installed. For more information, see Microsoft Dynamics CRM 2011 Reporting Extensions requirements. Warning 36

Microsoft Dynamics CRM users who use the Report Viewer control included with Microsoft Visual Studio 2008 can view information from the reports that they have access to. By using this control, the user can view additional report and session data that is not displayed when running the report in Microsoft Dynamics CRM. To reduce the risk of exposing confidential data, we recommend that you configure the Microsoft SQL Server Reporting Services website where the Microsoft Dynamics CRM Reporting Extensions is installed to allow only Secure Sockets Layer (SSL), also known as Secure HTTP, connections. For more information, see Configuring a Report Server for Secure Sockets Layer (SSL) Connections. To reduce the risk of certain security vulnerabilities, we strongly recommend that you use different Active Directory accounts for the application pools used to run the Microsoft Dynamics CRM Server 2011 and Microsoft SQL Server Reporting Services websites. Important Installing on Windows Server 2012 If you are installing Microsoft Dynamics CRM Reporting Extensions on Windows Server 2012 you must download the latest Setup update and apply Microsoft Dynamics CRM 2011 Update Rollup 13 after Setup is finished. For more information, see Microsoft Dynamics CRM 2011 Reporting Extensions requirements.

To install the CRM Reporting Extensions, locate the Microsoft Dynamics CRM installation files, and follow these steps: 1. In the ..\Server\amd64\SrsDataConnector folder, double-click SetupSrsDataConnector.exe. 2. On the Welcome to Microsoft Dynamics CRM Reporting Extensions Setup page, select whether you want to update Microsoft Dynamics CRM Server Setup. We recommend that, if updates are available, you let Setup download the latest version. To do this, click Update installation files, wait until the update process is complete, and then click Next. 3. On the License Agreement page, review the information and, if you accept the license agreement, click I accept this license agreement, and then click I Accept. 4. If Setup detects that components are missing, the Install Required Components page appears.

37

a. If you have already installed the required components, this page will not appear. b. If you have not installed the required components listed, you can install them now. Click Install. When the components are installed, the status column will change from Missing to Installed, and you can click Next to continue. 5. On the Specify Configuration Database Server page, if you are using the default instance of the SQL Server, enter the name of the computer that is running SQL Server and contains the Microsoft Dynamics CRM configuration database that is named MSCRM_CONFIG, and then click Next. Note If you are not using the default SQL Server instance, enter <machinename>\<instance-name>. 6. On the Specify SSRS Instance Name page, select a Microsoft SQL Server Reporting Services instance that will be used for Microsoft Dynamics CRM reporting, and then click Next. 7. On the Select Microsoft Update OptIn page, select whether you want to use Microsoft Update for checking for updates for your Microsoft products, and click Next. We recommend that you use the Microsoft Update to check for updates because this keeps your computer up-to-date and secure. 8. On the Select Installation Location page, click Browse, and select a path where you want to install CRM Reporting Extensions, and then click Next. 9. The System Checks page appears. This page is a summary of the requirements for a successful CRM Reporting Extensions installation. Errors must be corrected before installation can continue. All errors must be resolved. If no errors or only warnings appear, you can continue with the installation. To do this, click Next. 10. Review the Ready to Install Microsoft Dynamics CRM Reporting Extensions page, and then click Back to correct any errors. When you are ready to continue, click Install. 11. When Setup completes successfully, the Microsoft Dynamics CRM Reporting Extensions Setup Completed page appears. Click Finish. The reports will be published for the default organization. Important The reports will not be published if: The user running CRM Reporting Extensions Setup does not have appropriate permissions on the organization database. CRM Reporting Extensions are installed for an Microsoft SQL Server Reporting 38

Services instance that is different from the one that is being used by the organization. The base language of the organization is different from the language in which CRM Reporting Extensions are being installed.

See Also
Microsoft Dynamics CRM Server 2011 installation Microsoft Dynamics CRM Report Authoring Extension Installation Instructions

Microsoft Dynamics CRM Report Authoring Extension Installation Instructions

If not already installed, the following components are installed during Microsoft Dynamics CRM Report Authoring Extension Setup: Microsoft Application Error Reporting Tool Windows Live ID Sign-in Assistant 6.5 Important If your organization uses Microsoft Office 365, the computer on which the Microsoft Dynamics CRM Report Authoring Extension is installed must have the Microsoft Online Services Sign-in Assistant installed on it. If Microsoft Online Services Sign-in Assistant is already installed, check the registry key SOFTWARE\Microsoft\MSOIdentityCRL and make sure that the TargetDir registry key in MSOIdentityCRL contains msoidcli.dll.

Microsoft Dynamics CRM Report Authoring Extension Installation Instructions Microsoft Dynamics CRM Report Authoring Extension is a plug-in that obtains the metadata and data from Microsoft Dynamics CRM. This metadata is required to design and preview Fetchbased reports in Business Intelligence Development Studio. Important 39

Installing on Windows Server 2012 If you are installing Microsoft Dynamics CRM Report Authoring Extension on Windows Server 2012 you must install Microsoft Dynamics CRM Report Authoring Extension using the version that includes Microsoft Dynamics CRM 2011 Update Rollup 13 that is currently available on the Microsoft Download Center. Download the Microsoft Dynamics CRM 2011 Report Authoring Extension. For more information, see Microsoft Dynamics CRM 2011 Reporting Extensions requirements.

1. In the /BIDSExtensions/ folder, double-click SetupBIDSExtensions.exe. 2. On the Welcome to Microsoft Dynamics CRM Report Authoring Extension Setup page, we recommend that you click Get updates for Microsoft Dynamics CRM, to make sure that Setup has the most recent installation files. Click Next. 3. On the License Agreement page, review the information, and if you accept the license agreement, select the I accept this license agreement check box, and then click I Accept. 4. If Setup detects that some required components are missing, the Install Required Components page appears. To install them, click Install. When the components are installed, the status column will change from Not Installed to Installed. Click Next to continue. 5. On the Select Microsoft Update Preference page, we recommend that you select the Use Microsoft Update when I check for updates (recommended) option. Microsoft Update makes sure that your computer has the latest technology, which can help to reduce the risk of vulnerabilities and security issues. 6. On the Select Installation Location page, accept the default location or enter a different file installation location, and then click Next. 7. On the System Checks page, a summary of all requirements and recommendations for a successful installation is shown. Errors must be corrected before installation can continue. If no errors, or only warnings appear, you can continue with the installation. To do this, click Next. 8. Review the Ready to Install Microsoft Dynamics CRM Report Authoring Extension page, and then click Back to correct any errors. When you are ready to continue, click Install. When Setup successfully completes, the Microsoft Dynamics CRM Report Authoring Extension Setup Completed page appears. Click Finish. 40

See Also
Download: Microsoft Online Services Sign-In Assistant for IT Professionals RTW Microsoft Dynamics CRM Server 2011 installation Upgrade from Microsoft Dynamics CRM 4.0

Upgrade from Microsoft Dynamics CRM 4.0

This section provides best practice guidelines and actual procedures to install Microsoft Dynamics CRM Server 2011 in an organization that already has Microsoft Dynamics CRM 4.0 installed.

Upgrade options
There are three different upgrade options: Migrate by using a new instance of SQL Server. We recommend this option for upgrading from Microsoft Dynamics CRM 4.0 to Microsoft Dynamics CRM 2011. Although this option requires a different computer for Microsoft Dynamics CRM Server 2011 and a different instance of SQL Server, it provides the least amount of potential downtime for Microsoft Dynamics CRM since the Microsoft Dynamics CRM 4.0 deployment can remain functioning until the upgrade is completed and verified. Migrate by using the same instance of SQL Server. This option requires a different computer for Microsoft Dynamics CRM Server 2011, but will upgrade in-place the configuration and default organization databases using the same instance of SQL Server. If issues occur during the upgrade, you must roll back to Microsoft Dynamics CRM 4.0 to avoid significant downtime. In-place upgrade. Although this option does not require a different computer for Microsoft Dynamics CRM Server 2011 or a different instance of SQL Server, it poses the greatest risk if upgrade issues occur because a roll back and reinstall of Microsoft Dynamics CRM 4.0 Server will be required to avoid potential downtime. Important You cannot upgrade versions of Microsoft Dynamics CRM that are earlier than Microsoft Dynamics CRM 4.0 to Microsoft Dynamics CRM 2011. Because Microsoft Dynamics CRM Server 2011 is only available in 64-bit editions, you cannot perform an in-place upgrade with 32-bit versions of Microsoft Dynamics CRM 4.0

41

Server. For more information, see Migrate from 32-bit versions of Microsoft Dynamics CRM 4.0 Server to Microsoft Dynamics CRM 2011 Server in this guide.

See Also
Microsoft Dynamics CRM Server 2011 Installation Instructions Microsoft Dynamics CRM Server 2011 upgrade preparations

Microsoft Dynamics CRM Server 2011 upgrade preparations

To prepare a Microsoft Dynamics CRM Server 2011 for the upgrade, follow the guidelines in this section. Microsoft Dynamics CRM 4.0 server roles are not compatible with a Microsoft Dynamics CRM deployment. Therefore, after you upgrade the first Microsoft Dynamics CRM 4.0 server, other Microsoft Dynamics CRM 4.0 servers that are running in the deployment will become disabled. As each server is upgraded, the corresponding server will be enabled. Important We recommend that for each organization that you upgrade, the volume have free space that is at least three times the size of the organization database file and four times the size of the log file. Therefore, if a single organization database and log file are located on the same volume and are one gigabyte in total, you should have at least seven gigabytes of available disk space before you perform the upgrade.

Software prerequisites
We recommend that you install the following components on the Microsoft Dynamics CRM Server 2011 or the computer where Microsoft Dynamics CRM 4.0 will be migrated to before you run the upgrade: Windows Identity Foundation (WIF) Framework Microsoft .NET Framework 4 SQL Server Native Client Microsoft Application Error Reporting Tool 42

 Microsoft URL Rewrite Module for IIS If these components are not present when you run the upgrade, Setup will install them. However, to reduce the upgrade processing time, consider installing these components in advance. These components can be found in the redist folder of the Microsoft Dynamics CRM installation media.

See Also
Upgrade from Microsoft Dynamics CRM 4.0 Upgrade from Microsoft Dynamics CRM 4.0 Server 64-bit editions

Upgrade from Microsoft Dynamics CRM 4.0 Server 64-bit editions

This section outlines the tasks that you must perform to run the actual in-place upgrade on a Microsoft Dynamics CRM server. If you encounter problems during the upgrade, see Troubleshooting installation and upgrade in this guide. Warning Following these steps may cause significant application downtime if issues occur during the upgrade. Instead of using an upgrade option that may impact the production deployment, we recommend that you migrate your deployment to Microsoft Dynamics CRM 2011. For more information, see Migrate from 32-bit versions of Microsoft Dynamics CRM 4.0 Server to Microsoft Dynamics CRM 2011 Server in Upgrade from Microsoft Dynamics CRM 4.0 Server 32-bit editions in this guide. Important We strongly recommend that you back up your existing Microsoft Dynamics CRM data, including all reports and customizations, before you run Setup to upgrade your system. In addition, we recommend the following backup strategy be implemented before you run Setup: 1. Configure the Microsoft Dynamics CRM 4.0 databases by using a simple recovery model. 2. Complete a full backup of all production configuration and organization databases and transaction logs.

43

For more information, see Backing Up the Microsoft Dynamics CRM System in the Operating and Maintaining Guide. Important If the Microsoft Dynamics CRM 4.0 deployment is configured for an Internet-facing deployment (IFD), after the upgrade is complete you must run the Configure Claims-Based Authentication Wizard and then the Internet-Facing Deployment Configuration Wizard to reenable IFD. For more information about claims-based authentication and IFD, see the Microsoft Dynamics CRM 2011 Planning Guide and Deployment Manager Help. The user who is running Microsoft Dynamics CRM Server Setup to upgrade an existing Microsoft Dynamics CRM deployment must be a member of the Deployment Administrators group. Additionally, the user must have db_owner permission on the Microsoft Dynamics CRM 4.0 databases and have sysadmin permission on the SQL Server. For more information about how to add a member to the Deployment Administrators group see the Deployment Manager Help. For more information about how to grant permission in SQL Server, see the SQL Server Management Studio Help.

Tasks to perform before the upgrade

We recommend that you apply the Latest Update Rollup for Microsoft Dynamics CRM 4.0. Meet all requirements as specified under Microsoft Dynamics CRM 2011 System Requirements and Required Components in the Planning Guide. Log on to your domain as a user who has administrator-level permission. SQL Server replication is not supported with Microsoft Dynamics CRM. If you run SQL Server replication, disable it. Make sure that the Microsoft Dynamics CRM server that you are upgrading is connected to the Internet. If you do not have Internet access on that server, see KB article: How to obtain the setup updates for Microsoft Dynamics CRM 2011. Uninstall Microsoft Dynamics CRM 4.0 Connector for SQL Server Reporting Services if it is installed on the same computer where Microsoft Dynamics CRM Server 2011 is installed. See the Microsoft Dynamics CRM 2011 and Microsoft Dynamics CRM Online Readme to determine the location of the Microsoft Dynamics CRM installation files.

To run the upgrade, follow these steps

1. In the folder where the Microsoft Dynamics CRM files are located, move to the 44

Server\amd64 folder, and then double-click SetupServer.exe. 2. On the Welcome to Microsoft Dynamics CRM Setup page, we recommend that you click Get updates for Microsoft Dynamics CRM, to make sure that Setup has the most recent installation files. Click Next. 3. On the Product Key Information page, type your product key in the Product key boxes, and then click Next. Note If you purchased Microsoft Dynamics CRM through a Microsoft Volume Licensing program, the license key is provided in the license.txt file, which is included in the Microsoft Dynamics CRM installation files. 4. On the License Agreement page, review the information and if you accept the license agreement, click I accept this license agreement, and then click I Accept. 5. If Setup detects that components are missing, the Install Required Components page appears. If you have already installed the required components, this page will not appear. If you have not installed the required components listed, you can install them now. Click Install. When the components are installed, the status column will change from Not Installed to Installed, and you can click Next to continue. Note If you are prompted to restart the computer, do so, and then start Setup again. 6. On the Upgrade to Microsoft Dynamics CRM 2011 page, click Next to upgrade Microsoft Dynamics CRM. 7. On the Specify E-mail Router Settings page, in the E-mail Router server name box, type the name of the computer where the E-mail Router will be installed. This computer will route Microsoft Dynamics CRM e-mail messages. If you will not install the E-mail Router you can leave this box blank. However, if you install the E-mail Router later you must add the computer where the E-mail Router service is running when you use Local System, or if you use a domain user account, the account, to the PrivUserGroup security group. Click Next. 8. On the Organization Upgrade page, verify the display name and unique name of the organization, and then click Next. 9. On the Select Microsoft Update OptIn page, you must select either of the following options. For more information about the legal terms and privacy with Microsoft Update licensing see Windows Update FAQ. 45

 Use Microsoft Update when I check for updates (recommended). By selecting this option, Microsoft Dynamics CRM Server 2011 will use the Microsoft Update settings on the computer. I dont want to use Microsoft update. You should only select this option if the computer uses another method to install updates such as by using Microsoft Windows Server Update Services (WSUS). 10. The System Checks page appears. This page is a summary of all requirements and recommendations for a successful installation. Errors must be resolved before installation can continue. If no errors, or only warnings appear, you can continue with the installation. To do this, click Next. 11. The Service Disruption Warning page appears. This page lists all services that will be stopped or restarted during Setup. 12. Review the Ready to Upgrade the Application page, click Back to correct any errors. When you are ready to continue, click Upgrade. When Setup completes successfully, the Microsoft Dynamics CRM Server Setup completed page appears. If the Reporting Server instance that you specified during this Setup points to the local computer where Microsoft Dynamics CRM is installed, Setup provides an option to invoke Microsoft Dynamics CRM Reporting Extensions Setup. 13. To install Microsoft Dynamics CRM Reporting Extensions on the computer now, select the Launch Microsoft Dynamics CRM Reporting Extensions Setup check box. Click Finish. Important After you install Microsoft Dynamics CRM Server 2011, you must install the Microsoft Dynamics CRM Reporting Extensions to create, run, and schedule reports in Microsoft Dynamics CRM. For instructions, see Install Microsoft Dynamics CRM Reporting Extensions in this guide. You cannot install the Microsoft Dynamics CRM Reporting Extensions before you install or upgrade Microsoft Dynamics CRM Server 2011. By default, Setup turns on HTTP compression on the server that is running IIS where the Microsoft Dynamics CRM web application is installed. If you use another method to compress HTTP communications, you may want to turn this feature off. To do this, start Internet Services (IIS) Manager, click the Web site, double-click Compression, and then clear the compression check boxes. For an IFD deployment, after Microsoft Dynamics CRM Server Setup completes, you must configure claims-based authentication and the relying parties on the STS server. Then, run the Internet-Facing Deployment Configuration Wizard to complete the configuration. For 46

more information about this configuration see Microsoft Dynamics CRM 2011 Post-Installation and Configuration Guidelines in this guide.

See Also
Microsoft Dynamics CRM Server 2011 upgrade preparations Upgrade from Microsoft Dynamics CRM 4.0 Server 32-bit editions

Upgrade from Microsoft Dynamics CRM 4.0 Server 32-bit editions

This section outlines the tasks that you must perform to migrate Microsoft Dynamics CRM 4.0 Server to Microsoft Dynamics CRM Server 2011. Because Microsoft Dynamics CRM Server 2011 is available only for 64-bit editions of Windows Server, in-place upgrades from 32-bit versions of Microsoft Dynamics CRM 4.0 Server cannot be performed. Important To avoid potential downtime that may occur as a result of a direct upgrade of a production deployment, we recommend that you consider implementing the migration by using a new instance of SQL Server upgrade option described in the following Migrate from 32-bit versions of Microsoft Dynamics CRM 4.0 Server to Microsoft Dynamics CRM 2011 Server topic instead of an in-place upgrade.

Migrate from 32-bit versions of Microsoft Dynamics CRM 4.0 Server to Microsoft Dynamics CRM 2011 Server
To migrate a 32-bit version of Microsoft Dynamics CRM 4.0 Server to Microsoft Dynamics CRM Server 2011, first establish a different instance of SQL Server, run Microsoft SQL Server Setup on a new 64-bit computer to create a new Microsoft Dynamics CRM 2011 deployment, and then run the Import Organization Wizard to import one or more Microsoft Dynamics CRM 4.0 organizations to the newly installed Microsoft Dynamics CRM 2011 system. During the import the Microsoft Dynamics CRM 4.0 organization database will be upgraded.

47

Migrate by using a new instance of SQL Server

This procedure is useful when the Microsoft Dynamics CRM 4.0 deployment needs to remain available while Microsoft Dynamics CRM Server 2011 is installed (phase 1). Then, the Microsoft Dynamics CRM 4.0 deployment can be taken offline while the organization database is imported and upgraded into the new Microsoft Dynamics CRM 2011 deployment (phase 2). 1. If the configuration (MSCRM_CONFIG) and organization databases were maintained by a version of SQL Server that is not Microsoft SQL Server 2008 64-bit edition, upgrade the server or restore the databases to a supported version of SQL Server. 2. Install Microsoft Dynamics CRM Server 2011 as if it were a new server or server role without a preexisting version. During the installation Microsoft Dynamics CRM Server Setup creates a new Microsoft Dynamics CRM 2011 configuration database. For step-by-step guidance, see Install Microsoft Dynamics CRM 2011 Server on a server without Microsoft Dynamics CRM installed in this guide. 3. After the installation completes, disable the Microsoft Dynamics CRM 4.0 deployment by running Deployment Manager on the Microsoft Dynamics CRM 4.0 server. For more information, see the Deployment Manager Help. 4. On the SQL Server that is maintaining the existing Microsoft Dynamics CRM 4.0 databases, start SQL Server Management Studio and back up the MSCRM_CONFIG and OrganizationName_MSCRM databases. 5. Restore the organization databases to the SQL Server that will be maintaining the Microsoft Dynamics CRM 2011 databases. Important Do not change the organization database name before the migration is completed. If you must rename the database, complete the import and upgrade procedure that is described here, then delete the organization by using Deployment Manager, and then import the organization again. During the import you can change the organization database name. 6. Start Deployment Manager on the Microsoft Dynamics CRM Server 2011 and run the Import Organization Wizard to import and upgrade one or more Microsoft Dynamics CRM 4.0 organizations into the new Microsoft Dynamics CRM 2011 deployment. 7. Verify that the new deployment functions as expected. 8. Make the appropriate DNS and IIS modifications to make sure users are able to connect to the new system.

48

If issues occur that will cause significant downtime, enable the Microsoft Dynamics CRM 4.0 deployment while the issues are worked on. For more information, see the Deployment Manager Help.

Migrate by using the same instance of SQL Server

If you are migrating Microsoft Dynamics CRM 4.0 32-bit to a new Windows Server 64-bit server that will be running Microsoft Dynamics CRM 2011 and you want to use the same instance of SQL Server that maintains the configuration database, follow these steps: Warning Following these steps may cause significant application downtime if issues occur during the upgrade. Instead of using an upgrade option that may impact the production deployment, we recommend that you migrate your deployment to Microsoft Dynamics CRM 2011. For more information, see Migrate from 32-bit versions of Microsoft Dynamics CRM 4.0 Server to Microsoft Dynamics CRM 2011 Server above. 1. If the configuration (MSCRM_CONFIG) and organization databases were maintained by a version of SQL Server that is not Microsoft SQL Server 2008 64-bit edition, upgrade the server or restore the databases to a supported version of SQL Server. 2. On the SQL Server that is maintaining the existing Microsoft Dynamics CRM 4.0 databases, start SQL Server Management Studio and back up the MSCRM_CONFIG and OrganizationName_MSCRM databases. 3. Install Microsoft Dynamics CRM Server 2011 on the new 64-bit computer. During Microsoft Dynamics CRM Server Setup, select Connect to, and if necessary, upgrade an existing deployment on the Specify Deployment Options page during Microsoft Dynamics CRM Server Setup. Specify the SQL Server instance from the previous step and continue with the installation and organization upgrade. For guidance, see Install Microsoft Dynamics CRM 2011 Server on a server without Microsoft Dynamics CRM installed in this guide. 4. If you have additional organizations or if you are using a new SQL Server for the migration, you must import the organization databases to the new system. To do this, on the computer where Microsoft Dynamics CRM Server 2011 is installed and running, start Deployment Manager, right-click Organizations, click Import Organization, and then select the newly restored Microsoft Dynamics CRM 4.0 OrganizationName_MSCRM database. 5. If customizations were made to .NET assemblies or configuration files, you must copy those customized files to the new system. By default, these files are located under the <drive>:\Program Files\Microsoft Dynamics CRM\Server\bin\assembly\ folder on the existing Microsoft Dynamics CRM 4.0 server.

49

See Also
Upgrade from Microsoft Dynamics CRM 4.0 Server 64-bit editions Migrate from Microsoft Dynamics CRM 3.0 Server to Microsoft Dynamics CRM 2011 Server

Migrate from Microsoft Dynamics CRM 3.0 Server to Microsoft Dynamics CRM 2011 Server
In-place upgrade from versions of Microsoft Dynamics CRM 3.0 is not available. However, you can migrate your Microsoft Dynamics CRM 3.0 deployment to Microsoft Dynamics CRM 2011 by using a Microsoft Dynamics CRM 4.0 trial version as an interim step in the migration process. To migrate your 32-bit version of Microsoft Dynamics CRM 3.0 Server toMicrosoft Dynamics CRM Server 2011, perform the following tasks. Important Microsoft Dynamics CRM 4.0 Server and Microsoft Dynamics CRM Server 2011 have different component requirements than Microsoft Dynamics CRM 3.0 Server. Therefore, you must make sure that your hardware and software environment will support the migration. For more information about the hardware and software requirements for Microsoft Dynamics CRM 4.0, see the Microsoft Dynamics CRM 4.0 Implementation Guide. For more information about Microsoft Dynamics CRM 2011 hardware and software requirements, see Microsoft Dynamics CRM 2011 System Requirements and Required Components in the Planning Guide. 1. Upgrade to Microsoft Dynamics CRM 4.0 Server by downloading and installing the Microsoft Dynamics CRM 4.0 90-day trial versions available on the Microsoft Download Center. Or, you can migrate your Microsoft Dynamics CRM 3.0 organization to a trial 64-bit version of Microsoft Dynamics CRM 4.0. Important Trial versions of Microsoft Dynamics CRM 4.0 can be used within a 90-day period before you must enter a valid commercial product key to continue use. To make sure the latest updates to the Setup program are applied that help ease upgrading to Microsoft Dynamics CRM 2011, we strongly recommend that you click Get updates for Microsoft Dynamics CRM during the installation or upgrade to Microsoft Dynamics CRM 4.0.

50

2. Migrate the newly installed Microsoft Dynamics CRM 4.0 trial version by following the steps in the previous topic. Or, if you migrated your Microsoft Dynamics CRM 3.0 organization to a 64-bit version of Microsoft Dynamics CRM 4.0, you can perform an in-place upgrade of Microsoft Dynamics CRM Server 2011. 3. Install Microsoft Dynamics CRM Reporting Extensions. 4. Install additional components, such Microsoft Dynamics CRM 2011 E-mail Router, as necessary.

See Also
Upgrade from Microsoft Dynamics CRM 4.0 Server 32-bit editions Upgrade Microsoft Dynamics CRM Connector for SQL Server Reporting Services

Upgrade Microsoft Dynamics CRM Connector for SQL Server Reporting Services
In-place upgrade of the Microsoft Dynamics CRM 4.0 Connector for SQL Server Reporting Services is not supported. If Microsoft Dynamics CRM 4.0 Connector for SQL Server Reporting Services is already installed, you must first uninstall it and then run Microsoft Dynamics CRM Reporting Extensions Setup. 1. Uninstall Microsoft Dynamics CRM 4.0 Connector for SQL Server Reporting Services. 2. Meet all requirements as specified under Microsoft Dynamics CRM 2011 System Requirements and Required Components in the Planning Guide. 3. Upgrade from Microsoft Dynamics CRM 4.0 to Microsoft Dynamics CRM 2011. 4. At the computer where Microsoft Dynamics CRM 4.0 Connector for SQL Server Reporting Services was installed, log on to your domain as a user who has administrator-level privileges. 5. See the Readme file to review important information and determine the location of the Microsoft Dynamics CRM Reporting Extensions installation files. 6. In the ..\Server\amd64\SrsDataConnector folder, double-click SetupSrsDataConnector.exe. 7. Follow the instructions on the screen or see Install Microsoft Dynamics CRM Reporting Extensions in this guide.

51

See Also
Migrate from Microsoft Dynamics CRM 3.0 Server to Microsoft Dynamics CRM 2011 Server After the upgrade

After the upgrade

After Setup has upgraded the Microsoft Dynamics CRM Server 2011, perform the following tasks.

Post-upgrade steps for servers

For each of your Microsoft Dynamics CRM Server 2011 deployments, follow these steps: 1. If you have additional servers, upgrade or uninstall and reinstall Microsoft Dynamics CRM on those servers as described in Install Microsoft Dynamics CRM Server 2011 on multiple computers in this guide. 2. Install the Microsoft Dynamics CRM Reporting Extensions for SQL ServerReporting Services. If you are migrating to Microsoft Dynamics CRM 2011, you must install Microsoft Dynamics CRM Reporting Extensions for SQL ServerReporting Services before you can import and upgrade a Microsoft Dynamics CRM 4.0 organization. 3. Install the latest Microsoft Dynamics CRM 2011 update rollup package or server hotfixes. 4. In Microsoft SQL Server Reporting Services Report Manager, re-create any custom data sources under the OrganizationName_MSCRM folders. 5. Verify that the system jobs and workflows are running. 6. Although not required, we recommend that you register Microsoft Dynamics CRM.

Verify intranet Web addresses for in-place or connect to existing deployment upgrades
During an in-place upgrade or connect to existing deployment upgrade, Microsoft Dynamics CRM Server Setup may overwrite the Web addresses (AD root domain) that exist in the Microsoft Dynamics CRM 4.0. The issue occurs when the first local computer that is running Microsoft Dynamics CRM 4.0 Server is upgraded. If the Web addresses are not using the name of

52

the local computer, the change to the address may not be desired and can cause unexpected results. To work around this potential issue, verify that the intranet Web addresses are correct. For more information about how to view or change the Web addresses, see the Deployment Manager Help. This issue will not occur when you perform a migration upgrade. For more information about migration upgrades, see Upgrade from Microsoft Dynamics CRM 4.0 Server 32-bit editions in this guide.

Post-upgrade steps for clients

To be compatible with Microsoft Dynamics CRM Server 2011, Microsoft Dynamics CRM 4.0 for Outlook clients must be upgraded to Update Rollup 7 or later. However, to experience the new features that are available with Microsoft Dynamics CRM 2011 you must upgrade to Microsoft Dynamics CRM 2011 for Outlook.

To upgrade clients, follow these steps: 1. If you use Microsoft Dynamics CRM for Outlook or Microsoft Dynamics CRM for Outlook with Offline Access, run Microsoft Dynamics CRM 2011 for Outlook Setup on every user's computer. To ease the upgrade use Microsoft System Center Configuration Manager 2007 or Microsoft Group Policy to push the upgrade to users. See the Microsoft Dynamics CRM 2011 Planning Guide for information about how to deploy Microsoft Dynamics CRM 2011 for Outlook using these methods. 2. Verify that Microsoft Dynamics CRM for Outlook and Microsoft Dynamics CRM for Outlook with Offline Access have the latest updates. 3. Test the functionality from Microsoft Outlook and from the Microsoft Dynamics CRM web application. For more information, see Upgrade Microsoft Dynamics CRM 4.0 for Outlook to Microsoft Dynamics CRM 2011 for Outlook in this guide.

See Also
Upgrade from Microsoft Dynamics CRM 4.0 Troubleshooting installation and upgrade

53

Troubleshooting installation and upgrade

This section describes how to troubleshoot installation and known issues.

Log files
Setup creates log files that can be reviewed and used for troubleshooting. By default, the location of the log files, where User is the account of the user who ran Setup, is as follows: SystemDrive:\Users\User\AppData\Roaming\Microsoft\MSCRM\Logs\

See Also
Upgrade from Microsoft Dynamics CRM 4.0 Server installation and upgrade issues

Server installation and upgrade issues

This section describes how to troubleshoot Microsoft Dynamics CRM Server 2011 installation issues.

In This Topic
Timeout expired error message during organization upgrade Clients cannot connect to Microsoft Dynamics CRM Web application Microsoft Dynamics CRM Server 2011 cannot connect to Microsoft SQL Server Troubleshooting WIF installation failures Claims-based authentication issues 'Login failed for DomainName\ServerName$" error message after Microsoft Dynamics CRM Server 2011 install, repair, or configure

Timeout expired error message during organization upgrade

During an organization database upgrade, you may receive the error message: 54

InstallDatabaseAction failed. ---> System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

To work around this issue, add the OLEDBTimeout and the ExtendedTimeout registry subkeys to increase the time-out values. For more information, see A time-out occurs when you import large
customization files into Microsoft Dynamics CRM

Clients cannot connect to Microsoft Dynamics CRM Web application

Clients may be unable to connect to the Microsoft Dynamics CRM web application. This issue can occur when the following conditions are true: The Microsoft Dynamics CRM web application is configured for a TCP port that is not the default port (80), such as 5555. Windows Firewall does not include an exception for the TCP port. To resolve this issue, add the port as an exception in the firewall configuration on the server where Microsoft Dynamics CRM is installed.

Microsoft Dynamics CRM Server 2011 cannot connect to Microsoft SQL Server
This issue can occur when Windows Firewall does not include an exception for the TCP port used by Microsoft SQL Server. By default, the TCP port used by Microsoft SQL Server is 1433. For more information, see Configuring the Windows Firewall to Allow SQL Server Access.

Troubleshooting WIF installation failures

To help resolve issues that may occur when you install Windows Identity Framework (WIF), start Event Viewer and locate the Setup folder under Windows Logs. Filter on the source WUSA.

Claims-based authentication issues

Verify the certificate that you are using is valid for the associated Web site. Open the certificate and view the name. A wildcard certificate (for example, *.contoso.com) can authenticate all subdomains in the contoso.com domain. You can also use a Subject Alternative Names certificate or an individual certificate (for example, auth.domain.com:5555). 55

'Login failed for DomainName\ServerName$" error message after Microsoft Dynamics CRM Server 2011 install, repair, or configure
You may receive this error message when you try to sign-in to Microsoft Dynamics CRM after you install, upgrade, repair, or configure Microsoft Dynamics CRM Server 2011. This issue occurs when the following conditions are true: The server where you perform the installation, upgrade, repair, or configure action is located in a domain that is operating at a Windows Server 2003 domain functional level. One or more Microsoft Dynamics CRM service accounts are configured to use Network Service. To work around this issue, restart the server where Microsoft Dynamics CRM Server 2011 is installed.

See Also
Troubleshooting installation and upgrade Install Microsoft Dynamics CRM Server 2011 on multiple computers

Install Microsoft Dynamics CRM Server 2011 on multiple computers

You can install Microsoft Dynamics CRM Server 2011 on multiple computers to balance the processing load across several servers. Deploying Microsoft Dynamics CRM Server 2011 in this manner can increase performance and availability. Important Installing the Microsoft Dynamics CRM Workgroup Server 2011 edition on multiple servers is not supported and is a violation of the license agreement.

In This Topic
Multiple-server configuration overview Step 1: Enable network load balancing

56

Step 2: Configure Active Directory Step 3: Install Microsoft Dynamics CRM servers Step 4: Configure NLB for the deployment Step 5: Verify and monitor the cluster installation

Multiple-server configuration overview

Before getting started with load balancing, installation and configuration planning is needed. For more information, see the Microsoft Dynamics CRM 2011 Planning Guide. The base configuration typically uses separate computers that run the components of a Microsoft Dynamics CRM deployment that includes Microsoft SQL Server and an instance of Windows Server functioning as an Active Directory domain controller. A multiple-server configuration of Microsoft Dynamics CRM has multiple computers that are running Microsoft Dynamics CRM that access a single server that is running SQL Server. This topic describes the steps to install Microsoft Dynamics CRM in a two-node network loadbalancing configuration where all Microsoft Dynamics CRM Server 2011 roles are installed on a single computer. This kind of deployment is called a Full Server installation. You can use similar steps to install a particular server group role, such as the Front End Server role group, or one or more specific server roles. When you install Microsoft Dynamics CRM, you have the following choices for load balancing the Microsoft Dynamics CRM web application, where both servers in the network load-balancing (NLB) cluster must have the following server-group roles or individual server roles installed. 1. Full Server install. 2. Front End Server install. 3. Server role install (by using Microsoft Dynamics CRM Server Setup Wizard or command-line install with an XML configuration file). You will have to install at least the following two roles on the load-balanced servers in the cluster. Web Application Server role). This Microsoft Dynamics CRM Server 2011 role is used to run the Web application components that are used to connect users to Microsoft Dynamics CRM data. Organization Web Service role. This Microsoft Dynamics CRM Server 2011 role is used to run applications that use the methods described in the Microsoft Dynamics CRM SDK. Important 57

If you decide to install only the Front End Server role group, you must install the Back End Server group role on another server in the Active Directory domain for Microsoft Dynamics CRM to function. Similarly, if you want to install only the required Web Application Server and Organization Web Service roles, you must install the remaining server roles on other servers in the Active Directory domain for Microsoft Dynamics CRM to function. In this example, a two-node cluster will be set up by using two computers that are running Windows Server 2008. The server names are CRM01 and CRM02.

Step 1: Enable network load balancing

Enable NLB on the network and create a server cluster for servers CRM01 and CRM02. We recommend that you use the following port-rule settings when you enable the load-balanced cluster. Port range. Leave the default range, which is from 0 to 65535. Protocols. Both Affinity. Single For information about procedures for loading and administering NLB on Windows Server, see the Network Load Balancing Manager Help on the Windows Server computer. For information about how to configure NLB in Windows Server 2008, see Network Load Balancing Deployment Guide.

Step 2: Configure Active Directory

Configure Active Directory by creating an account to run the CRMAppPool service and use a Service Principal Name (SPN). This is required when you run IIS 7.0 in a clustered or a network load-balanced environment. The SPN uniquely identifies an instance of a running service. Active Directory uses the SPN for mutual authentication of a service instance, which enables the service instance to correctly authenticate when a user attempts to access resources that are located on other domain-member computers. For more information, see the MSDN article Service Principal Names. To create SPNs, you use ADSI Edit that is included with Windows Server. You can use this Microsoft Management Console (MMC) snap-in tool to enter SPN values for a specific computer or user account. Important 58

If IIS is configured to use kernel mode authentication, you must configure IIS to use the Web application pools identity for internal virtual directories used by Microsoft Dynamics CRM. You can do so by modifying the windowsAuthentication element for the default Web site on the Web site where Microsoft Dynamics CRM is installed. For details about the windowsAuthentication element, see the IIS 7.0: windowsAuthentication Element (IIS Settings Schema) MSDN article. To configure useAppPoolCredentials using the ApplicationHost.config file open the ApplicationHost.config file in a text editor. By default, this file is located at %windir%\system32\inetsrv\config\. For all folders under the Default Web Site location path, set the value of the WindowsAuthentication element and the useAppPoolCredentials attribute to true. For example:
<system.webServer> <security> <authentication> <windowsAuthentication enabled="true" useAppPoolCredentials="true" /> </authentication> </security> </system.webServer>

To configure the SPN, follow these steps: 1. Open Active Directory Users and Computers. 2. Create a user account to run the CRMAppPool application pool in IIS. To do this, we recommend that you use a name that describes what the account will be used for, such as CRMService. Important This user account must be member of the Domain Users group. 3. Close Active Directory Users and Computers. 4. Click start, type adsi edit, and then press ENTER. 5. Expand the domain, expand the node that begins with DC=, and then expand CN=Users. 6. Right-click the user account that you created in the previous step, such as CRMService, 59

and then click Properties. 7. In the Attribute list, scroll down, select servicePrincipalName, and then click Edit. 8. In the Value to add box, type HTTP/CRMNLBName. FQDN and then click Add. Where, CRMNLBName, is the NLB cluster name and FQDN is the fully qualified domain name. For example, the CRMNLBName.FQDN name might be CRMNLBCluster.contoso.com. Important Note this NLB cluster name. You must use this name in the following step when you create the NLB cluster and when you update the configuration database. Tip Use the setspn command line tool to determine if the SPN is already in use. 9. In the Value to add box, type HTTP/CRMNLBName and then click Add. 10. Click OK two times. 11. Close ADSI Edit.

Step 3: Install Microsoft Dynamics CRM servers

Each instance of Microsoft Dynamics CRM in a multi-server deployment must be installed one at a time. The following steps assume that an instance of a Full Server installation of Microsoft Dynamics CRM will be deployed on a computer named CRM01, and a second instance will be installed on a computer named CRM02. Microsoft Dynamics CRM Server 2011 is supported for multiple-server installations. Installing Microsoft Dynamics CRM Workgroup Server 2011 on multiple servers is not supported and is a violation of the license agreement.

Install the first instance Microsoft Dynamics CRM on CRM01: 1. Run Microsoft Dynamics CRM Setup on server CRM01. For step-by-step guidance, see the previous topics in this section. 2. On the Specify Deployment Options page, select the instance of SQL Server that will be used for the Microsoft Dynamics CRM databases. Then, select the Create a new deployment option. Click Next and continue Setup. 3. On the Specify Security Account page, select the domain user account (for example, 60

CRMService) created previously. 4. Continue to run Setup until the installation is completed. Install the second instance Microsoft Dynamics CRM on CRM02: 1. Run Microsoft Dynamics CRM Setup on server CRM02. 2. On the Specify Deployment Options page, enter or select the name of the computer that is running SQL Server where the Microsoft Dynamics CRM databases are stored (from the installation of CRM01), and then click Connect to, and if necessary, upgrade an existing deployment. Click Next. 3. On the Specify Security Account page, select the domain user account (for example, CRMService) created previously. 4. Continue to run Setup until the installation is completed.

Step 4: Configure NLB for the deployment

After the Microsoft Dynamics CRM Server 2011 installations are complete, run Deployment Manager to configure NLB for the deployment.

Verify or change the Web addresses 1. On the Microsoft Dynamics CRM server, start Deployment Manager. 2. In the console tree, right-click Microsoft Dynamics CRM, and then click Properties. 3. Click the Web Address tab and make sure that the virtual cluster name, such as crmcluster:5555 appears. Important Depending on how you deployed the Microsoft Dynamics CRM Server 2011 role group or separate server role installation, and the configuration of each server in the NLB cluster, the Web Application Server, Organization Web Service, Discovery Web Service, or Deployment Web Service Web addresses may be different. For example, if you installed the Front End Server role group on a server in an NLB cluster that is named crmcluster1 in the contoso domain but installed the Back End Server role group on a different server in a different NLB cluster such as crmcluster2 in the same domain, the name of the Web Application Server, Organization Web Service, Discovery Web Service Web addresses will be different from the Deployment Web Service Web address. 61

For a Full Server role deployment, all Web addresses will use the same computer name or FQDN of the cluster. If you are using a TCP port other then 80 (non-secure HTTP) or 443 (secure HTTP or SSL), you must specify the port number by appending the FQDN name with :5555, where 5555 is the port number, such as crmcluster:5555.

Set NLB for the deployment 1. On the Microsoft Dynamics CRM server, start Deployment Manager. 2. In the console tree, right-click Microsoft Dynamics CRM, and then click Properties. 3. Click the Web Address tab and then click Advanced. 4. In the NLB and SSL Header Information dialog box, specify if you are using network load-balancing (NLB) and the header for the Secure Sockets Layer (SSL) offloading system. To make Microsoft Dynamics CRM aware of the NLB cluster, you must select The deployment uses an NLB option. Selecting The deployment uses an NLB sets Microsoft Dynamics CRM to configure Windows Identity Foundation (WIF) to use the encryption certificate to encrypt, decrypt, and sign the Microsoft Dynamics CRM session authentication cookies. The encrypted cookies can then be processed by any server in the NLB cluster. For information about procedures for loading and administering NLB on Windows Server, see the Network Load Balancing Manager Help on the Windows Server computer. For information about how to configure NLB in Windows Server 2008, see Network Load Balancing Deployment Guide. Note The SSL header is not a URL or domain. It is an agreed upon header value for the HTTP request that is configured on the device that is handling the SSL offloading. Review the SSL offloading device documentation for the header value. 5. Click OK and then close Deployment Manager.

Configure domain names for IFD

To configure Microsoft Dynamics CRM for IFD, you must start Deployment Manager and run the Internet-Facing Deployment Configuration Wizard to add or revise the domain values. Depending on how you deployed the Microsoft Dynamics CRM 2011 role group or separate 62

server role installation, and the configuration of each server in the NLB cluster, the Web Application Server Domain, Organization Web Service Domain, and Discovery Web Service Domain values use the NLB virtual cluster domain name. For example, if the Web Application Server is installed on an Internet-facing NLB cluster that has the FQDN virtual name crmcluster.contoso.com, enter contoso.com as the Web Application Server Domain value. For more information about how to configure internal web address and external domain values, see the Deployment Manager Help.

Step 5: Verify and monitor the cluster installation

Verify that Microsoft Dynamics CRM client applications can connect to Microsoft Dynamics CRM by using the cluster name, such as CRMNLBCluster. To monitor the cluster, you have the following options. Network Load Balancing Manager. Log entries are displayed in the bottom of Network Load Balancing Manager. Event Viewer. Entries are recorded in the System logs by using the NLB source. Wlbs. Run the wlbs.exe query or wlbs.exe display command at the command prompt to view information about the state of the cluster. Windows Server 2008 Network Load Balancing Management Pack for Operations Manager 2007. When your organization uses MOM to monitor and manage the servers in your organization, include the Windows Server 2008 Network Load Balancing Management Pack for Operations Manager 2007 on the cluster hosts. Microsoft Server Network Load Balancing Management Pack for Operations Manager 2007

See Also
Troubleshooting installation and upgrade Install Microsoft Dynamics CRM Server 2011 to use a Microsoft SQL Server cluster environment

Install Microsoft Dynamics CRM Server 2011 to use a Microsoft SQL Server cluster environment
You can install Microsoft Dynamics CRM Server 2011 so that it can use a clustered Microsoft SQL Server environment that uses Windows Server failover clusters. 63

Important Failover clustering is not supported with Microsoft SQL Server 2008 Workgroup.

Base configuration
This topic describes the options that are available to configure Microsoft Dynamics CRM to use a clustered SQL Server environment. The base configuration for a Microsoft Dynamics CRM Server 2011 system is described previously in this guide. The instructions in this topic expand on the base configuration by installing Microsoft Dynamics CRM Server 2011 so that it has a connection to a cluster of computers that are running SQL Server. The configuration described here involves a single deployment of Microsoft Dynamics CRM Server 2011 accessing a cluster of two computers that are each running an instance of Microsoft SQL Server 2008. The typical Microsoft Dynamics CRM deployment creates and uses the following Microsoft Dynamics CRM-specific databases on SQL Server: OrganizationName_MSCRM. This is the organization database where Microsoft Dynamics CRM data is stored, such as all records and activities. MSCRM_CONFIG. This database contains Microsoft Dynamics CRM metadata, such as configuration and location information that is specific to each organization.

See Also
Troubleshooting installation and upgrade Option 1: Install a new Microsoft Dynamics CRM Server 2011 deployment

Option 1: Install a new Microsoft Dynamics CRM Server 2011 deployment

Follow these steps to install Microsoft Dynamics CRM Server 2011 that will use a SQL Server cluster.

Step 1: Create the SQL Server cluster

Using the SQL Server documentation for the appropriate SQL Server edition, install and configure SQL Server and create a SQL Server cluster. The basic steps include the following: 64

 Collecting the information that you must have to create the virtual server. This can include a cluster disk resource, IP addresses, network names, and the nodes available for the cluster. Performing SQL Server Setup. After the necessary information is entered, the Setup program installs a new instance of SQL Server on the local disk of each node in the cluster and installs the system databases on the shared disk that is specified as part of the cluster configuration. The SQL Server program files are installed on each cluster node. During the cluster configuration, a virtual server is created. Note Although you can install Microsoft Dynamics CRM Server 2011 to a SQL Server cluster that is configured for either active-active or active-passive clustering, the cluster will function in an active-passive manner. For more information about SQL Server failover clustering, see High Availability with SQL Server R2.

Step 2: Install Microsoft Dynamics CRM Server 2011

Install Microsoft Dynamics CRM Server 2011 by using the procedures in the previous section and perform the following tasks during Setup: 1. On the Select SQL Server page, type the virtual server name that you specified when you created the SQL Server cluster. 2. On the same page, select the Create a new deployment option, and then complete Microsoft Dynamics CRM Server Setup.

See Also
Install Microsoft Dynamics CRM Server 2011 to use a Microsoft SQL Server cluster environment Option 2: Rehome or configure an existing Microsoft Dynamics CRM Server 2011 deployment that connects to a SQL Server cluster that stores only the organization database

65

Option 2: Rehome or configure an existing Microsoft Dynamics CRM Server 2011 deployment that connects to a SQL Server cluster that stores only the organization database
To configure your existing Microsoft Dynamics CRM Server 2011 to use the SQL Server cluster that contains only the organization database, follow these steps: 1. Follow the procedure in the previous section to create the SQL Server cluster. 2. Back up the MSCRM_CONFIG and OrganizationName_MSCRM databases that are on the existing SQL Server. 3. Restore the OrganizationName_MSCRM database to the SQL Server cluster. For more information about how to restore databases, see Backing Up and Restoring Databases in SQL Server. 4. On the computer that is running the Deployment Tools server role, start Deployment Manager. To do this, click Start, point to All Programs, point to Microsoft Dynamics CRM, and then click Deployment Manager. 5. Expand the Deployment Manager node, and then click Organizations. 6. Right-click the organization, and then click Disable. Warning When you disable an organization, users will no longer be able to access Microsoft Dynamics CRM for that organization. Click Yes to disable the organization. 7. In the list of organizations, right-click the organization, and then click Edit Organization. 8. In the Edit Organization Wizard, in the SQL Server box, type the virtual SQL Server name for the SQL Server cluster that you created earlier, and then click Next. 9. On the System Requirements page, after a successful diagnostics check, click Next, and then click Apply. 10. Click Finish. 11. Enable the organization. To do this, right-click the organization, and then click Enable. 12. Reset the IIS services on the computer that is running IIS where the Microsoft Dynamics 66

CRM Server 2011 Web application is installed. To do this, click Start, click Run, type iisreset in the Open box, and then click OK.

See Also
Option 1: Install a new Microsoft Dynamics CRM Server 2011 deployment Option 3: Rehome or configure an existing Microsoft Dynamics CRM Server 2011 deployment that connects to a SQL Server cluster that stores both the configuration and organization databases

Option 3: Rehome or configure an existing Microsoft Dynamics CRM Server 2011 deployment that connects to a SQL Server cluster that stores both the configuration and organization databases
Configure your existing Microsoft Dynamics CRM Server 2011 to use the SQL Server cluster that contains both the configuration and organization databases.

To implement this option, follow these steps: 1. Follow the procedure in the previous section to create the SQL Server cluster. Important Before you complete the following steps, make sure that users are not connected to, or accessing, the Microsoft Dynamics CRM system. You can do this by disabling the organization. 2. Back up the MSCRM_CONFIG and OrganizationName_MSCRM databases that are on the existing SQL Server. 3. Restore the MSCRM_CONFIG and OrganizationName_MSCRM databases to the SQL Server cluster shared disk. For more information, see Backing Up and Restoring Databases in the SQL Server. 4. On all nodes in the cluster, modify Windows registry subkeys. Warning Serious problems might occur if you modify the registry incorrectly. These problems might require you to reinstall the operating system and Microsoft 67

Dynamics CRM. We cannot guarantee that these problems can be resolved. Modify the registry at your own risk. 5. Update the configdb registry subkey on the computer that is running Microsoft Dynamics CRM Server 2011. To do this, follow these steps: a. On the computer that is running the Microsoft Dynamics CRM web application, click Start, click Run, type regedit in the Open box, and then click OK. b. Locate the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM c. Right-click configdb, and then click Modify. d. In the Value data box, change the data source to the name of the new virtual SQL Server, and then click OK. For example, the string value in the Value data box should resemble the following:
Data Source=NewSQLServer;Initial Catalog=MSCRM_CONFIG;Integrated Security=SSPI

Note If multiple Microsoft Dynamics CRM Server 2011 roles are in your deployment, you must update the registry keys for all the server roles. If you use the Microsoft Dynamics CRM Reporting Extensions and if you are not moving the Microsoft SQL Server Reporting Services server, you must update the configdb subkey on the computer on which the Microsoft Dynamics CRM Reporting Extensions is installed. 6. Configure Microsoft Dynamics CRM Server 2011 to connect with the new instance of SQL Server where the organization database is now located. To do this, follow these steps: a. On the computer that is running the Microsoft Dynamics CRM Server 2011 Web application, start Deployment Manager. To do this, click Start, point to All Programs, point to Microsoft Dynamics CRM, and then click Deployment Manager. b. Expand the Deployment Manager node, and then click Organizations. c. Right-click the organization, and then click Disable. When you disable an organization, users will no longer be able to access Microsoft Dynamics CRM for that organization. d. Click Yes to disable the organization. 68

e. In the list of organizations, right-click the organization, and then click Edit Organization. f. In the Edit Organization Wizard, in the SQL Server box, type the virtual SQL Server name for the SQL Server cluster that you created earlier, and then click Next.

g. On the System Requirements page, after a successful diagnostics check, click Next, and then click Apply. h. Click Finish. i. Enable the organization. To do this, right-click the organization, and then click Enable.

7. Reset the IIS services on the computer that is running IIS where the Microsoft Dynamics CRM Server 2011 Web application is installed. To do this, click Start, click Run, type iisreset in the Open box, and then click OK. Disable an organization 1. On the computer that is running the Microsoft Dynamics CRM Server 2011 Web application, start Deployment Manager. To do this, click Start, point to All Programs, point to Microsoft Dynamics CRM, and then click Deployment Manager. 2. Expand the Deployment Manager node, and then click Organizations. 3. Right-click the organization, and then click Disable. When you disable an organization, users will no longer be able to access Microsoft Dynamics CRM for that organization. 4. Click Yes to disable the organization.

See Also
Option 2: Rehome or configure an existing Microsoft Dynamics CRM Server 2011 deployment that connects to a SQL Server cluster that stores only the organization database Configure an organization database for SQL Server 2008 database mirroring

Configure an organization database for SQL Server 2008 database mirroring

Microsoft Dynamics CRM uses two databases, configuration and organization. The configuration database contains configuration information that is specific to the Microsoft Dynamics CRM system. The organization database is used to store all the organization-specific data and the 69

customer relationship data for the organization. Some versions of Microsoft Dynamics CRM let you create and use multiple organizations. Therefore, some deployments may have multiple organization databases in the Microsoft Dynamics CRM system. To mirror a Microsoft Dynamics CRM organization database that can automatically fail over to another computer that is running Microsoft SQL Server, you configure the following three computers to establish the SQL Server database mirroring session: Primary database computer. This computer runs SQL Server where the Microsoft Dynamics CRM organization database is located. In this example, Microsoft Dynamics CRM is installed and running on the default instance of SQL Server. The computer name is MSCRM_Primary. Mirrored database computer. This computer, with a connection to MSCRM_Primary, is running SQL Server and it uses a different default instance. This computer must have a network connection to MSCRM_Primary. The computer name is MSCRM_Mirror. Witness computer. This computer runs SQL Server, or it can be a desktop system that is running SQL Server 2005 Express Edition. This computer must have a network connection to MSCRM_Primary and MSCRM_Mirror. The computer name is MSCRM_Witness. Note A computer that is running Microsoft SQL Server 2008 Workgroup edition can be a Witness. However, it cannot be a Primary or Mirror computer in a database-mirroring session.

See Also
Install Microsoft Dynamics CRM Server 2011 to use a Microsoft SQL Server cluster environment Configure an organization database for SQL Server 2008 database mirroring

Configure a Microsoft Dynamics CRM organization for database mirroring

Note The previously mentioned computers (MSCRM_Primary, MSCRM_Mirror, and MSCRM_Witness) must all have a network connection and must be running an edition of SQL Server that supports database mirroring.

70

To mirror the organization database, follow these steps: 1. On the instance of SQL Server that stores the primary database (MSCRM_Primary), start SQL Server Management Studio. 2. Expand Databases, right-click OrganizationName_MSCRM, where OrganizationName is the name of your organization, and then click Properties. Verify that the Microsoft Dynamics CRM organization database recovery model is set to Full. This is required for a database that will be mirrored. a. To verify the recovery model, on the Database Properties window under Select a page, click Options. The recovery model appears in the Recovery model list. Select Full. b. Click OK to close the Database Properties window. 3. Make a full backup of the organization database. For more information about how to do this, see the SQL Server Management Studio Help. 4. Restore the full backup of the primary (MSCRM_Primary) to the mirror instance (MSCRM_Mirror) by using the RESTORE WITH NORECOVERY option, which is required for database mirroring. For more information about how to do this, see the SQL Server Management Studio Help. 5. Configure database mirroring. To do this, start SQL Server Management Studio, connect to the instance of SQL Server where the primary database (MSCRM_Primary) is located, and then follow these steps: a. Expand Databases, right-click the Microsoft Dynamics CRM organization database that you want to mirror, point to Tasks, and then click Mirror. b. Click Configure Security, and then, on the new window, click Next. c. On the Include Witness Server window, select Yes, and then click Next. d. On the Choose Servers to Configure window, select Witness server instance, and then click Next. e. On the Principle Server Instance window, in the Principal server instance list, select the instance of SQL Server (MSCRM_Primary) where the Microsoft Dynamics CRM organization database is located. In addition, you can change the default settings for the listener port, encryption, and endpoint name. Click Next. f. On the Mirror Server Instance window, in the Mirror server instance list, select the instance of SQL Server (MSCRM_Mirror) where you restored the Microsoft Dynamics CRM organization database in the previous step. You can change the default settings for the listener port, encryption, and endpoint name, if it is necessary. Click Next. 71

g. On the Witness Server Instance window, in the Witness server instance list, select the computer that you want to designate as the Witness (MSCRM_Witness). At this point, you can change the default settings for the listener port, encryption, and endpoint name. Click Next. If you are connecting to an instance of SQL Server that is running Microsoft SQL Server 2008 Express Edition, verify that remote connections are supported. To do this, on the computer where Microsoft SQL Server 2008 Express Edition is installed start SQL Server Configuration Manager and make sure that the remote-connections feature is enabled. h. On the Service Accounts window, enter the Active Directory service account for each instance. We recommend that you specify the same service account for all three partners in the mirroring session. Click Next. i. Click Finish. The wizard runs through a list of verification checks. Upon completion, click Start Mirroring.

6. If you want to mirror the configuration database (MSCRM_CONFIG) you must complete similar steps to establish the mirror and update the SQL Server connection string in the registry. To do this, follow these steps. Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require you to reinstall the operating system and Microsoft Dynamics CRM. We cannot guarantee that these problems can be resolved. Modify the registry at your own risk. a. On the computer that is running Internet Information Services (IIS), where the Microsoft Dynamics CRM web application is installed, start Registry Editor and locate the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM\ b. Right-click configdb, and then click Modify. Insert Failover Partner=MSCRM_Mirror; into the connection string, after the DataSource value. The complete connection string will appear similar to the following example, where MSCRM_Primary is the primary SQL Server\instance name and MSCRM_Mirror is the mirrored SQL Server\instance name:
Data Source=MSCRM_Primary\SQL1;Failover Partner=MSCRM_Mirror\SQL2;Initial Catalog= MSCRM_CONFIG;Integrated Security=SSPI

72

c. Click OK, and then close Registry Editor. 7. Create the SQL logins for the Microsoft Dynamics CRM security groups on the Mirror server (MSCRM_Mirror). To do this, follow these steps. a. On the SQL Server (MSCRM_Primary) start SQL Server Management Studio, and connect to the Primary database. b. Expand Databases, expand the OrganizationName_MSCRM database where OrganizationName is the name of your organization, expand Security, and then double-click Users. c. Copy and paste the names, including the domain name and the GUIDs, (the GUIDs are located at the end of the name) for the following groups: PrivReportingGroup ReportingGroup SQLAccessGroup To do this, right-click the SQL user name, click Properties, in the User name box, right-click the whole value, and then click Copy. Then, in a text editor such as Notepad, paste the contents. Repeat these steps for each group until you have the contents for all three groups. d. In SQL Server Management Studio, connect to the SQL Server Mirror instance (MSCRM_Mirror). e. Expand Databases, expand Security, right-click Logins, and then click New Login. f. Switch to the text editor in which the SQL users were previously pasted, and copy the contents of one of the groups.

g. Switch to the Login New form that was opened in step e. In the Login name box, paste the contents into the box, and then click OK. The SQL user contents should resemble the following example. DomainName\SQLAccessGroup {859409f6-c4a5-4cb6-86f2-af264520ea10} h. Repeat steps e through g to create SQL logins for the remaining groups. 8. Update the configuration database to specify the mirror. To do this, follow these steps. Important Back up the Microsoft Dynamics CRM configuration database (MSCRM_CONFIG) before you run these update statements. 73

a. Run the following update statement against the configuration (MSCRM_CONFIG) database.
Update Organization set ConnectionString = 'Provider=SQLOLEDB;Data Source=MSCRM_Primary\SQL1;Failover Partner=MSCRM_Mirror\SQL2;Initial Catalog=Organization_MSCRM;Integrated Security=SSPI' where DatabaseName = 'Organization_MSCRM'

Replace MSCRM_Primary\SQL1 with the name of the Primary instance of SQL Server. If you are using the default instance, do not designate the instance such as \SQL1. Replace MSCRM_Mirror\SQL2 with the name of the Mirrored instance SQL Server. If you are using the default instance, do not designate the instance such as \SQL2. Replace Organization_MSCRM with the name of the organization database. b. Run the following update statement against the configuration (MSCRM_CONFIG) database.
Update Organization set MirroredSQLServerName = 'MSCRM_Mirror\SQL2' where DatabaseName = 'Organization_MSCRM'

Replace MSCRM_Mirror\SQL2 with the name of the Mirrored instance of SQL Server. If you are using the default instance, do not designate the instance such as \SQL2. Replace Organization_MSCRM with the name of the organization database. 9. After you make these changes, reset IIS on the computer that is running Microsoft Dynamics CRM. To do this, click Start, and then click Run. In the Open box, type iisreset, and then click OK.

See Also
Configure an organization database for SQL Server 2008 database mirroring Monitor and test for failover

Monitor and test for failover

The Mirrored databases can fail over either manually or automatically.

74

To monitor and test the failover, follow these steps: 1. Start SQL Server Management Studio, right-click the primary database, point to Tasks, and then click Mirror. 2. On the Database Properties window, you can monitor the status of the synchronization between the Primary and Mirrored database. To test the fail-over feature manually, click Failover. When failover occurs, SQL Server will switch the mirroring session roles between the Primary database and the Mirrored database to make the mirror the primary and the primary the mirror. For more information about how to implement database mirroring, see Data Mirroring Deployment.

See Also
Configure an organization database for SQL Server 2008 database mirroring Microsoft Dynamics CRM 2011 E-mail Router Installation Instructions

Set configuration and organization databases for SQL Server 2012 AlwaysOn failover
Applies to: Microsoft Dynamics CRM 2011 Microsoft SQL Server 2012 AlwaysOn Failover Cluster Instances (FCI) and AlwaysOn Availability Groups provide a comprehensive high availability and disaster recovery solution. This topic describes how to configure an existing on-premises deployment of Microsoft Dynamics CRM 2011 so that the configuration and organization databases are part of a two-node SQL Server 2012 AlwaysOn failover cluster instance that uses availability groups. For more information about these SQL Server 2012 high availability solutions, see AlwaysOn Failover Cluster Instances and AlwaysOn Availability Groups. In this Topic
Prerequisites Enable SQL Server 2012 AlwaysOn Create the availability group Create the SQL logins for the Microsoft Dynamics CRM security groups on all secondary replicas

75

Update the configuration database connection string in the Windows registry Update the connection string in the configuration database Restart IIS and Microsoft Dynamics CRM services Monitor the availabity group and test for failover Known issues

Prerequisites
In this topic, a simple two-server instance failover cluster will be configured that requires the following: Two Windows Server 2008 R2 or Windows Server 2012 servers running in a two-node failover cluster configuration with shared storage, such as a SAN, NAS, or Windows Storage Server. Two servers running SQL Server 2012 on Windows Server 2008 R2 that will be replicas in the SQL Server 2012 AlwaysOn instance failover cluster. The SQL Server primary replica instance has both the configuration (MSCRM_CONFIG) and organization (OrganizationName_MSCRM) databases. For more information about what versions of SQL Server 2012 support AlwaysOn, see High Availability (AlwaysOn). For more information about how to create a SQL Server 2012 failover cluster, see, Create a New SQL Server Failover Cluster (Setup). Microsoft Dynamics CRM 2011 with Microsoft Dynamics CRM 2011 Update Rollup 6 or later update rollup deployed. For multi-subnet failover support, you must apply Update 4.0.2 for Microsoft .NET Framework 4 Runtime.

76

Important Microsoft Dynamics CRM 2011 Update Rollup 6 or later update rollup is required to use Microsoft SQL Server 2012. Microsoft Dynamics CRM 2011 databases are supported with SQL Server on Windows Server 2012. Microsoft Dynamics CRM Server 2011, Microsoft Dynamics CRM Reporting Extensions, and Microsoft Dynamics CRM E-mail Router require Microsoft Dynamics CRM 2011 Update Rollup 13 or a later update rollup to run on Windows Server 2012. For more information, see Supported Windows Server 2012 editions.

Enable SQL Server 2012 AlwaysOn

The following steps for establishing the AlwaysOn features use Microsoft SQL Server 2012 Management Studio. Alternatively, you can use Transact-SQL or SQL Server PowerShell. For more information, see Getting Started with AlwaysOn Availability Groups (SQL Server). 1. In SQL Server Configuration Manager, enable AlwaysOn Availability Groups on the primary and secondary replica. For detailed steps, see Enable AlwaysOn Availability Groups. To enable SQL Server 2012 AlwaysOn running on Windows Server 2008, see A hotfix is available to let you
configure a cluster node that does not have quorum votes in Windows Server 2008 and in Windows Server 2008 R2.

2. In SQL Server Management Studio SQL Server Management Studio, create an availability group; specify the configuration and organization databases, and primary and secondary replica. For more information, see Creation and Configuration of Availability Groups (SQL Server).

Create the availability group

The following steps create a single SQL Server 2012 availability group that includes a Microsoft Dynamics CRM 2011 configuration database and a single organization database. Additionally, a listener will be added to the availability group.

Create the availability group for the configuration and organization databases 1. On the SQL Server that will be the primary replica, start SQL Server Management Studio. 2. In Object Explorer, right-click AlwaysOn High Availablility, and then click New Availability Group Wizard. 3. When the wizard appears, click Next. 4. On the Specify Name page, type a name for the availability group, such as Dynamics 77

CRM, and then click Next. 5. On the Select Databases page, select the MSCRM_CONFIG and OrganizationName_MSCRM databases, and then click Next. Important Notice the following requirements for adding a database to an availability group: The recovery model must be set to Full. By default, organization databases (OrganizationName_MSCRM), are set to Simple. A full back up of the database is required. 6. On the Specify Replicas page, click Add Replica, type the name of your replica SQL Server in the Server name box (such as CRMNode2 in this example), and then click Connect. The replica server instance appears in the Server Instance list. 7. Click the Endpoints tab and verify the both replicas are in the list. Scroll right to the SQL Server Service Account and make sure a domain user account is specified. A domain user account for the SQL Server service is required for SQL Server failover clustering. 8. Click the Listener tab. An availability group listener enables faster client connection failover in multi-subnet scenarios. Enter the following information. Listener DNS name: Type a name for the listener. To complete the listener creation, specify a port, and set the Network Mode to Static IP. Click Add to enter the IP address, and click OK. For more information about these properties, click Help in the New Availability Group wizard. Click Next. 9. Determine what, if any, additional changes to make to the replicas, and then click Next. For more information, click Help in the New Availability group wizard. a. On the Select Data Synchronization page, select the data synchronization method. If you select Full, you must add a network share that can be accessed by all replicas. Notice that the SQL Server service account requires read\write permissions to the share. For more information, click Help in the New Availability group wizard. Click Next. 10. The Validation page appears that runs the validation checks for the new availability group. Errors must be resolved before the availability group can be created. Click Next. 11. On the Summary page, verify that the choices are correct, and then click Finish. 78

Create the SQL logins for the Microsoft Dynamics CRM security groups on all secondary replicas
Create the SQL logins for the Microsoft Dynamics CRM security groups on the secondary replica. To do this, follow these steps: 1. Start SQL Server Management Studio and connect to the secondary replica (CRMNode2). 2. Expand the Security node, right-click Logins and then click New Login. 3. In the Login name box, click Search, make sure that Groups is included in the Select this object type (if not click Object Types and add it). Type DomainName\PrivReportingGroup, click Check Names, and when the name resolves correctly, click OK. 4. Click the User Mapping page and select the MSCRM_CONFIG database and all the OrganizationName_MSCRM databases, and then click OK on the Login - New dialog box to close and save the new login. 5. Repeat steps 2 through 4 for the following security groups. ReportingGroup SQLAccessGroup Create the MSCRMSqlClrLogin SQL Login 1. Create the asymmetric key for the MSCRMSqlClrLogin SQL Login On all secondary replicas, execute the following SQL statement against the master database to create the asymmetric key, where <path> is the folder path to the Microsoft.Crm.SqlClr.Helper.dll file. By default, this is located in the \\<serverName>\Program Files\Microsoft Dynamics CRM\Tools\ folder, where the Deployment Tools server role is installed.
IF NOT EXISTS (SELECT * FROM sys.asymmetric_keys WHERE name = 'MSCRMSqlClrKey') BEGIN EXECUTE ('CREATE ASYMMETRIC KEY MSCRMSqlClrKey FROM EXECUTABLE FILE =<path>\Microsoft.Crm.SqlClr.Helper.dll')END

2. Create the MSCRMSqlClrLogin SQL login Execute the following SQL statement against the master database to create the MSCRMSqlClrLogin SQL login.
IF NOT EXISTS (SELECT * FROM sys.syslogins WHERE name = 'MSCRMSqlClrLogin')BEGIN CREATE LOGIN MSCRMSqlClrLogin FROM

79

ASYMMETRIC KEY MSCRMSqlClrKey GRANT UNSAFE ASSEMBLY TO MSCRMSqlClrLogin END

Update the configuration database connection string in the Windows registry

Update the SQL Server connection string in the Windows registry on the computer running IIS where the Web Application Server role is installed. To do this, follow these steps. Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require you to reinstall the operating system and Microsoft Dynamics CRM. We cannot guarantee that these problems can be resolved. Modify the registry at your own risk. 1. On the computer that is running Internet Information Services (IIS), where the Web Application Server role is installed, start Registry Editor and locate the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM\ 2. Right-click configdb, and then click Modify. a. If Failover Partner=MSCRM_Mirror is present, remove this from the value. b. Change the Data Source from the SQL Server instance name to the availability group listener name. The complete connection string should appear similar to the following example, where MSCRMAG is the availability group listener name for the availability group that includes the Microsoft Dynamics CRM configuration database: Data Source MSCRMAG;Initial Catalog= MSCRM_CONFIG;Integrated Security=SSPI Tip The listener name can be located under the Availability Groups node in in SQL Server Management Studio. c. If the Microsoft Dynamics CRM deployment is running in a multiple subnet, add ;multisubnetfailover=true to the end of the configdb value to form the connection string. A complete configdb value for a multiple subnet should appear as the following:

80

Data Source MSCRMAG;Initial Catalog= MSCRM_CONFIG;Integrated Security=SSPI;multisubnetfailover=true 3. Click OK, and then close Registry Editor.

Update the connection string in the configuration database

Update the organization table in the configuration database to specify the availability group listener name for the client connection string. To do this, run the following update statement against the configuration (MSCRM_CONFIG) database. Warning Back up the Microsoft Dynamics CRM configuration database (MSCRM_CONFIG) before you run these update statements.
Update Organization set ConnectionString = 'Provider=SQLOLEDB;Data Source=AG_Listener_Name;Initial Catalog=OrganizationName_MSCRM;Integrated Security=SSPI' where DatabaseName = 'MSCRM_CONFIG'

Replace AG_Listener_Name with the availability group listener name where the Microsoft Dynamics CRM organization database is located. Replace OrganizationName_MSCRM with the name of the organization database. Additional parameters available If you are running on a multi-subnet, add the following parameter to the end of the connection string before you run the statement: ;multisubnetfailover=true Additionally, if you use a port number other than 1433 for the availability group listener add the following parameter where Port_Number is the network port number.
Update Organization set ConnectionString = 'Provider=SQLOLEDB;Data Source=AG_Listener_Name, Port_Number;Initial Catalog=OrganizationName_MSCRM;Integrated Security=SSPI;multisubnetfailover=true' where DatabaseName = 'MSCRM_CONFIG'

Restart IIS and Microsoft Dynamics CRM services

After you make these changes, reset IIS on the computer that is running the Web Application Server role. Warning 81

All active Microsoft Dynamics CRM users will be disconnected. To do this, click Start, and then click Run. In the Open box, type iisreset, and then click OK. Restart all Microsoft Dynamics CRM services in the deployment on all servers where Microsoft Dynamics CRM Server 2011 features are installed.

Monitor the availabity group and test for failover

Microsoft SQL Server 2012 Management Studio includes features that make viewing the availability group status and executing a manual failover easy.

View the availability group state 1. Start SQL Server Management Studio and connect to the instance of SQL Server that is the primary replica in the availability group. 2. In SQL Server Management Studio, expand Availability Groups, right-click the availability group that you created for Microsoft Dynamics CRM, and then click Show Dashboard. The dashboard displays all replicas and the synchronization state. Notice that you can view the dashboard from any replica in the availability group.

Test for failover 1. Verify that a Microsoft Dynamics CRM can connect to the availability group. For example, start Internet Explorer, and connect to the Microsoft Dynamics CRM organization URL. 2. From the dashboard described in the previous procedure, click Start Failover Wizard to begin the failover process. 3. Follow the instructions in the wizard to complete the failover. After a successful failover, the primary replica becomes the secondary replica and the secondary replica becomes the primary replica. 4. Switch to the web browser connected to the Microsoft Dynamics CRM organization and verify that you can seamlessly connect to the new primary replica by clicking anywhere in the application. To switch back to the original primary and secondary replicas, perform the manual failover procedure again on the new primary replica. 82

Known issues
This section describes issues that may occur when you configure Microsoft Dynamics CRM databases for SQL Server AlwaysOn failover cluster instance and availability groups.

Some Deployment Manager organization features do not work after failover

After a SQL Server 2012 failover that uses availability groups for one or more organization databases, certain Microsoft Dynamics CRM Deployment Manager organization operations do not work, such as the following: Edit Organization. An error message is returned when you try to change an organization. Organization properties. An error message is returned when you try to view the properties for an organization. Organization Browse and Update feature functionality does not appear. This issue occurs because Deployment Manager uses the SQLServerName column in the organization table of the configuration database to locate and connect to the SQL Server. The value contains the original SQL Server primary replica before the failover and is not updated to the new primary replica when a failover occurs. To work around this issue, you can manually update the SQLServerName value to reference the new primary replica after a failover has occurred. To do this, run the following SQL query where New_Primary is the instance of SQL Server that is the new primary replica and Old_Primary is the name of the instance of SQL Server that was the original primary replica before the failover. Warning The following SQL query will set all organization databases in the deployment to the same instance of SQL Server.

Update MSCRM_CONFIG.dbo.Organization set SQLServerName='New_Primary' where SQLServerName='Old_Primary'

See Also
Microsoft Dynamics CRM Server 2011 Installation Instructions Failover Cluster Step-by-Step Guide: Configuring a Two-Node File Server Failover Cluster

83

Microsoft Dynamics CRM 2011 E-mail Router Installation Instructions

This section applies to Microsoft Dynamics CRM Online and on-premises versions of Microsoft Dynamics CRM 2011. The Microsoft Dynamics CRM E-mail Router is a software component that creates an interface between Microsoft Dynamics CRM 2011 or Microsoft Dynamics CRM Online and Microsoft Exchange Server 2003, Microsoft Exchange Server 2007, Microsoft Exchange Server 2010, Microsoft Exchange Online, SMTP, or a POP3-compliant e-mail server. After the Email Router is installed, it transfers e-mail messages to the Microsoft Dynamics CRM system, and it sends outgoing e-mail messages that users created in the Microsoft Dynamics CRM system. Microsoft Dynamics CRM stores e-mail messages as activity records. These e-mail activity records are stored in the Microsoft Dynamics CRM database and include both the contents of the e-mail message, such as the text of the message and its subject line, and relevant associations with other Microsoft Dynamics CRM records. For example, when a salesperson replies to a customer about a case, the salesperson creates an e-mail activity record that includes the text of the message, plus information associating the email activity record with the correct case record. Note For more information, see Planning e-mail integration in the Planning Guide. For a list of prerequisites, see Microsoft Dynamics CRM E-mail Router software requirements in the Planning Guide.

In This Section
Overview Install E-mail Router and Rule Deployment Wizard Troubleshooting E-mail Router issues

See Also
Download: Microsoft Dynamics CRM 2011 E-mail Router Microsoft Dynamics CRM Server 2011 Installation Instructions

84

Overview
Microsoft Dynamics CRM 2011 and Microsoft Dynamics CRM Online provide the following email processing features: Microsoft Dynamics CRM for Microsoft Office Outlook can process incoming and outgoing email messages for each user and does not require the E-mail Router. E-mail Router routes both incoming and outgoing messages. The E-mail Router supports POP3 e-mail systems for incoming messages and SMTP e-mail systems for outgoing messages. Microsoft Dynamics CRM e-mail messages are sent asynchronously when you use the E-mail Router. This section describes the e-mail system options and configurations.

See Also
Microsoft Dynamics CRM 2011 E-mail Router Installation Instructions E-mail Router

E-mail Router
The E-mail Router performs the following tasks: Routes incoming email messages to Microsoft Dynamics CRM. Sends email messages generated from Microsoft Dynamics CRM. The E-mail Router is required for users or queues that do not use Microsoft Dynamics CRM for Outlook. The E-mail Router can be installed on various versions of the Microsoft Windows operating system. For a list of supported Windows versions, see Microsoft Dynamics CRM Email Router software requirements in the Planning Guide. The computer on which you install the E-mail Router must have a connection to a Microsoft Exchange Server or to a POP3/SMTP email server. The E-mail Router contains the following components: The E-mail Router service ("Microsoft CRM Email Router") and the E-mail Router configuration files. 85

 The E-mail Router Configuration Manager. You use this wizard to configure the E-mail Router service. The Rule Deployment Wizard. This wizard lets you deploy rules that are used to route email messages to a forward mailbox from the mailbox of a user or queue. The Rule Deployment Wizard does not work with POP3/SMTP email servers. For more information, see Deploy inbox rules in Configure the E-mail Router in this guide. Important Only message class types that start with IPM.Note are tracked and saved in Microsoft Dynamics CRM. For a list of known message class types, see Office Dev Center: Item Types and Message Classes.

See Also
Overview Install E-mail Router and Rule Deployment Wizard

Install E-mail Router and Rule Deployment Wizard

You install the E-mail Router and the Rule Deployment Wizard by running the Microsoft Dynamics CRM E-mail Router Setup. To install the E-mail Router and the Rule Deployment Wizard, follow the instructions in this section. Important Installing on Windows Server 2012 If you are installing Microsoft Dynamics CRM 2011 E-mail Router on Windows Server 2012 you must download the latest Setup update and apply Microsoft Dynamics CRM 2011 Update Rollup 13 after Setup is finished. For more information, see Microsoft Dynamics CRM 2011 E-mail Router software requirements. Keep your Microsoft Dynamics CRM deployment current by installing the latest updates and hotfixes automatically from Microsoft Update. You can also search for updates on the Microsoft Download Center. Choosing Microsoft Update lets you install recommended updates automatically and without administrator permissions. If you have a previous version of the E-mail Router installed, do not use the procedures in this section. Instead, see Upgrade the E-mail Router in this guide.

86

To set up the E-mail Router 1. Installation Task 1: Install the E-mail Router and, optionally, the Rule Deployment Wizard. For more information, see "Install the E-mail Router" below. 2. Installation Task 2: Configure the E-mail Router. For more information, see Configure the E-mail Router in the Microsoft Dynamics CRM 2011 Installing Guide. 3. Installation Task 3: (Optional) Deploy Inbox Rules. For more information, see "Deploy Inbox Rules" in Configure the E-mail Router in the Microsoft Dynamics CRM 2011 Installing Guide. Important If you did not specify an incoming email server during Microsoft Dynamics CRM Server Setup, you must manually add the service account running the E-mail Router service to the PrivUserGroup security group. The PrivUserGroup security group is created during Microsoft Dynamics CRM Server Setup. For steps about how to add members to this group, see Troubleshooting E-mail Router issues in the Microsoft Dynamics CRM 2011 Installing Guide.

Install the E-mail Router

To install E-mail Router on a server named EXBE01 1. Meet the E-mail Router requirements specified in Microsoft Dynamics CRM E-mail Router hardware requirements and in Microsoft Dynamics CRM E-mail Router software requirements. 2. Log on to EXBE01 as a Domain User with Local Administrator privileges. 3. Obtain and run the appropriate installation files. To install from a network or from a DVD: Open the appropriate installation folder (..\EmailRouter\amd64 for 64-bit or ..\EmailRouter\i386 for 32-bit) and then run the SetupEmailRouter.exe file. To install from the Web, open the download page (Microsoft Dynamics CRM 2011) and then download and run the executable file. Note The download site may present you with a choice of executable files. If you are installing on a 64-bit computer, choose a file with a name such as DynamicsCRMEmail_1033_amd64.exe. For a 32-bit computer, the file name 87

is similar to DynamicsCRMEmail_1033_i386.exe. 4. If a Security Warning dialog box appears, click Run. 5. On the Welcome to Microsoft Dynamics CRM 2011 E-mail Router setup page, select whether you want to update E-mail Router setup. We recommend that you click Get updates for Microsoft Dynamics CRM. Then, click Next. 6. On the License Agreement page, review the information and if you accept the license agreement, click I accept this license agreement, and then click I Accept. 7. If required components are missing, the Install Required Components page appears. If this page does not appear, all required components are installed, and you can skip to the next step in the installation procedure. If required components are listed, you can install them now. Click Install. After the components are installed, the status column changes from Not Installed to Installed. Click Next to continue. Note These components are required before the E-mail Router can be installed. You can exit Setup and install the components manually, or select Install. The Next button on this page is disabled until Setup detects that these components are installed. Setup might require connection to the internet if the required component setup binary files are not found on your computer. Although installation of certain components requires a computer restart, the computer is not restarted automatically. Setup installs the required components and then waits for your input. At this point, quit the setup process, restart the computer, and continue the E-mail Router installation by running SetupEmailRouter.exe again. 8. On the Select Router Components page, select either or both options, and then click Next. 9. Microsoft Dynamics CRM E-mail Router Service. This option installs the E-mail Router service and E-mail Router Configuration Manager. Rule Deployment Wizard. This option installs the Rule Deployment Wizard. Optionally, you can install this wizard on any computer in the Active Directory Domain of the Exchange Server. Caution 88

On the Select Router Components page, if you clear the option of a component that has already been installed, that component will be uninstalled. 10. On the Select Install Location page, either accept the Default file installation directory or Browse to indicate a different location, and then click Next. 11. The System Checks page appears. This page is a summary of all system requirements for a successful E-mail Router installation. Verification errors must be corrected before the installation can continue. If there is a problem that will take time to correct, cancel Setup at this point, fix the problem, and restart Setup. When no verification errors remain, click Next. 12. The Ready to Install page appears. Review the installation selections that you have made. Click Back to change your selections, or Install to install now. 13. After E-mail Router Setup is finished installing files, click Finish.

Minimum permissions required to run the E-mail Router and the Rule Deployment Wizard
For E-mail Router, the following conditions must be met: The account that is running the E-mail Router must be LocalSystemAccount. The computer where the E-mail Router service is running must be added to the PrivUserGroup group. For the Rule Deployment Wizard, the following conditions must be met: The user must have logged on as a Microsoft Dynamics CRM user with a security role. The user must be a local administrator on the computer where the wizard is running. The user must have administrative permissions on the Exchange Server.

See Also
E-mail Router Upgrade the E-mail Router

89

Upgrade the E-mail Router

To upgrade your installation of the E-mail Router from Microsoft Dynamics CRM 4.0 to Microsoft Dynamics CRM 2011, you first back up the state files that are used by the E-mail Router, and then install the E-mail Router. Follow the steps in the following tasks: Upgrade Task 1: Back up and use E-mail Router state files and Smart Matching settings. For more information, see Back up and use E-mail Router state files below. Upgrade Task 2: Install the Microsoft Dynamics CRM 2011 E-mail Router. For more information, see Upgrade the E-mail Router to Microsoft Dynamics CRM 2011 below.

In This Topic
Upgrading both the E-mail Router and Microsoft Dynamics CRM Back up and use E-mail Router state files and Smart Matching settings Upgrade the E-mail Router to Microsoft Dynamics CRM 2011

Upgrading both the E-mail Router and Microsoft Dynamics CRM

If you plan to upgrade both the E-mail Router and Microsoft Dynamics CRM, perform the upgrade tasks in the following order:

1. Stop the Microsoft Dynamics CRM E-mail Router service. To do this, on the Start menu, type services.msc, and then press ENTER; or click Run, type services.msc, and then press ENTER. Right-click the Microsoft Dynamics CRM E-mail Router service, and then click Stop. 2. Upgrade Microsoft Dynamics CRM 4.0 Server to Microsoft Dynamics CRM Server 2011. For more information, see Upgrade from Microsoft Dynamics CRM 4.0 in the Microsoft Dynamics CRM 2011 Installing Guide. 3. Install the Microsoft Dynamics CRM 2011 E-mail Router: If you already have the Microsoft Dynamics CRM 4.0 E-mail Router installed, upgrade to the Microsoft Dynamics CRM 2011 E-mail Router, as described below. If you do not have the Microsoft Dynamics CRM 4.0 E-mail Router installed, install the Microsoft Dynamics CRM 2011 E-mail Router, as described in Install E-mail Router 90

and Rule Deployment Wizard in the Microsoft Dynamics CRM 2011 Installing Guide.

4. You might need to restart the Microsoft Dynamics CRM E-mail Router service after the upgrade to the Microsoft Dynamics CRM 2011 E-mail Router finishes. To do this, in the services list, right-click Microsoft Dynamics CRM E-mail Router, and then click Start.

Back up and use E-mail Router state files and Smart Matching settings
We recommend that you back up the files that store the state of your E-mail Router before you upgrade to the Microsoft Dynamics CRM 2011 E-mail Router. The following steps describe how to back up and use these files to recover from a failed upgrade to the next version of the E-mail Router.

To back up and use E-mail Router state files 1. Locate the following files in the folder <drive:>\Program Files\Microsoft CRM Email\Service\: Microsoft.Crm.Tools.EmailAgent.Configuration.bin Microsoft.Crm.Tools.EmailAgent.SystemState.xml Microsoft.Crm.Tools.EmailAgent.xml Microsoft.Crm.Tools.Email.Management.config EncryptionKey.xml 2. Copy these files to a safe location. 3. If you have modified the smart matching email correlation settings that are located in the HKEY_LOCAL_MACHINE\Software\Microsoft\MSCRM Windows Registry, you must add the effective change in the System Settings area of the Microsoft Dynamics CRM 2011 application. The smart matching settings are no longer maintained in the Windows Registry and must be modified in the application. For more information about how to change smart matching settings in Microsoft Dynamics CRM 2011, see the Microsoft Dynamics CRM Help. The subkey names and default values are: HashFilterKeywords. ^[\s]*([\w]+\s?:[\s]*)+ HashMaxCount. 20 HashDeltaSubjectCount. 0

91

 HashMinAddressCount. 2 4. Perform the upgrade to Microsoft Dynamics CRM 2011 E-mail Router. For more information, see the following procedure, "To upgrade the E-mail Router on a server named EXBE01" below. 5. If the E-mail Router upgrade succeeds, you can discard the backup files and exit this procedure. If the E-mail Router upgrade fails, continue with the following procedure. If the upgrade fails 1. If the upgrade fails, you have to uninstall the E-mail Router. For more information, see Uninstall, change, or repair E-mail Router in the Microsoft Dynamics CRM 2011 Installing Guide. 2. Reinstall the Microsoft Dynamics CRM 4.0 E-mail Router. 3. Reinstall all of the Microsoft Dynamics CRM update rollups that were installed before you attempted this upgrade. For more information, see Microsoft Dynamics CRM 4.0 updates and hotfixes. Note If you previously installed Microsoft Dynamics CRM 2011 Update Rollup 7 or later, you need not reinstall any of the individual Microsoft Dynamics CRM update rollups that preceded Microsoft Dynamics CRM 2011 Update Rollup 7. Instead, reinstall Microsoft Dynamics CRM 2011 Update Rollup 7 and then reinstall the latest Microsoft Dynamics CRM update rollup (such as Microsoft Dynamics CRM 2011 Update Rollup 9) that had been installed before you attempted to upgrade the E-mail Router. 4. Stop the E-mail Router service. For more information, see "To stop a service," in Incoming e-mail configuration issues in the Microsoft Dynamics CRM 2011 Installing Guide. 5. Copy the backed-up files to the installation location of Microsoft Dynamics CRM 4.0 Email Router. (This might be the original installation location: <drive>:\Program Files\Microsoft CRM Email\Service.) 6. Start the E-mail Router service. For more information, see "To start a service," in Incoming e-mail configuration issues in the Microsoft Dynamics CRM 2011 Installing Guide.

92

Upgrade the E-mail Router to Microsoft Dynamics CRM 2011

To upgrade the E-mail Router on a server named EXBE01 1. Meet the E-mail Router requirements specified in Microsoft Dynamics CRM E-mail Router hardware requirements and in Microsoft Dynamics CRM E-mail Router software requirements. 2. Log on to EXBE01 as a Domain User with Local Administrator privileges. 3. Obtain and run the appropriate installation files. To install from a network or from a DVD: Open the appropriate installation folder (EmailRouter\amd64 or EmailRouter\i386) and then run the SetupEmailRouter.exe file. (To install on a 64-bit computer, use the Setup file in the EmailRouter\amd64 folder; to install on a 32-bit computer, use the Setup file in the EmailRouter\i386 folder.) To install from the web, open the download page (Microsoft Dynamics CRM 2011) and then download and run the executable file. Note The download site may present you with a choice of executable files. If you are installing on a 64-bit computer, choose a file with a name such as DynamicsCRMEmail_1033_amd64.exe. For a 32-bit computer, the file name is similar to DynamicsCRMEmail_1033_i386.exe. 4. If a Security Warning dialog box appears, click Run. 5. On the Welcome to Microsoft Dynamics CRM 2011 E-mail Router setup page, select whether you want to update E-mail Router setup. We recommend that you click Get updates for Microsoft Dynamics CRM. Then, click Next. 6. On the License Agreement page, review the information and if you accept the license agreement, click I accept this license agreement, and then click I Accept. 7. On the Select Router Components page, click Next. 8. The System Checks page appears. This page is a summary of all system requirements for a successful E-mail Router installation. Verification errors must be corrected before the installation can continue. If there is a problem that will take time to correct, cancel Setup at this point, fix the problem, and restart Setup. When no verification errors remain, click Next. 9. The Ready to Upgrade page appears. Review the installation selections that you have 93

made. Click Back to change your selections, or Upgrade to upgrade the E-mail Router now. 10. After E-mail Router Setup is finished, click Finish. Your configuration settings from the previous installation have been retained. To change configuration settings, run the E-mail Router Configuration Manager. For more information, see Configure the E-mail Router in the Microsoft Dynamics CRM 2011 Installing Guide.

See Also
Install E-mail Router and Rule Deployment Wizard Configure the E-mail Router

Configure the E-mail Router

This content applies to both the on-premises deployment of Microsoft Dynamics CRM 2011 and Microsoft Dynamics CRM Online. Content for a specific deployment will be noted. After the E-mail Router has been installed, you can configure it. Some of these configuration tasks are mandatory. Others are optional in that you use them to enable the following functionality: Configuration Task 1: Set up profiles and (optionally) set up deployments, by using the E-mail Router Configuration Manager. For more information, see "E-mail Router Configuration Manager" later in this topic. Configuration Task 2: Microsoft Dynamics CRM users must have their incoming email access type set to E-mail Router. For more information, see "Set e-mail access type" later in this topic. Configuration Task 3: (Optional) As part of configuration, you can deploy rules. For more information, see "Deploy Inbox Rules" later in this topic. Configuration Task 4: (Optional) As part of configuration, you can set up a forward mailbox. For more information, see "Set up a Forward Mailbox" later in this topic.

In This Topic
E-mail Router Configuration Manager Keep user credentials secure

94

Set email access type Deploy inbox rules Set up a forward mailbox

E-mail Router Configuration Manager

The E-mail Router Configuration Manager is a tool that you use to configure the E-mail Router. The E-mail Router Configuration Manager is installed with the E-mail Router and can be run after the E-mail Router Setup is completed. The E-mail Router settings configured by using the E-mail Router Configuration Manager are saved in the Microsoft.Crm.tools.EmailAgent.xml file that is located in the folder where the Email Router is installed. The E-mail Router has several options. Before you run the E-mail Router Configuration Manager, you should determine how you want to configure these options: Incoming Configuration. The Microsoft Dynamics CRM E-mail Router supports Exchange Server 2003, Exchange Server 2007, Exchange Server 2010, Exchange Online, or POP3 email systems for incoming email messages. Outgoing Configuration. Microsoft Dynamics CRM supports only Exchange Online or SMTP email systems for outgoing email messages. Mailbox Monitoring Type. You can configure the following two mailbox types: Forward Mailbox. If you select Forward Mailbox when you run the E-mail Router Configuration Manager, the E-mail Router uses a single mailbox to process email messages. Then, for each Microsoft Dynamics CRM user or queue that will receive email messages, you must create a rule for the user or queue by running the Rule Deployment Wizard. E-mail Router. If email messages can be forwarded as attachments, but your email system does not allow rules, you must configure each user to use the E-mail Router setting. If you are using Exchange Server, we recommend that you use Forward Mailbox Monitoring. For more information about E-mail Router options, see Planning Deployment in the Planning Guide. Also, see the E-mail Router Configuration Manager Help, which you can open by clicking Help on the Configuration Profiles or the Deployments tab in the E-mail Router Configuration Manager.

95

To start the E-mail Router Configuration Manager, click Start, point to All Programs, point to Microsoft Dynamics CRM E-mail Router, and then click Microsoft Dynamics CRM E-mail Router Configuration Manager.

Configuration profiles
You must configure at least one incoming email profile and one outgoing email profile to enable the E-mail Router to route email to and from your Microsoft Dynamics CRM organization. Depending on the complexity of your organizations email system, you may have to create multiple incoming and outgoing configuration profiles. For example, if your organization requires incoming E-mail Router services for multiple email servers, you must create one incoming configuration profile for each email server. Important Due to performance throttling when accessing Exchange Online, the E-mail Router should not be configured to use the on-premises deployments of Microsoft Exchange Server or POP3 accounts when a profile is also configured for Exchange Online. If you must communicate with both Exchange Online and an Exchange Server On-Premises or POP3 email server, you can do so by using multiple instances of the E-mail Router (you can install only one instance of the E-mail Router on a computer). Connecting to Exchange Server On-Premises and POP3 email servers by using multiple profiles from the same E-mail Router instance is supported.

Authentication types
You must specify the type of authentication the E-mail Router will use for each incoming and outgoing email profile. For Exchange Server, incoming profiles support Windows authentication only. For POP3compliant servers, incoming profiles support NTLM and clear text authentication. Tip You can configure the E-mail Router to use POP3 protocol with Exchange Server. However, the Exchange Server POP3 service is disabled by default. For information about how to enable POP3, see the Exchange Server documentation. Important Clear text authentication transmits unencrypted user names and passwords. If you use clear text authentication, we recommend that you do this only with Secure Sockets Layer (SSL). Select the Use SSL and set the Network Port field (on the Advanced tab) to 96

a value that is appropriate for your environment. (If you specify Exchange Online, the Use SSL option is not available because you can connect to Exchange Online only over an https connection.) Verify your POP3 server requirements with your email administrator. Depending on the type of email server that you use to process incoming email, select one of the following authentication types: Note Anonymous SMTP is only valid for internal, non-Internet-facing SMTP servers. Many SMTP servers do not support Anonymous authentication. To ensure uninterrupted email flow from the E-mail Router, verify your SMTP server requirements with your email administrator. Windows Authentication. This is the only authentication type available if you use Microsoft Exchange Server for incoming email. NTLM. This option is available only if you use a POP3-compliant server for incoming email. Clear Text. This option is available if you use either a POP3-compliant server or Microsoft Exchange Online for incoming email. For Microsoft Exchange Online, this is the only authentication type available.

Access credentials
Depending on how you set the other configuration profile options, the following options are available for specifying the user name and password that the E-mail Router will use to access each mailbox that the profile serves. Important If you use access credentials that are valid for the email server but not for a particular mailbox, a "401 access denied" error is generated when you test access. Incoming profiles support the following access credentials: Local System Account. This option requires a machine trust between the computer where the E-mail Router is running and the computer where Microsoft Exchange Server is running. For incoming profiles, this option is available only for Exchange Server (not for Exchange Online or other POP3 compliant email servers). User specified. This option is available only in the on-premises version of the product. This option is available for all email server types, protocols, and authentication types. 97

This option requires that each user enter a user name and password in the Set Personal Options dialog box (available in the Workplace section of the Microsoft Dynamics CRM web client). This enables the E-mail Router to monitor mailboxes by using each user's access credentials. When a user changes a domain password -- for example, when it expires -- the user must update the password in Microsoft Dynamics CRM so that the E-mail Router can continue to monitor the mailbox. This option is available for Exchange Server, Exchange Online and other POP3 compliant email servers. Other specified. Select this option if you want the E-mail Router to authenticate by using the credentials of a specified user. This option is available for all email server types, protocols, and authentication types. The specified user must have full access to all the mailboxes that the incoming profile will serve. To specify multiple sets of access credentials, you must create a separate configuration profile for each specified user. Outgoing profiles support the following access credentials. For more information, see the E-mail Router Configuration Manager Help. Local System Account. Select this option if you select SMTP as the email server type and you want to authenticate by using the local system account of the computer where the E-mail Router is running. This option requires a machine trust between the computer where the Email Router is running and the computer where the Exchange Server is running. For more information, see Securing Exchange Server and Outlook in Operating system and software component security considerations in the Planning Guide. If you select this option, either the E-mail Router must be installed on the same server as the Microsoft Dynamics CRM Server 2011, or the E-mail Router computer name must have been entered during Microsoft Dynamics CRM Server Setup. This option is available only when you select SMTP as the email server type, and Windows Authentication or Anonymous as the authentication type. User Specified. This option is available in the on-premises and Service Provider editions of Microsoft Dynamics CRM, and when you are using Exchange Online as the Exchange Server Type. Select this option if you want the E-mail Router to authenticate by using an individual user account or a mailbox. Other Specified. This option enables the administrator to configure the E-mail Router to send email messages on each user's behalf by using the access credentials of a specified user account. The specified user must have full access to all the mailboxes that the incoming profile will serve. To specify multiple sets of access credentials, you must create a separate configuration profile for each specified user. This option is not available if you select SMTP as the email server type and Anonymous as the authentication type. User Type. If you select Exchange Online as the email server type and Other Specified as the access credentials, you must select either Administrator or User as the user type. Select 98

Administrator if you want to use a single set of credentials to process multiple mailboxes, or if you want to provide a different set of email credentials to process individual mailboxes. Access Type. If you select Exchange Online as the email server type, Other Specified as the access credentials, and Administrator as the user type, you must select either Delegate Access or Send as as the access type. Note Delegate Access causes email to be sent as "Send on behalf of" messages. Send as causes email to be sent as "Send As" messages.

Deployments
You can link a configuration profile of the E-mail Router to Microsoft Dynamics CRM Online. It is not mandatory, but doing so provides the benefit of assigning the configuration profile to users for whom no other profile is assigned. You must select the type of Microsoft Dynamics CRM system that the E-mail Router will connect to. The following options are available: My company. Select this option if Microsoft Dynamics CRM is deployed at your company. An online service provider. Select this option if the deployment that the E-mail Router will connect to is an online service provider deployment of Microsoft Dynamics CRM. Microsoft Dynamics CRM Online. Select this option to connect the E-mail Router to a Microsoft Dynamics CRM Online organization.

Microsoft Dynamics CRM Server

Type the URL of the Microsoft Dynamics CRM Server 2011. If you are connecting to an on-premises version at your company, the format is similar to http://myCRMServer:5555/OrganizationUniqueName. If you are connecting to a service provider deployment, contact your service provider to obtain the correct URL. For more information, see the documentation for service providers that is available from the Microsoft Download Center. If you are connecting to Microsoft Dynamics CRM Online and your organization uses Microsoft account, enter: https://dev.crm.dynamics.com/<OrganizationName> where OrganizationName is a placeholder for the actual ID of your organization.

99

 If you are connecting to Microsoft Dynamics CRM Online and your organization uses Microsoft Office 365, enter: https://disco.crm.dynamics.com/<OrganizationName> where OrganizationName is a placeholder for the actual ID of your organization. Important Make sure that the URL of the Microsoft Dynamics CRM deployment is spelled correctly. The OrganizationUniqueName part of the URL must be spelled exactly as it appears in the Microsoft Dynamics CRM server. To determine the OrganizationUniqueName, start the Microsoft Dynamics CRM web application as a user who has the System Customizer role. Click Settings, and then click Customizations. On the Customization page, click Developer Resources. The OrganizationUniqueName is displayed below the Organization Unique Name label.

One deployment type at a time

There are two types of deployments. One type includes deployments to Microsoft Dynamics CRM Online only. The other type includes deployments to either My company or An online service provider. If you define multiple deployments for the E-mail Router, they must all be of the same type. That is, after you have created a deployment that uses one deployment type, any other deployments that you create must be of the same type. (To create a deployment of the other type, you must first delete all of the deployments that currently exist.)

Obtaining user e-mail credentials from Microsoft Dynamics CRM

In certain circumstances, the E-mail Router must obtain user credentials from Microsoft Dynamics CRM. However, Microsoft Dynamics CRM stores user names and passwords only when HTTPS has been selected as the protocol that the E-mail Router will use to access Microsoft Dynamics CRM. You can change this behavior so that Microsoft Dynamics CRM can store and distribute user names and passwords to the E-mail Router over HTTP. For more information, see HTTP Option in Keep user credentials secure later in this topic.

Access Credentials
You must specify the access credentials that the E-mail Router will use to log on to Microsoft Dynamics CRM Server 2011. To use the Local System Account (available only if you select My company as the deployment type), either the E-mail Router must be installed on the same computer as the Microsoft Dynamics CRM Server 2011, or the computer where the E-mail Router is installed must be a member of the Active Directory PrivUserGroup security group. 100

Tip For an on-premises deployment of Microsoft Dynamics CRM 2011, the computer will already be added to the PrivUserGroup security group if you specified the E-mail Router computer during Microsoft Dynamics CRM Server 2011 Setup.

Configuring E-mail Routing for Multiple Configurations and Deployments

You can add or edit an E-mail Router configuration, which contains a single incoming and outgoing method that routes email to the email server. In the configuration, you must specify the following: A name of the configuration profile, for display and reference. The direction of the configuration profile: incoming or outgoing. The email transport type, such as Exchange or POP3 for incoming, and SMTP for outgoing. You can also add or edit E-mail Router deployments. An E-mail Router deployment contains a URL to a Microsoft Dynamics CRM Server 2011 computer, one incoming configuration, and one outgoing configuration. In an E-mail Router deployment object, you specify the following components: A URL to the Microsoft Dynamics CRM Server 2011 computer (required). A default incoming configuration (optional). A default outgoing configuration (optional). To specify additional operational settings for a new or existing configuration profile, click Advanced on the E-mail Router Configuration Manager dialog box. For more information, see the E-mail Router Configuration Manager Help.

Keep user credentials secure

If your organization uses the E-mail Router to send and receive messages on behalf of users or queues, you should increase security. You can do this either by using the HTTPS protocol or by enabling IPsec. Note This issue applies only to users of the on-premises deployment of Microsoft Dynamics CRM 2011.

101

HTTPS option
In processing email for a user or queue, the E-mail Router requires credentials for the user or queue. Those credentials can be entered in the Microsoft Dynamics CRM web application in the Set Personal Options dialog box (for users) and in the Queues form (for queues). Microsoft Dynamics CRM stores these credentials in encrypted form in the Microsoft Dynamics CRM database. The E-mail Router uses a key stored in the Microsoft Dynamics CRM database to decrypt these credentials. The call that the E-mail Router makes to obtain this key enforces HTTPS. In Microsoft Dynamics CRM 2011, the E-mail Router functions this way by default, which means that you need not take any action to retain this behavior. However, if you do not want to use HTTPS, you must set a particular Windows registry key, as described in the following section.

HTTP option
If you do not want to use HTTPS, you must set a Windows registry key, as follows: 1. On the Microsoft Dynamics CRM Server 2011, check the value of the registry key DisableSecureDecryptionKey at the path HKLM\Software\Microsoft\MSCRM. If this registry key is present, set its value to 1. (If the key is not present or set to 0, calls from the E-mail Router to the Microsoft Dynamics CRM Server 2011 are made using HTTPS.) Setting the value of this key to 1 allows the E-mail Router to obtain information from the Microsoft Dynamics CRM database over the HTTP protocol. 2. If you changed the value of DisableSecureDecryptionKey, do the following on the Microsoft Dynamics CRM Server 2011: Restart Internet Information Services (IIS). To do this, click Start, click Run, type IISRESET, and then click OK. 3. (Recommended) Enable IPsec for all communications between the Microsoft Dynamics CRM Server 2011 and the E-mail Router computer. For more information about enabling IPsec, see IPSec.

Managing certificates to use the E-mail Router with HTTPS

If you are running Microsoft Dynamics CRM on HTTPS and one or more certificates is not signed by a certification authority, do the following on the computer on which the E-mail Router is installed: For the Microsoft Dynamics CRM certificate 1. If the E-mail Router Service is configured to use the "LocalSystem" account, import the Microsoft Dynamics CRM certificate into the trusted store of the local machine account of the computer on which the E-mail Router is installed. 2. If the E-mail Router Service is configured to use any other specific user account, import the Microsoft Dynamics CRM certificate into the trusted store of that user's account on the computer on which the E-mail Router is installed. 102

For any Exchange Server certificates: 1. If the E-mail Router Service is configured to use the "LocalSystem" account, import the Exchange Server certificate into the trusted store of the local machine account of the computer on which the E-mail Router is installed. 2. If the E-mail Router Service is configured to use any other specific user account, import the Exchange Server certificate into the trusted store of that user's account on the computer on which the E-mail Router is installed.

Set email access type

Before a user can send and receive email messages that will be tracked in Microsoft Dynamics CRM, you must change the email access type that is set for that user, as described in the following procedure.

To set the email access type 1. Open the Microsoft Dynamics CRM web application. 2. In the Navigation Pane, click Settings. 3. Under System, click Administration. 4. In the Administration area, click Users. 5. Find the user whose settings you want to edit. You may need to navigate to a different page. 6. Click the name of the user, or select the user and then click Edit. The User form opens. You can edit the messaging options in the E-mail Access Configuration section. Note By default, Microsoft Dynamics CRM sets both the incoming email access type and the outgoing e-mail access type to "Microsoft Dynamics CRM for Outlook." 7. For each user of the Microsoft Dynamics CRM web application whose mail will be routed by the E-mail Router, you must change the incoming type to E-mail Router or to Forward Mailbox, and the outgoing type to E-mail Router.

Connect the E-mail Router to Microsoft Dynamics CRM Online

Set the E-mail Router to work with Microsoft Dynamics CRM Online 103

1. Start the E-mail Router Configuration Manager. 2. Click the Deployments tab. 3. Click New to create a new deployment. 4. Make sure that the Deployment option is set to Microsoft Dynamics CRM Online. If the Microsoft Dynamics CRM Online option is not available, delete the existing deployments as explained in the following note: Note There are two types of deployments. One type includes deployments to Microsoft Dynamics CRM Online only. The other type includes deployments to either My company or An online service provider. If you define multiple deployments for the E-mail Router, they must all be of the same type. That is, after you have created a deployment that uses one deployment type, any other deployments that you create must be of the same type. (To create a deployment of the other type, you must first delete all of the deployments that currently exist.) 5. Enter the rest of the information required to define the deployment and then click OK to finish.

Deploy inbox rules

An important part of routing email messages to your Microsoft Dynamics CRM system is the placement of an Microsoft Exchange Server inbox rule in the inbox of each Microsoft Dynamics CRM user or queue. This rule sends a copy of each message that is received by a Microsoft Dynamics CRM user to the Microsoft Dynamics CRM system mailbox. From the Microsoft Dynamics CRM system mailbox, the E-mail Router retrieves the messages and creates an email activity in Microsoft Dynamics CRM. To deploy these Microsoft Dynamics CRM user inbox rules, use the Rule Deployment Wizard, which can be run at any time to add or change the inbox rules for your Microsoft Dynamics CRM users. Important The Rule Deployment Wizard can deploy rules only to Exchange Server mailboxes. You cannot use the Rule Deployment Wizard to deploy rules to POP3 email servers. Note 104

For information about installing the Rule Deployment Wizard, see Install E-mail Router and Rule Deployment Wizard in this guide. If you chose to install this wizard as part of the E-mail Router installation, you can access this wizard by doing the following: On the computer where you have installed the Rule Deployment Wizard, click Start, point to All Programs, point to Microsoft Dynamics CRM E-mail Router, and then click Rule Deployment Wizard. The Rule Deployment Wizard does not have to be run on a computer with an instance of Exchange Server. To run the Rule Deployment Wizard, you must: Be logged on as a Microsoft Dynamics CRM user with a security role. (Users can be in restricted access mode). Be a local administrator on the computer where the wizard is running. Have Exchange Server administrative permissions. To deploy rules to the mailbox of a Microsoft Dynamics CRM user, the person running the Rule Deployment Wizard must have Exchange Server administrative permissions for the mailbox. Use the Exchange System Manager and the Exchange Server delegation wizard to designate Exchange Server administrators. Or, make sure that the person running the Rule Deployment Wizard has full permissions on the Exchange Server mailbox store or storage group in which the users' mailboxes are located.

Create the rule manually

For POP3 email servers that support email system rules where an email message can be forwarded as an attachment, you can create the rule manually. Note Before you can specify a forward mailbox in a rule, you must create a mailbox and designate it as a forward mailbox. For more information, see Specify a Forward Mailbox in the E-mail Router Configuration Manager Help.

To create the rule manually in Microsoft Office Outlook 1. On the Tools menu, click Rules and Alerts. (In Office 2010, on the Home tab, click Rules, and then click Manage Rules & Alerts.) The Rules and Alerts dialog box appears. 2. On the E-mail Rules tab, click New Rule. 105

3. Under Step 1: Select a template, in the Start from a blank rule section, click Apply rule on messages I receive, and then click Next. 4. Under Step 1: Select conditions, select where my name is in the To box, and then click Next. 5. Under Step 1: Select actions, select forward it to people or public group as an attachment. 6. Under Step 2: Edit the rule description (click and underlined value), click people or public group. 7. Select the name of your E-mail Router forward mailbox, and then click OK. 8. Click Next two times. 9. Optionally, under Step 1: Specify a name for this rule, change the name of the rule. 10. Make sure that the Turn on this rule option is selected, and then click Finish. 11. Make sure that the rule is at the top of the list, and then click Apply.

Set up a forward mailbox

The forward mailbox is used as a collection box for email messages that are transferred from each Microsoft Dynamics CRM users mailbox by a server-side rule. The forward mailbox must be dedicated to the E-mail Router system, and should not be used as a working mailbox by an individual user. Before you specify a forward mailbox, you must create or use an existing Exchange Server or POP3 mailbox that can be dedicated to processing email messages that are tracked by Microsoft Dynamics CRM. After you specify the forward mailbox, you can run the Rule Deployment Wizard to deploy the rules that will be used to forward email messages to the forward mailbox. Note If you specify a POP3 mailbox as the forward mailbox, you must manually deploy the rules. The Rule Deployment Wizard cannot deploy rules to a POP3 email server. For information about how to deploy rules manually, see Create the rule manually above.

Specify or modify a forward mailbox 1. Make sure that you have a mailbox to dedicate as the forward mailbox. If you do not, see your messaging server documentation for information about how to create a mailbox. If you select Exchange Server as the incoming email server type, you must log 106

on to the mailbox by using an email client such as Microsoft Office Outlook or Outlook Web Access (OWA) at least once to complete the creation of the mailbox. 2. Click the Users, Queues, and Forward Mailboxes tab, and then click Load Data. 3. When the list appears, click the Forward Mailboxes tab, and then click New. To change an existing forward mailbox, click Modify. 4. In the Forward Mailbox dialog box, complete the following boxes, and then click OK: Name. Type a name for the forward mailbox. This will be used to display in the Email Router Configuration Manager and the Rule Deployment Wizard. Email Address. Type the email address for the forward mailbox, such as forwardmailbox@contoso.com. Incoming Configuration Profile. Select the incoming configuration profile to associate with the forward mailbox. You can have multiple forward mailboxes that use different incoming configuration profiles. Note To delete email messages in the forward mailbox after they have been processed by the E-mail Router, select the Delete messages in forward mailbox after processing option. 5. Click Publish. 6. Stop the Microsoft CRM Email Router service. To do this, on the Start menu, type services.msc, and then press ENTER; or click Run, type services.msc, and then press ENTER. Right-click the Microsoft CRM Email Router service, and then click Stop. 7. Restart the Microsoft CRM Email Router service. To do this, in the services list, right-click Microsoft CRM Email Router, and then click Start. 8. Click OK, and then close the Services application.

Complete the forward mailbox

If you will use a forward mailbox to route email messages, in Active Directory directory service, you must create the user and mailbox that will be used for the E-mail Router forward mailbox. Important You must log on to the forward mailbox at least one time before the E-mail Router can use it to process email messages.

107

See Also
Upgrade the E-mail Router Install E-mail Router on multiple computers

Install E-mail Router on multiple computers

You can deploy and run the Microsoft Dynamics CRM E-mail Router on multiple computers in a Microsoft cluster to provide high availability and failover functionality. In Windows Server 2003 this kind of server cluster is known as server clustering and in Windows Server 2008 it is known as failover clustering. Both of these server clustering technologies are supported with the E-mail Router. To implement the minimum configuration for a cluster with failover capabilities, you must have the following hardware and configuration: At least two nodes running Windows Server that support clustering. A common storage I/O technology between the nodes in the cluster, such as Parallel SCSI or Fibre Channel. The cluster configured in an active/passive manner. To install and run the E-mail Router in a failover cluster environment, follow these steps in the order listed.

In This Topic
Step 1: Establish the cluster Step 2: Install the E-mail Router to the active primary node in the cluster Step 3: Install the E-mail Router to the passive node in the cluster Step 4: Create the generic resource service for the cluster Step 5: Verify and monitor the cluster

Step 1: Establish the cluster

To install and configure the cluster 108

1. Install the minimum configuration of a two-node cluster with a shared disk. 2. Configure the cluster as active/passive. The E-mail Router does not support an active/active cluster deployment. For more information, see Failover Clusters and Designing and Deploying Server Clusters.

Step 2: Install the E-mail Router to the active primary node in the cluster
Install and configure the E-mail Router on the active primary node in the cluster 1. Run E-mail Router Setup on the active primary node in the cluster. Important You do not have to install the E-mail Router on a computer that is running Microsoft Exchange Server. We recommend that you install the E-mail Router as the only application on Windows Server 2003 or Windows Server 2008 computers in the cluster or in an existing cluster that is operating with a light load. Installing the E-mail Router on nodes operating in an active/active cluster, such as an Exchange Server active/active cluster, is not supported. 2. Start the E-mail Router Configuration Manager on the first node and configure the Email Router. Verify that the E-mail Router is routing messages correctly. 3. Copy all E-mail Router application files to the common storage or shared hard disk. By default, the E-mail Router files are located at <drive:>\Program Files\Microsoft CRM Email. The following files must be located on the common storage or shared disk so that they can be moved to the secondary node in the event of a failover: Microsoft.Crm.Tools.EmailAgent.Configuration.bin Microsoft.Crm.Tools.EmailAgent.SystemState.xml Microsoft.Crm.Tools.EmailAgent.xml Microsoft.Crm.Tools.Email.Management.config EncryptionKey.xml

109

Important The E-mail Router files should be manually secured on the common storage or shared disk. We recommend that you grant full control only to the service account running the E-mail Router service ("Microsoft CRM Email Router") and to those administrators who might have to update configuration files manually. 4. Update the following Windows registry subkey so that the E-mail Router will use the shared disk to load the E-mail Router settings: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSCRMEmail To do this, change the ImagePath value to point to the common storage or shared disk drive where the E-mail Router files were copied. 5. Restart the "Microsoft CRM Email Router" service. To do this, on the Start menu, type services.msc, and then press ENTER; or click Run, type services.msc, and then press ENTER. In the services list, right-click the "Microsoft CRM Email Router" service, and then click Start. Close the Services application.

Step 3: Install the E-mail Router to the passive node in the cluster
Install and configure the E-mail Router on the passive secondary node in the cluster 1. Run E-mail Router Setup on the second node in the cluster. Important Do not run the E-mail Router Configuration Manager and do not copy the files to the common storage or shared hard disk as described in "Step 2: Install the Email Router to the active primary node in the cluster". 2. Update the Windows registry subkey as in the previously performed steps on the primary node. Repeat these steps for each additional node in the cluster. 3. Restart the "Microsoft CRM Email Router" service. To do this, on the Start menu, type services.msc, and then press ENTER; or click Run, type services.msc, and then press ENTER. In the services list, right-click the "Microsoft CRM Email Router" service, and then click Start. Close the Services application.

110

Step 4: Create the generic resource service for the cluster

To create a generic service resource for the cluster 1. On each node in the cluster, start the Services MMC snap-in. In the list of services, rightclick "Microsoft CRM Email Router," click Properties, and then set Startup type to Manual. Close the Services MMC snap-in. 2. Start Active Directory Users and Computers. Locate the PrivUserGroup {GUID} security group for the deployment. Add the computer accounts for each node in the cluster. Close Active Directory Users and Computers. 3. If you are using Windows Server 2003, start Cluster Administrator or, if you are using Windows Server 2008, start Failover Cluster Manager, and create a generic service resource. Use the following parameters: Name: Create a descriptive name for the generic service resource, such as MSCRM E-mail Router. Resource type: Generic Service Group: Cluster Group Possible owners: Add all nodes in the cluster. Dependencies: If you are using Microsoft Exchange Server and you have installed the E-mail Router on the Exchange Server (not recommended), add Exchange Server Information Store. Service Name: Microsoft CRM Email Router Start Parameters: Leave blank. Use Network Name for Computer Name: Leave unchecked. Do not checkpoint any Registry keys. 4. Bring the resource online. If necessary, configure the resource properties, such as the failover policies. 5. Close Cluster Administrator or Failover Cluster Manager. For more information about how to create a generic service resource, see Checklist: Installing a Generic Service resource.

111

Step 5: Verify and monitor the cluster

During a failover of node 1 (the primary node), node 2 (the secondary node) will become the primary node and the common storage or shared disk resources described in Step 2: Install the E-mail Router to the active primary node in the cluster" will move from node 1 to node 2. To test for failover, start Cluster Administrator or Failover Cluster Manager and force a failover.

See Also
Install E-mail Router and Rule Deployment Wizard Troubleshooting E-mail Router issues

Troubleshooting E-mail Router issues

This section provides guidelines for troubleshooting issues that you might encounter as you deploy and configure the E-mail Router.

In This Section
E-mail Router installation issues Incoming e-mail configuration issues Outgoing e-mail configuration issues Users do not receive Microsoft Dynamics CRM e-mail messages Test Access feature

See Also
Install E-mail Router and Rule Deployment Wizard

E-mail Router installation issues

This section provides troubleshooting guidelines and reference information about how to resolve issues that can occur during E-mail Router installation. Note 112

You can upgrade from the Microsoft Dynamics CRM 4.0 E-mail Router to the Microsoft Dynamics CRM 2011 E-mail Router without first needing to uninstall. Upgrading without uninstalling is supported only when moving from version 4.0 of the E-mail Router, but not when upgrade from versions earlier than 4.0. Keep your Microsoft Dynamics CRM deployment current by installing the latest updates and hotfixes automatically from Microsoft Update. You can also search for updates on the Microsoft Download Center. Choosing Microsoft Update lets you install recommended updates automatically and without administrator permissions.

To troubleshoot an E-mail Router installation 1. Verify that your operating environment meets all hardware and software requirements. For detailed requirements, see Microsoft Dynamics CRM E-mail Router hardware requirements and Microsoft Dynamics CRM E-mail Router software requirements in the Planning Guide. 2. Make sure that you follow the E-mail Router installation instructions in the Microsoft Dynamics CRM 2011 E-mail Router Installation Instructions in this guide. For more information about installation limitations and known issues, see the E-mail Router Known Issues section in the Microsoft Dynamics CRM 2011 and Microsoft Dynamics CRM Online Readme.

Logging (E-mail Router)

If a problem occurs during E-mail Router Setup, review the log file for information. By default, the E-mail Router Setup log is named crm50emailroutersetup.log and is located in the C:\Documents and Settings\<user>\Application Data\Microsoft\MSCRM\Logs folder on the computer where the E-mail Router is installed.

See Also
Troubleshooting E-mail Router issues Incoming e-mail configuration issues

113

Incoming e-mail configuration issues

This section provides troubleshooting guidelines and reference information about how to resolve some commonly encountered issues that can occur during E-mail Router incoming profile configuration.

To troubleshoot an E-mail Router incoming profile configuration 1. Make sure that you follow the incoming profile configuration procedures in the E-mail Router Configuration Manager Help. 2. For more information about how to configure an incoming profile, see Configure the Email Router in the Microsoft Dynamics CRM 2011 Installing Guide. 3. See the following sections for information about how to resolve some commonly encountered issues with incoming configuration profiles.

In This Topic
Login timeout error Unauthorized access to the mailbox Mailbox not found (access test fails) Mailbox not found (access test succeeds) The E-mail Router service configuration parameter "EmailUser" is missing SSL/TLS error from E-mail Router Configuration Manager test access POP3 issues

Login timeout error

Symptom: When you click Test Access in the E-mail Router Configuration Manager, you receive the following HTTP error message: Incoming Status: Failure - The remote server returned an error: (440) Login Timeout This is typically caused by trying to use forms-based authentication instead of Windows authentication (the only supported authentication method).

114

Resolution: Change the authentication mode to Windows authentication on the mailbox server. For more information, see the Microsoft Knowledge Base (KB) article 954047. Note Make sure that you point the incoming profile to the Exchange Server that has the mailbox server where the Exadmin and Exchange virtual directories are located.

Unauthorized access to the mailbox

Symptom: When you click Test Access in the E-mail Router Configuration Manager, you receive the following HTTP error message: Incoming Status: Failure - The remote Microsoft Exchange e-mail server returned the error "(401) Unauthorized". Verify that you have permission to connect to the mailbox. Resolution: Verify the following: 1. Before you click Test Access, make sure that the user has logged on to the mailbox so that the mailbox is activated. 2. Make sure that you can receive e-mail messages in the mailbox. 3. In the Location section of the E-mail Router Configuration Profile dialog box, verify that the correct URL of the Exchange Server is entered. For example: https://myexchangeserver https://www.myexchangeserver.local https://myexchangeserver/EWS/Exchange.asmx Important Do not enter any additional characters at the end of the URL string, such as /OWA or /Exchange or even a / character. If you are using Secure Sockets Layer (SSL), be sure to use https in the URL instead of http. 4. Verify the settings in the Access Credentials section of the E-mail Router Configuration Manager incoming profile dialog box: Make sure that the specified user has full access rights to the mailboxes that this incoming profile will serve. To test this, log on to the computer that is running the E-mail Router by using the specified access credentials, or in Windows Internet Explorer, try to access the Outlook Web Access (OWA) URL of the user that you are testing (for example, http://exchangeserver/Exchange/crmuser). 115

For instructions about how to grant this access in Exchange Server 2003, see the Microsoft TechNet article How to Give a User Full Access to Another User's Mailbox. For instructions about granting this access in Exchange Server 2007, see the Microsoft TechNet article Add-MailboxPermission. If you selected the User specified option in the Access Credentials drop-down list, make sure that the users whose mailboxes this profile will serve have set their user name and password in the Set Personal Options dialog box (available in the Workplace section of the Microsoft Dynamics CRM web application). This enables the E-mail Router to access mailboxes by using each user's access credentials. Note The User specified option is intended for use in scenarios where the E-mail Router is configured to monitor user mailboxes, instead of a forward mailbox. This option is available only in the on-premises version of the product.

Mailbox not found (access test fails)

Symptom: When you click Test Access in the E-mail Router Configuration Manager, you receive the following HTTP error message: Incoming Status: Failure - The remote Microsoft Exchange e-mail server returned an error "(404) Not Found". The user or queue does not have a mailbox. Create a mailbox and try again. Resolution: Depending on which version of Exchange Server you are using, perform one of the following procedures.

For Exchange Server 2007 1. Connect to the Exchange Server where the mailbox is located. 2. Open Internet Information Services (IIS) Manager: Click Start, type inetmgr, and then press ENTER. 3. Verify the presence of the virtual directory (Exadmin or Exchange) that you are using to connect to the mailbox: a. Expand the default Web site. b. Verify that the Exadmin folder is present. If it is not, you will have to create it. For detailed information, see the Microsoft KB article 947802. Note 116

Another possible cause of this error is in the Microsoft Dynamics CRM user e-mail address information. In the Web application, verify that the user's e-mail address is set correctly.

For Exchange Server 2003 1. In the Web application, verify that the e-mail address logon information is the same as the users domain logon: Example of correct configuration: DomainName: DOMAIN\user1 E-mailAddress: user1@domain.com Example of incorrect configuration: DomainName: DOMAIN\user2 E-mailAddress: CRM.User@domain.com 2. Make sure that the Microsoft Dynamics CRM user properties are set to use the correct e-mail address. 3. Run the E-mail Router Configuration Manager to configure an incoming profile and then publish the profile. 4. Stop the E-mail Router service. For more information, see "To stop a service" below. 5. Open the Microsoft.Tools.Crm.EmailAgent.Xml file in a text editor such as Notepad. 6. At the top of the file, set ConfigUpdatePeriod = 0. 7. Modify each users incoming profile as follows: <EmailUser>DOMAIN\User2</EmailUser> <EmailPassword>{2A48C4DBF2BFZ3g==@MkoEoFd1wvV8bY8UijX7VA==</EmailPassword> <EmailAddress>CRM.User@domain.com</EmailAddress> Change only CRM.User to User2, as follows: <EmailAddress>User2@domain.com<EmailAddress> 8. Save the Microsoft.Tools.Crm.EmailAgent.Xml file. 117

9. Restart the E-mail Router service. For more information, see "To start a service" below. Important Clicking Test Access in the E-mail Router Configuration Manager will not result in a successful test. This is because test access will get the information from the Microsoft Dynamics CRM server directly and not from the Microsoft.Tools.Crm.EmailAgent.Xml file. To verify that the E-mail Router is functioning correctly, you can monitor the trace and errors and send test e-mail messages. Note You may find the following procedures helpful when you work with services in the preceding procedures.

To start a service 1. On the Start menu, type services.msc, or click Run, type services.msc, and then press ENTER. 2. Right-click the service that you want to start, and then click Start. 3. Click OK and then close the Services application. To stop a service 1. On the Start menu, type services.msc, or click Run, type services.msc, and then press ENTER. 2. Right-click the service that you want to stop, and then click Stop. 3. Click OK and then close the Services application.

Mailbox not found (access test succeeds)

Symptom: When you click Test Access in the E-mail Router Configuration Manager, the test succeeds. However, you receive HTTP 404 errors in the application event log when the E-mail Router processes e-mail messages. Check the IIS logs for the following error: Request Filtering: Denied because URL doubled escaping 404.11 Resolution: Run the following command on the Exchange Web site to allow double escaping: 118

%windir%\system32\inetsrv\appcmd set config "Default Web Site" section:system.webServer/security/requestfiltering -allowDoubleEscaping:true

For more information, see: IIS 7.0: Configure Request Filters in IIS 7.0 How to Use Request Filtering

The E-mail Router service configuration parameter "EmailUser" is missing

Symptom: When you use the E-mail Router, you may experience one or more of the following issues: An error event is logged in the application log (Event Source: MSCRMEmail) with a description that states EmailUser" is missing. When you use the Test Access functionality in the E-mail Router Configuration Manager, you receive an error message that states Emailuser is missing. This issue occurs because Microsoft Dynamics CRM is not configured to use your credentials to send and receive e-mail messages. Resolution: For information about how to resolve this issue, see the KB article 947094.

SSL/TLS error from E-mail Router Configuration Manager test access

Symptom: You run the E-mail Router to configure access to a mailbox. When you try to test access to the mailbox, you receive the following error message: Incoming Status: Failure - The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. The remote certificate is invalid according to the validation procedure. This issue occurs if you use self-signed certificates. The E-mail Router does not support selfsigned certificates. Resolution: For information about how to resolve this issue, see the KB article 954584.

119

POP3 issues
Error connecting the E-mail Router a POP3 mailbox
Symptom: When you click Test Access in the E-mail Router Configuration Manager to test a profile that uses a POP3 mailbox, you receive the following error: Incoming Status: Failure An error occurred while executing POP3 command Command removed for security reasons. The server response was: -ERR authorization first. This error occurs because POP3 does not use NTLM authentication. Instead, POP3 uses Basic authentication (clear text). Resolution: For information about how to resolve this issue, see the KB article 954046.

Issues with using a POP3 e-mail account

Symptom: After you configure the E-mail Router to use a POP3 e-mail account, you may experience one or more of the following symptoms: After you read e-mail messages from the POP3 mailbox, the E-mail Router does not process these messages. When you try to open the POP3 mailbox by using an e-mail reader, or when the E-mail Router connects to the POP3 mailbox, you receive one of the following error messages: The application cannot connect or open the mailbox. The mailbox is in use. Resolution: For information about how to resolve this issue, see the KB article 947059.

See Also
E-mail Router installation issues Outgoing e-mail configuration issues

Outgoing e-mail configuration issues

This section provides troubleshooting guidelines and information about resolving issues that can occur during E-mail Router outgoing profile configuration.

120

To troubleshoot an E-mail Router outgoing configuration profile 1. Make sure that you follow the outgoing configuration profile procedures in the E-mail Router Configuration Manager Help. 2. For more information about how to configure an outgoing profile, see Configure the Email Router in this guide. 3. See the following sections for information about how to resolve commonly encountered issues with outgoing configuration profiles.

Test Access error

If there is a problem with your outgoing e-mail configuration, you may receive the following error message when you click Test Access on the E-mail Router Configuration Manager: "Outgoing status: Failure - An error occurred while checking the connection to e-mail server EXSERVERNAME. The requested address is not valid in its context"

To troubleshoot test access 1. Run a telnet command to verify that connectivity is functioning between the computer that is running the E-mail Router and the Microsoft Exchange Server. For example, start the Telnet tool and type the following command: TELNET EXSERVERNAME PORT 2. Make sure that you have no antivirus services running on the Exchange Server computer that prevent connection through port 25.

Load Data error

When you click Load Data in the E-mail Router Configuration Manager, you receive the following error: The E-mail Router Configuration Manager was unable to retrieve user and queue information from the Microsoft Dynamics CRM server. This may indicate that the Microsoft Dynamics CRM server is busy. Verify that URL 'http://OrganizationName' is correct. Additionally, this problem can occur if the specified access credentials are insufficient. To try again, click Load Data. (The request failed with HTTP status 404: Not Found.)

121

To resolve this issue 1. Make sure the user account that is running the E-mail Router service is a member of the Active Directory directory service PrivUserGroup security group. 2. Make sure the account that is specified in the Access Credentials field on the General tab of the E-mail Router Configuration Profile dialog box is a Microsoft Dynamics CRM administrative user. If the access credentials are set to Local System Account, the computer account must be a member of the Active Directory PrivUserGroup security group. 3. Make sure that the URL of the Microsoft Dynamics CRM deployment is spelled correctly. The OrganizationUniqueName part of the URL must be spelled exactly as it appears in the Microsoft Dynamics CRM server. To determine the OrganizationUniqueName, start the Microsoft Dynamics CRM web application as a user who has the System Customizer role. Click Settings, and then click Customizations. On the Customization page, click Developer Resources. The OrganizationUniqueName is displayed below the Organization Unique Name label. For more information, see Configure the E-mail Router.

See Also
Incoming e-mail configuration issues Users do not receive Microsoft Dynamics CRM e-mail messages

Users do not receive Microsoft Dynamics CRM email messages

This issue can occur because the service account that the E-mail Router is running under has not been added to the PrivUserGroup security group. Note Perform the following steps on a computer that is a domain controller in the domain where you installed Microsoft Dynamics CRM Server 2011.

To resolve this issue 1. Click Start, point to Administrative Tools, and then click Active Directory Users and Computers. 2. Expand the organizational unit (OU) that you selected during Microsoft Dynamics CRM 122

Server Setup. By default, this is the Domain Controllers OU. 3. Right-click PrivUserGroup, and then click Properties. 4. On the Members tab, click Add, and then select the computer where the E-mail Router service is installed and running. 5. Click OK two times.

See Also
Outgoing e-mail configuration issues Test Access feature

Test Access feature

The E-mail Router Configuration Manager can test access for Microsoft Dynamics CRM users, queues, and forward mailboxes. By using the test-access feature, you can troubleshoot issues that can prevent the E-mail Router from functioning correctly.

Test Access error

If there is a problem with your outgoing email configuration, you may receive the following error message when you click Test Access on the E-mail Router Configuration Manager: "Outgoing status: Failure - An error occurred while checking the connection to e-mail server EXSERVERNAME. The requested address is not valid in its context"

To troubleshoot test access 1. Run a telnet command to verify that connectivity is functioning between the computer that is running the E-mail Router and the Microsoft Exchange Server. For example, start the Telnet tool and type the following command: TELNET EXSERVERNAME PORT 2. Make sure that there are no antivirus services or firewall services running on the server that is running Exchange Server that prevent connection through port 25. 3. For information about how to configure the SMTP server to allow relay messages from Microsoft Dynamics CRM, see the Microsoft Knowledge Base article 915827. 123

Error message when you send an email message by using the Microsoft Dynamics CRM web application
In addition, when you send an email message by using the Microsoft Dynamics CRM web application, you may receive an error message that resembles one of the following: This message has not yet been submitted for delivery. 1 attempts have been made so far. The message delivery failed. It must be resubmitted for any further processing. For more information see the Microsoft Knowledge Base article 915827. For more information about the test access feature, see "Test Access for Users, Queues, and Forward Mailboxes" in the E-mail Router Configuration Manager Help, as well as the following topics in this guide: Access credentials in Configure the E-mail Router in the Microsoft Dynamics CRM 2011 Installing Guide Incoming e-mail configuration issues in the Microsoft Dynamics CRM 2011 Installing Guide Outgoing e-mail configuration issues in the Microsoft Dynamics CRM 2011 Installing Guide

See Also
Troubleshooting E-mail Router issues Microsoft Dynamics CRM 2011 for Outlook Installation Instructions

Microsoft Dynamics CRM 2011 for Outlook Installation Instructions

This section applies to Microsoft Dynamics CRM Online and on-premises versions of Microsoft Dynamics CRM 2011. Microsoft Dynamics CRM for Microsoft Office Outlook enables access to the same data through Microsoft Outlook as the Microsoft Dynamics CRM Web client. Microsoft Dynamics CRM for Outlook is targeted at Microsoft Dynamics CRM users who need access to CRM data while they are using the familiar Outlook application. Note For information about how to plan Microsoft Dynamics CRM for Outlook deployments, see Planning Deployment in the Planning Guide. 124

For information about using Microsoft Group Policy to deploy Microsoft Dynamics CRM for Outlook, see Deploy Microsoft Dynamics CRM for Outlook by using Group Policy in the Planning Guide. After you install and configure Microsoft Dynamics CRM for Outlook, an individual user can use it to access Microsoft Dynamics CRM data. If a computer is shared by several users (that is, each user has a separate logon account and is a valid Microsoft Dynamics CRM user), you must configure Microsoft Dynamics CRM for Outlook by running Microsoft Dynamics CRM for Outlook configuration for each user. Note To install or upgrade Microsoft Dynamics CRM for Outlook, you must have administrator permissions on the computer where you perform the installation or upgrade steps. The exception to this is when you install an update from Microsoft Update, in which case administrator privileges are not required. You can install Microsoft Dynamics CRM for Outlook with offline capability. A user who has this capability installed can access Microsoft Dynamics CRM data when they are not connected to the LAN. You can add offline capability at either of the following times: During installation of Microsoft Dynamics CRM for Outlook. After installation has completed. In this case, a user can add offline capability by clicking Go Offline in Microsoft Outlook. This starts the installation of additional required components and stores a copy of the users Microsoft Dynamics CRM data locally. Subsequent offline sessions require no additional installations, but may require updating the local copy of the users data. Note Although multiple users can share a computer that uses Microsoft Dynamics CRM for Outlook, only one user can go offline on that computer.

In This Section
Installing on a computer that does not have Microsoft Dynamics CRM for Outlook installed Upgrade Microsoft Dynamics CRM 4.0 for Outlook to Microsoft Dynamics CRM 2011 for Outlook Troubleshooting Microsoft Dynamics CRM for Outlook installation, configuration and upgrade Install Microsoft Dynamics CRM for Outlook by using Microsoft System Center Configuration Manager
2007

Installing Microsoft Dynamics CRM for Outlook with Roaming User Profiles, Windows Server Remote
Desktop Services, or Citrix Presentation Server

125

See Also
Download: Microsoft Dynamics CRM 2011 for Microsoft Office Outlook (Outlook Client) Microsoft Dynamics CRM 2011 E-mail Router Installation Instructions

Installing on a computer that does not have Microsoft Dynamics CRM for Outlook installed
This section applies to Microsoft Dynamics CRM Online and on-premises versions of Microsoft Dynamics CRM 2011. The main application interface of Microsoft Dynamics CRM for Outlook resides in Microsoft Outlook. You can access it by using the Microsoft Outlook shortcut bars, ribbon, and folder navigation. Installing Microsoft Dynamics CRM for Outlook also creates a toolbar in Microsoft Outlook and a folder in the structure of the user's mailbox. To set up Microsoft Dynamics CRM for Outlook on a users computer, perform the following installation and configuration tasks: 1. Install Microsoft Dynamics CRM for Outlook. To complete this task, run the SetupClient.exe file in the appropriate folder on the installation media. For more information, see Task 1: Install Microsoft Dynamics CRM for Outlook below. 2. Configure Microsoft Dynamics CRM for Outlook. To complete this task, run the Microsoft Dynamics CRM for Outlook Configuration Wizard. For more information, see Task 2: Configure Microsoft Dynamics CRM for Outlook. You can run the Configuration Wizard either right after the installation finishes or at a later time. Note The Configuration Wizard starts automatically the first time you run Microsoft Outlook after you install Microsoft Dynamics CRM for Outlook. 3. Configure user email settings. To complete this task, configure the incoming email and outgoing email options for the user. You do this by using the User form in the Microsoft Dynamics CRM web application. By default, Microsoft Dynamics CRM for Outlook is selected as both the incoming and outgoing email access type. For more information, see Task 3: Configure user email settings below.

Task 1: Install Microsoft Dynamics CRM for Outlook

Use this procedure to install Microsoft Dynamics CRM for Outlook. You can add offline capability for the user either during this installation or at a later time. 126

Important Running Microsoft Dynamics CRM for Outlook on a computer that is running Microsoft Exchange Server is not supported.

To install Microsoft Dynamics CRM for Outlook 1. Meet the Microsoft Dynamics CRM for Outlook requirements specified in Microsoft Dynamics CRM for Outlook hardware requirements and Microsoft Dynamics CRM for Outlook software requirements in the Planning Guide. 2. Log on to the computer as a user who has Local Administrator privileges. 3. Best practice: Make sure that all Microsoft Office security updates are installed. To verify, visit Microsoft Update. 4. Locate and run the appropriate installation file: To install from a DVD, double-click SetupClient.exe in the installation folder for the architecture (32-bit or 64-bit) of Microsoft Office that you have installed: ... \Client\amd64 for 64-bit ... \Client\i386 for 32-bit To install from the web, open the Microsoft Dynamics CRM 2011 for Microsoft Office Outlook (Outlook Client) download page and then download and run the executable file that matches the architecture of Microsoft Office that you have installed. To install from the Microsoft Dynamics CRM user interface, click Get CRM for Outlook on the message bar. If you see one or more dialog boxes entitled Security Warning, click Run in each. The Microsoft Dynamics CRM 2011 for Microsoft Office Outlook Setup wizard starts. 5. On the License Agreement page, review the information. If you accept the license agreement, select I accept the license agreement, and then click Next. 6. On the Get Recommended Updates page, indicate whether you want to obtain updates through the Microsoft Update program, and then click Next. Note Should Microsoft make improvements to Microsoft Dynamics CRM for Outlook, it will release them in a software update. If you choose Get Recommended Updates, those updates will be installed on an automated basis. The exact level of automation for example, whether any user interaction is required during 127

the installation is determined by the group policy that is in place within your organization. 7. Click either Install Now or Options. To install Microsoft Dynamics CRM for Outlook with offline access, click Options, select Offline Capability on the Customize Installation page, and then click Install Now. To install Microsoft Dynamics CRM for Outlook without offline access, click Install Now. Important If you do not install offline capability at this point, the user will initially have no offline capability. If you choose Install Now, the Microsoft Outlook user can add offline capability later by clicking Go Offline in Microsoft Outlook. The program features are installed and a progress indicator is displayed. You may be asked to restart your computer to complete the installation. 8. On the completion page of the Microsoft Dynamics CRM 2011 for Microsoft Office Outlook Setup wizard, click Close.

Task 2: Configure Microsoft Dynamics CRM for Outlook

After Microsoft Dynamics CRM for Outlook is installed, it must be configured. When you restart Outlook after you have installed Microsoft Dynamics CRM for Outlook, the Configuration Wizard starts automatically. Note If you do not want to configure Microsoft Dynamics CRM for Outlook immediately after you install it, click Cancel on the Configure Organization page of the wizard. A Configure Microsoft Dynamics CRM for Outlook button then appears on the Microsoft Outlook toolbar and will remain there until you configure Microsoft Dynamics CRM for Outlook. If the Configuration Wizard does not start automatically, you can start it as described in the first procedure that follows. The second procedure gives information about how to use a script to configure multiple client computers.

To configure Microsoft Dynamics CRM for Outlook manually 1. Start the Configuration Wizard: Click Start, point to All Programs, point to Microsoft 128

Dynamics CRM, and then click Configuration Wizard. Alternatively, click Configure Microsoft Dynamics CRM for Outlook on the CRM tab in Microsoft Outlook. 2. For Server URL, choose the option appropriate for you. To connect to a Microsoft Dynamics CRM Online organization, in the Server URL list, click CRM Online. To connect to an on-premises deployment of Microsoft Dynamics CRM 2011, type the discovery-service URL for Microsoft Dynamics CRM in the format http://crmserver or http://crmserver:5555. Note If you are configuring Microsoft Dynamics CRM for Outlook to connect to an on-premises deployment of Microsoft Dynamics CRM 2011 over the Internet, use the discovery-service URL with this format: https://dev.crmserver.contoso.com. Check with your system administrator for the exact URL. 3. Click Test Connection. This populates the Organization Information list. If you are prompted for credentials, select from the following options. For a Microsoft Dynamics CRM Online organization Connecting through Office 365, enter your Microsoft online services user name and password, and then click OK. This information should have been sent to you in email when your account was added. Connecting by using an earlier online services platform, enter your Microsoft account (formerly Windows Live ID) and password, and then click OK. This information should have been sent to you in email when your account was added. For an on-premises deployment of Microsoft Dynamics CRM 2011, you may not be prompted because Microsoft Dynamics CRM will use your Active Directory domain credentials. Click OK. 4. For Organization, verify the Microsoft Dynamics CRM organization in the Organization list to which you want to connect, and then click OK. The organization is initialized. Click Close. 5. If you are a member of more than one organization, restart the Configuration Wizard to 129

designate a different organization as your current organization. Note To configure Microsoft Dynamics CRM for Outlook automatically from the command line, in quiet mode, or using a script, see Step 2: Configure Microsoft Dynamics CRM for Outlook by using an XML configuration file.

Task 3: Configure user email settings

The E-mail Router is not required to send and receive Microsoft Dynamics CRM email messages. Instead of using the E-mail Router, you can use Microsoft Dynamics CRM for Outlook to perform the following tasks: Deliver received email messages to Microsoft Dynamics CRM. Send email messages that are generated from Microsoft Dynamics CRM. Note By default, the incoming and outgoing email access types for a user are set to Microsoft Dynamics CRM for Outlook. To enable the Microsoft Dynamics CRM for Outlook for a particular user, you must set the incoming and outgoing email access types only if they have been changed from their default value. As part of email configuration, you should verify email tracking options. By default, only email messages in response to a Microsoft Dynamics CRM generated email message are tracked. For more information about these settings, see "Specify how your email is tracked" in the Microsoft Dynamics CRM Help.

User and queue email configuration

The email messaging incoming and outgoing settings can be different for each user or queue. You configure these incoming and outgoing options on the User form.

To set the email access type 1. Open the Microsoft Dynamics CRM web application. 2. In the Navigation Pane, click Settings. 3. Under System, click Administration. 4. In the Administration area, click Users. 130

5. Find the user whose settings you want to edit. You may need to navigate to a different page. 6. Click the name of the user, or select the user and then click Edit. The User form opens. You can edit the messaging options in the Email Access Configuration section. Note By default, Microsoft Dynamics CRM sets both the incoming email access type and the outgoing email access type to "Microsoft Dynamics CRM for Outlook." 7. To enable Microsoft Dynamics CRM for Outlook for this user, select Microsoft Dynamics CRM for Outlook.

Incoming email messaging options

You can use the following incoming email configurations when a user or a queue receives Microsoft Dynamics CRM email messages: None. Use this option for users or queues that do not use Microsoft Dynamics CRM to send email messages. Microsoft Dynamics CRM for Outlook. This option requires that Microsoft Outlook be installed on the user's computer. This option does not require the E-mail Router component. However, to process Microsoft Dynamics CRM email messages, Microsoft Outlook must be running. E-mail Router. This option delivers Microsoft Dynamics CRM email messages directly to Microsoft Dynamics CRM, without the need of a forward mailbox. The email system that you can use to process messages can be Microsoft Exchange Server 2003, Microsoft Exchange Server 2007, Microsoft Exchange Server 2010, Exchange Online, or a POP3-compliant server. For more information, see the E-mail Router documentation. Forward Mailbox. To use this option, you must install the E-mail Router. This option requires a dedicated mailbox, which your administrator must create. The E-mail Router processes email messages that are forwarded to this mailbox. Although this option does not require users to run Microsoft Outlook, it does require that a server-side rule be deployed for the user. If you are using Exchange Server to process incoming email messages, you can deploy the rule by using the Rule Deployment Wizard. For more information, see Deploy inbox rules and Set up a forward mailbox in Configure the E-mail Router in this guide.

Outgoing email messaging options

The following are the outgoing email configurations that you can use when users or queues send Microsoft Dynamics CRM email messages:

131

 None. Use this option for users or queues that do not use Microsoft Dynamics CRM to send email messages. Microsoft Dynamics CRM for Outlook. This option requires that Microsoft Outlook be installed on the user's computer. This option does not require the E-mail Router component. E-mail Router. This option sends Microsoft Dynamics CRM email messages by using the Email Router component. The email system must be SMTP compliant. The E-mail Router can be installed on an SMTP server, or on a different computer that has a connection to an SMTP server.

See Also
Microsoft Dynamics CRM 2011 for Outlook Installation Instructions Upgrade Microsoft Dynamics CRM 4.0 for Outlook to Microsoft Dynamics CRM 2011 for Outlook

Upgrade Microsoft Dynamics CRM 4.0 for Outlook to Microsoft Dynamics CRM 2011 for Outlook

Notes about upgrading Microsoft Dynamics CRM for Outlook

The following procedures do not apply to moving between versions of Microsoft Dynamics CRM 2011 for Outlook. Do not use these upgrade procedures to update a computer that has an earlier version of Microsoft Dynamics CRM 2011 for Outlook installed. Keep your Microsoft Dynamics CRM deployment current by installing the latest updates and hotfixes automatically from Microsoft Update. You can also search for updates on the Microsoft Download Center. Choosing Microsoft Update lets you install recommended updates automatically and without administrator permissions. Base languages must match. To upgrade Microsoft Dynamics CRM for Outlook, the base language of Microsoft Dynamics CRM 2011 for Outlook must match the base language of Microsoft Dynamics CRM 4.0 for Outlook. Upgrade is required to continue offline access after server upgrade. For an on-premises deployment of Microsoft Dynamics CRM 2011, after the Microsoft Dynamics CRM Server 2011 in an organization has been upgraded to Microsoft Dynamics CRM Server 2011, users must upgrade to Microsoft Dynamics CRM 2011 for Outlook to continue accessing data offline. For example, a particular user runs Microsoft Dynamics CRM 4.0 for Outlook and 132

accesses data offline. This user's organization is upgraded from Microsoft Dynamics CRM 4.0 to Microsoft Dynamics CRM 2011. Although there now exists a client-server mismatch, the user can still connect to the server and can still access data online. However, to go offline again, the user must upgrade to Microsoft Dynamics CRM 2011 for Outlook.

Cross-architecture upgrade of Microsoft Dynamics CRM for Outlook

If you intend to change to a different architecture (move from 32-bit to 64-bit or vice versa) while upgrading, note the following: In-place cross-architecture upgrade is not supported. Microsoft Dynamics CRM 4.0 for Outlook was available only in a 32-bit architecture. If you are running Microsoft Dynamics CRM 4.0 for Outlook, you can perform an in-place upgrade only to 32-bit Microsoft Dynamics CRM 2011 for Outlook. This also applies to Office 2010: If you are running and intend to retain 32-bit Office 2010, you can upgrade only to 32-bit Microsoft Dynamics CRM 2011 for Outlook. Cross-architecture upgrade requires uninstalling and reinstalling. To change to a different architecture, perform the following steps in the order listed: a. Uninstall Microsoft Dynamics CRM 4.0 for Outlook. b. Uninstall Microsoft Office. c. Install a 64-bit edition of Microsoft Office. d. Install the 64-bit edition of Microsoft Dynamics CRM 2011 for Outlook. For more information about installing Microsoft Dynamics CRM 2011 for Outlook, see "Task 1: Install Microsoft Dynamics CRM for Outlook" in Installing on a computer that does not have Microsoft Dynamics CRM for Outlook installed in this guide.

Task 1: Install Microsoft Dynamics CRM 2011 for Outlook

Follow this procedure to install Microsoft Dynamics CRM 2011 for Outlook on a computer that has Microsoft Dynamics CRM 4.0 for Outlook installed. Note These steps describe an in-place upgrade. To know whether an in-place upgrade is possible in your situation, see the information above.

To upgrade Microsoft Dynamics CRM 4.0 for Outlook to Microsoft Dynamics CRM 2011 for Outlook 1. Meet the Microsoft Dynamics CRM for Outlook requirements specified in Microsoft Dynamics CRM for Outlook hardware requirements and Microsoft Dynamics CRM for 133

Outlook software requirements in the Planning Guide. 2. Log on to the computer as a user who has Local Administrator privileges. 3. Best practice: Make sure that all Microsoft Office security updates are installed. To verify, visit Microsoft Update (http://go.microsoft.com/fwlink/?LinkId=165705). 4. Locate and run the appropriate installation file: To install from a DVD, double-click the SetupClient.exe file in the ... \Client\i386 installation folder. To install from the Web, open the Microsoft Dynamics CRM 2011 for Microsoft Office Outlook (Outlook Client) download page and then download and run the executable file for 32-bit Microsoft Office. To install from the Microsoft Dynamics CRM user interface, click Get CRM for Outlook on the message bar. If you see one or more dialog boxes entitled Security Warning, click Run in each. The Microsoft Dynamics CRM 2011 for Microsoft Office Outlook Setup wizard starts. 5. On the License Agreement page, review the information. If you accept the license agreement, select I accept the license agreement, and then click Next. 6. On the Upgrade page, click Upgrade Now. 7. Setup stores your configuration information, installs the program features, and displays a progress indicator. Your configuration information is reapplied in the new installation. 8. On the completion page of the Microsoft Dynamics CRM 2011 for Microsoft Office Outlook Setup wizard, click Close.

Task 2: Configure Microsoft Dynamics CRM for Outlook

After the upgrade from Microsoft Dynamics CRM 4.0 for Outlook, Microsoft Dynamics CRM for Outlook attempts to use the configuration information that was used by Microsoft Dynamics CRM 4.0 for Outlook. If the configuration information is correct, this re-use will succeed and you will need to take no action. However, Microsoft Dynamics CRM for Outlook must be reconfigured if the old configuration details no longer apply. When the user restarts Outlook after the installation of Microsoft Dynamics CRM for Outlook, you will know that reconfiguration is necessary if the Configuration Wizard automatically starts. It does so if either of the following is true: The URL of Microsoft Dynamics CRM Online to which the Microsoft Dynamics CRM for Outlook connects has changed. 134

Important For on-premises deployment of Microsoft Dynamics CRM 2011, if the discoveryservice URL or the organization URL changes during the upgrade of an Internetfacing deployment (IFD) from Microsoft Dynamics CRM 4.0 to Microsoft Dynamics CRM 2011, Microsoft Dynamics CRM 4.0 for Outlook will not work. You must either reconfigure each instance of Microsoft Dynamics CRM 4.0 for Outlook (by using the Configuration Wizard, System Center Configuration Manager, or Group Policy), to point Microsoft Dynamics CRM 4.0 for Outlook to the new URL, or upgrade to Microsoft Dynamics CRM 2011 for Outlook. The user's installation of Microsoft Dynamics CRM 4.0 for Outlook was not completely configured. Note If you do not want to configure Microsoft Dynamics CRM for Outlook immediately after you install it, click Cancel on the Configure Organization page of the wizard. A Configure Microsoft Dynamics CRM for Outlook button then appears on the Outlook toolbar and will remain there until you configure Microsoft Dynamics CRM for Outlook. If the Configuration Wizard does not start automatically, you can start it as described in the following procedure.

To configure Microsoft Dynamics CRM for Outlook manually 1. Start the Configuration Wizard: Click Start, point to All Programs, point to Microsoft Dynamics CRM, and then click Configuration Wizard. Alternatively, click Configure Microsoft Dynamics CRM for Outlook on the CRM tab in Outlook. 2. For Server URL, choose the option appropriate for you. To connect to a Microsoft Dynamics CRM Online organization, in the Server URL list, click CRM Online. To connect to an on-premises deployment of Microsoft Dynamics CRM 2011, type the discovery-service URL for Microsoft Dynamics CRM in the format http://crmserver or http://crmserver:5555. Note If you are configuring Microsoft Dynamics CRM for Outlook to connect to an on-premises deployment of Microsoft Dynamics CRM 2011 over the internet, use the discovery-service URL with this format: 135

https://dev.crmserver.contoso.com. Check with your system administrator for the exact URL. 3. Click Test Connection. This populates the Organization Information list. If you are prompted for credentials, select from the following options. For a Microsoft Dynamics CRM Online organization Connecting through Office 365, enter your Microsoft online services user name and password, and then click OK. This information should have been sent to you in email when your account was added. Connecting by using an earlier online services platform, enter your Microsoft account (formerly Windows Live ID) and password, and then click OK. This information should have been sent to you in email when your account was added. For an on-premises deployment of Microsoft Dynamics CRM 2011, you may not be prompted because Microsoft Dynamics CRM will use your Active Directory domain credentials. Click OK. 4. For Organization, verify the Microsoft Dynamics CRM organization in the Organization list to which you want to connect, and then click OK. The organization is initialized. Click Close. 5. If you are a member of more than one organization, restart the Configuration Wizard to designate a different organization as your current organization. To configure Microsoft Dynamics CRM for Outlook using a script 1. Write a script that automatically updates the configuration settings for users of Microsoft Dynamics CRM for Outlook. You could use lines such as the following to perform the basic configuration actions, based on a new configuration file that is stored on the computer indicated as <servername>. In the following script, the default client configuration file is overwritten, previously configured organizations are removed, and the new organization is installed:
copy /y \\<servername>\share\Default_Client_Config.xml "c:\Program Files\Microsoft Dynamics CRM\Default_Client_Config.xml"

136

"C:\Program Files\Microsoft Dynamics CRM\Client\ConfigWizard\Microsoft.Crm.Application.Outlook.Con figWizard.exe" /q /xa "C:\Program Files\Microsoft Dynamics CRM\Client\ConfigWizard\Microsoft.Crm.Application.Outlook.Con figWizard.exe" /q /i "C:\Program Files\Microsoft Dynamics CRM\Default_Client_Config.xml"

Tip Consider running your script as a logon script, or forcing the script to run at a specific time, such as by using Microsoft System Center Configuration Manager 2007. In the script, you might also want to include detection logic that determines whether the client computer has already been configured. If it has, you can have the script exit without taking action. Example Default_Client_Config.xml file
<Deployment> <DiscoveryUrl>http://CrmDiscoveryUrl</DiscoveryUrl> <Organizations> <Organization IsPrimary='true'>Organization1</Organization> </Organizations> </Deployment>

2. Run the script on each client computer in the organization whose server has changed. You can run the script in various ways, including through the Profile tab of the user properties dialog box in Active Directory Users and Computers (ADUC), or through Group Policy Objects (GPO).

See Also
Installing on a computer that does not have Microsoft Dynamics CRM for Outlook installed Troubleshooting Microsoft Dynamics CRM for Outlook installation, configuration and upgrade

137

Troubleshooting Microsoft Dynamics CRM for Outlook installation, configuration and upgrade
This section describes how to troubleshoot Microsoft Dynamics CRM for Outlook installation and upgrade issues.

Troubleshooting installation and configuration tips and known issues

Run the Microsoft Dynamics CRM for Outlook Configuration Troubleshooting Wizard . A step by step wizard that can help resolve Microsoft Dynamics CRM for Outlook configuration issues.

Microsoft Dynamics CRM Online with Office 365

When you try to connect to an organization that is part of your Microsoft Office 365 subscription by using the Configuration Wizard or Microsoft Dynamics CRM Online for Outlook, you are cannot connect. To resolve this issue, verify, and if necessary, correct the following: Make sure that you can connect to the organization by using Internet Explorer. There may be incomplete information with your Microsoft online services account that is preventing you from authenticating with the service. The URL for the organization is provided in the invitation email message you should have received from Microsoft online services, and is typically in the form of https:// OrganizationName.onmicrosoft.com or https:// OrganizationName.crm.dynamics.com. If you are not certain of the URL, contact your system administrator Make sure that the Microsoft Online Services Sign-in Assistant is installed on your computer. This component is required by Microsoft Dynamics CRM Online for Outlook to sign-in to an Office 365 subscription. To verify, click Start, click Control Panel, and then in the Control Panel window click Programs, and then click Programs and Features. In this list of installed programs verify that Microsoft Online Services Sign-in Assistant appears. If it is not installed, download and install the component.
Microsoft Online Services Sign-In Assistant for IT Professionals RTW

Log files
When you install and configure Microsoft Dynamics CRM for Outlook, the system creates log files that you can use for troubleshooting.

138

By default, the location of the Setup log files (including crm50setup.log and the Microsoft.Crm.Application.Hoster log file), where User is the account of the user who ran Setup, is as follows: Windows XP: SystemDrive:\Documents and Settings\<User>\Application Data\Microsoft\MSCRM\Logs\ Windows Vista: SystemDrive:\Users\<User>\AppData\Roaming\Microsoft\MSCRM\Logs\ Windows 7: SystemDrive:\Users\<User>\AppData\Local\Microsoft\MSCRM\Logs By default, the location of the configuration log files (including crm50clientconfig.log), where User is the account of the user who ran Configuration Wizard, is as follows: Windows XP: SystemDrive:\Documents and Settings\<User>\Local Settings\Application Data\Microsoft\MSCRM\Logs\ Windows Vista: SystemDrive:\Users\<User>\AppData\Local\Microsoft\MSCRM\Logs Windows 7: SystemDrive:\Users\<User>\AppData\Local\Microsoft\MSCRM\Logs

Event Viewer
To access event logging information for Microsoft Dynamics CRM for Outlook, you open Event Viewer from the client computer where Microsoft Dynamics CRM for Outlook is installed, and then view the entries in the Application log. To view the Application log in Event Viewer on Windows Vista or Windows 7: 1. On the computer where Microsoft Dynamics CRM for Outlook is installed, start Event Viewer. 2. In the navigation pane, expand Windows Logs and then click Application. 3. To make it easier to locate events that apply to Microsoft Dynamics CRM for Outlook, use Create Custom View or Filter Current Log and then sort by applying the following Event sources: MSCRM* (such as MSCRMAddin, MSCRMAddressBook, etc.) MSSQL$CRM

139

Disable the CRM for Outlook button on the Web application

By default, if a user does not have Microsoft Dynamics CRM for Outlook installed and configured, the Microsoft Dynamics CRM web application displays a Get CRM for Outlook button on the message bar. This button provides a link for users to download Microsoft Dynamics CRM for Outlook. If you do not want users to have this capability, you can remove the button.

To remove the Get CRM for Outlook button from the Microsoft Dynamics CRM web application 1. With a security role that has read and write permissions (for example, the System Administrator role), start the Microsoft Dynamics CRM web application. 2. Click Settings. 3. Under System, click Administration. 4. Click System Settings. The System Settings dialog box appears. 5. Click the Outlook tab. 6. Set the value for Outlook client is advertised to users in the Message Bar to No.

See Also
Upgrade Microsoft Dynamics CRM 4.0 for Outlook to Microsoft Dynamics CRM 2011 for Outlook Install Microsoft Dynamics CRM for Outlook by using Microsoft System Center Configuration Manager 2007

Install Microsoft Dynamics CRM for Outlook by using Microsoft System Center Configuration Manager 2007
Microsoft System Center Configuration Manager 2007 is a tool that administrators can use to distribute software to users computers. System Center Configuration Manager 2007 is one way to distribute Microsoft Dynamics CRM 2011 for Outlook to users in an organization. 140

In This Topic
Prerequisites Use Microsoft System Center Configuration Manager 2007 to distribute Microsoft Dynamics CRM for Outlook Part 1: Start the Distribute Software to Collection Wizard Part 2: Continue the Distribute Software to Collection Wizard Part 3: Complete the Distribute Software to Collection Wizard Inspect the distribution package

Prerequisites
Prepare System Center Configuration Manager
You can perform the following procedures only if your organization has a working System Center Configuration Manager implementation. Also, software distribution for System Center Configuration Manager must be enabled for clients in your network. For more information, see Configuration Manager 2007 Documentation Library.

Distribute prerequisite software for Microsoft Dynamics CRM for Outlook

Use one of the following methods to distribute the prerequisite software required by Microsoft Dynamics CRM for Outlook: Use System Center Configuration Manager to distribute the prerequisite software. This helps avoid computer restarts during Microsoft Dynamics CRM client setup. Propagate the prerequisite software to a central file share along with the Microsoft Dynamics CRM installation files. Then, let Microsoft Dynamics CRM setup perform the installation. It will, when required, restart client computers. For more information, see Configuration Manager 2007 Documentation Library.

Use Microsoft System Center Configuration Manager 2007 to distribute Microsoft Dynamics CRM for Outlook
In the following procedures, you use Microsoft System Center Configuration Manager 2007 to create and distribute a distribution package. This package will contain files and settings that will 141

install Microsoft Dynamics CRM for Outlook and can be customized with configuration information that will allow users to begin using Microsoft Dynamics CRM immediately. Important The following procedures describe an example of a way to install Microsoft Dynamics CRM 2011 for Outlook by using System Center Configuration Manager. The file names, installation options, and other settings given here depict one way but not the only way to accomplish this task. Other choices might be more appropriate for other system configurations. For more information about the settings that System Center Configuration Manager makes available, see the Help system that is built into System Center Configuration Manager. Also see the online documentation for System Center Configuration Manager, in particular the section Wizard Pages. The following procedures use a System Center Configuration Manager client called "SCCM_CLIENT1."

Part 1: Start the Distribute Software to Collection Wizard

To create a distribution package 1. Open the Microsoft System Center Configuration Manager 2007 console. This console is where you control System Center Configuration Manager by setting up client agents, network addresses, boundaries, and so on. 2. In the navigation pane, expand Computer Management, and then expand Collections. Note A collection is a logical grouping of computers. This grouping can represent, for example, the set of computers onto which you intend to distribute Microsoft Dynamics CRM for Outlook. 3. Under Collections, right-click the client System: SCCM_CLIENT1, point to Distribute, and click Software. The Distribute Software to Collection Wizard starts. In this wizard, you complete all the steps needed to create a software package and distribute it to clients. 4. On the Welcome page, click Next. 5. On the Package page, click Create a new package and program without a definition file, and then click Next. 6. On the Package Identification page, type a name for the package. In this example, for 142

Name, type CRM Client for Outlook. 7. Type the following values into the remaining fields on the Package Identification page: Version: 5.0 Publisher: Microsoft Language: 1033 Comment: Outlook Client Distribution Package 8. Click Next. 9. On the Source Files page, click Create a compressed version of the source files, and then click Next. 10. On the Source File Compression page, indicate where System Center Configuration Manager is to find the source files for Microsoft Dynamics CRM for Outlook so that it can place them in a package. First, under Source directory location, select Network path (UNC name) or Local drive on site server. Then, under Source directory, indicate the actual path to the Microsoft Dynamics CRM for Outlook source files. Click Next. 11. Continue with Part 2: Continue the Distribute Software to Collection Wizard below.

Part 2: Continue the Distribute Software to Collection Wizard

1. On the Distribution Points page, select one or more points from which the package will be distributed. In a large organization, especially if it is geographically dispersed, you may want to use multiple distribution points. In a small organization, a single distribution point may be enough. Under Distribution points, select one or more distribution points, and then click Next. 2. On the Program Identification page, indicate the action that System Center Configuration Manager should take to install the package. For Name, type SetupClient. 3. Click Browse, and then navigate to the setup location that you indicated on the Source File Compression page. Select the executable file that installs Microsoft Dynamics CRM for Outlook (SetupClient.exe), and then click Open. The name of this executable file displays in the Command line field. 4. (Optional) Add command-line options to the SetupClient.exe command. The following are examples that you may want to consider: 143

 Type /q to specify a "quiet" installation, namely one that requires no interaction with the user on whose computer Microsoft Dynamics CRM for Outlook is being installed. Type /targetdir=<folder name> to indicate a folder into which to install Microsoft Dynamics CRM for Outlook. If you omit this option Microsoft Dynamics CRM for Outlook is installed to the default folder,drive:\Program Files\Microsoft Dynamics CRM\Client or drive:\Program Files (x86)\Microsoft Dynamics CRM\Client. Type /l drive:\<folder name>\<file name> to indicate the name and folder of a log file in which to record setup events. You can use this log file to troubleshoot installation issues. In this distribution package example, we use the following command line: SetupClient.exe /q /l c:\sms.log 5. (Optional) For Comment, add notes that System Center Configuration Manager administrators may need to read. 6. If applicable, for Category, select a custom category, and then click Next. In System Center Configuration Manager, categories are properties by which users can filter software to more easily find distribution packages that meet their needs. For example, you could classify Microsoft Dynamics CRM for Outlook as an example of the type "customer-relationship management." 7. Continue with Part 3: Complete the Distribute Software to Collection Wizard below.

Part 3: Complete the Distribute Software to Collection Wizard

1. On the Program Properties page, specify how you want the installation program to run. For Program can run, select Whether or not a user is logged on. 2. For After running, select No action required, and click Next. Note A particular software installation might require a computer restart, but it might not enforce the restart. In this case, you could have System Center Configuration Manager cause the restart by selecting ConfigMgr restarts computer (or Program restarts computer). You could also schedule the restart to occur at a time of day when users are not expected to be working. 144

3. On the Advertise Program page, select Yes, and then click Next. 4. On the Select Program page, make sure that SetupClient is selected under Programs, and then click Next. 5. On the Advertisement Name page, the Name of the advertisement is shown as CRM Client for Outlook SetupClient to System : SCCM_CLIENT1. For Comment, you can add text to remind you, for example, of the purpose of the software distribution, so that you can more easily identify it later. Click Next. 6. On the Advertisement Subcollection page, select Advertise the program to members of the collection and its subcollections, and then click Next. 7. On the Advertisement Schedule page, specify when you want the installation to take place. You could, for example, specify that installations can take place only during "maintenance windows," or times that the technical staff has set aside for preventive maintenance that might cause a disruption of service. For Advertise the program after, input a date and time. 8. Select No, this advertisement never expires. 9. (Optional) Clear the check box for Download content from unprotected distribution point and run locally. Then, click Next. 10. On the Assign Program page, click Yes, assign the program. This choice makes it mandatory for users to install the programin this case, Microsoft Dynamics CRM for Outlook. 11. On the Summary page, click Next. System Center Configuration Manager creates the distribution package. 12. On the Wizard Completed page, click Close. 13. Continue with Inspect the distribution package below.

Inspect the distribution package

Note This procedure is optional. After you complete the steps in the preceding procedure, the new distribution package exists. Next, you can inspect the distribution package to make sure that it is ready to be propagated and used.

To inspect the distribution package 145

1. In the navigation pane of the System Center Configuration Manager console, under Computer Management, expand Software Distribution, and then expand Packages. The Microsoft CRM Client for Outlook package displays in the Packages pane. 2. In the navigation pane, expand Microsoft CRM Client for Outlook, and then click Distribution Points. 3. In the Distribution Points pane, make sure that at least one distribution point is displayed. 4. In the navigation pane, expand the Package Status node, and within it, the other Package Status node. This displays information about each package for each site to which the package is targeted. 5. In the interior Package Status folder, click the name of a distribution point. The distribution point and its contents display in the main pane of the System Center Configuration Manager console. 6. You can now determine whether a deployment package has been successfully provisioned on the distribution point. If, for example, the value in the State column is Install Pending, the propagation of the distribution package has not yet occurred. You might need to wait a few minutes for provisioning to complete. 7. After the State of the package has changed to Installed, the distribution package has been propagated, which means it can be used to install software on client computers. 8. In the navigation pane of the System Center Configuration Manager console, click Advertisements. 9. Right-click the advertisement listed in the Advertisements pane, and then click Properties. Make sure that the values shown for Package, Program, and Schedule are correct. 10. (Optional) Check that the values shown on the other tabs of the Properties dialog box are correct.

See Also
Troubleshooting Microsoft Dynamics CRM for Outlook installation, configuration and upgrade Installing Microsoft Dynamics CRM for Outlook with Roaming User Profiles, Windows Server Remote Desktop Services, or Citrix Presentation Server

146

Installing Microsoft Dynamics CRM for Outlook with Roaming User Profiles, Windows Server Remote Desktop Services, or Citrix Presentation Server
This section describes how to install Microsoft Dynamics CRM for Outlook with roaming user profiles, Windows Server Remote Desktop Services, or Citrix Presentation Server. Important Microsoft Dynamics CRM for Outlook with Offline Access is not supported for installation with roaming user profiles, Windows Server Remote Desktop Services, or Citrix Presentation Server. Instead, you should install Microsoft Dynamics CRM for Outlook from the command prompt and include the parameter disableofflinecapability. This removes the offline button from the Microsoft Dynamics CRM for Outlook user interface. For more information, see Install Microsoft Dynamics CRM for Outlook using a Command Prompt in this guide.

Roaming User Profiles

A roaming user profile is a copy of the local user profile that is copied to, and stored on, a server share. This profile is downloaded to each computer that a user logs onto on a network. Changes made to a roaming user profile are synchronized with the server copy of the profile when the user logs off. The advantage of roaming user profiles is that users do not have to create a profile on each computer that they use on a network. While the roaming user profile moves with the user, software applications such as Microsoft Dynamics CRM for Outlook do not. Identical applications have to be installed on each computer that the user roams to.

Windows Server Remote Desktop Services

Remote Desktop Services (RDS) in Windows Server 2008 is the new name for Terminal Services. RDS is a centralized desktop and application platform solution that uses presentation and desktop virtualization technologies. Microsoft Dynamics CRM for Outlook is supported for running on Windows Server 2008 or Windows Server 2008 R2 of Remote Desktop Services. When users run an application on Remote Desktop Services, the application execution occurs on the server. Only keyboard, mouse, and display information are transmitted over the network. Users see only their own

147

individual sessions, which are managed transparently by the server operating system and remain independent of any other client session. For more information, see Remote Desktop Services.

Citrix XenApp
Instructions about how to deploy Microsoft Dynamics CRM for Outlook with Citrix XenApp 6 are available on the Microsoft Download Center at: Microsoft Dynamics CRM for Microsoft Office Outlook Compatibility with Citrix XenApp 6.

Disable the Get CRM for Outlook button

Note The information in this topic applies to deployments with Microsoft Terminal Server or Citrix server user connections. For general Get CRM for Outlook button removal steps, see Disable the CRM for Outlook button on the Web application . The Microsoft Dynamics CRM for Outlook Configuration Wizard will start when users connect to a Microsoft Terminal Server or Citrix server. In addition, users will see an option to configure Microsoft Dynamics CRM for Outlook. To disable the Microsoft Dynamics CRM for Outlook Configuration Wizard and the option to configure Microsoft Dynamics CRM for Outlook in Microsoft Outlook 2010, follow these steps on the client computer. Note You can also use Group Policy or a logon script to create this registry key for Terminal Server or Citrix users who do not use Microsoft Dynamics CRM for Outlook.

1. Click Start, and then type regedit in the Search programs and files box. 2. Locate the following registry subkey: HKEY_CURRENT_USER\Software\Microsoft\Office\Outlook\Addins 3. Right-click Addins, point to New, and then click Key. 4. Type crmaddin.Addin, and then press ENTER. 5. Right-click crmaddin,Addin, point to New, and then click DWORD Value or DWORD (32148

bit) Value. 6. Type LoadBehavior and then press ENTER. 7. Right-click LoadBehavior, and then click Modify. 8. Type 8 in the Value Data box, click Decimal, and then click OK. 9. Exit Registry Editor. To disable the Microsoft Dynamics CRM for Outlook Configuration Wizard and the option to configure Microsoft Dynamics CRM for Outlook in Microsoft Office Outlook 2007 and Microsoft Office Outlook 2003, follow these steps on the client computer:

1. Click Start, and then type regedit in the Search programs and files box. 2. Locate the following registry subkey: Outlook 2007
HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\Resiliency\DisabledIt ems

Outlook 2003
HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook\Resiliency\DisabledIt ems

3. Right-click DisabledItems, point to New, and then click Binary Value. 4. Type CRMAddin and then press ENTER. 5. Right-click CRMAddin and then click Modify. 6. Type the following in the Value Data box and then click OK: Use this value for: 32-bit versions of Microsoft Office and Microsoft Dynamics CRM for Outlook running on 32-bit versions of Windows. 64-bit versions of Microsoft Office and Microsoft Dynamics CRM for Outlook running on 64-bit versions of Windows.
hex:01,00,00,00,80,00,00,00,2e,00,00,00,63,00,3a,00,5c,00,70, 00,72,\ 00,6f,00,67,00,72,00,61,00,6d,00,20,00,66,00,69,00,6c,00,65,0

149

0,73,00,5c,00,\ 6d,00,69,00,63,00,72,00,6f,00,73,00,6f,00,66,00,74,00,20,00,6 4,00,79,00,6e,\ 00,61,00,6d,00,69,00,63,00,73,00,20,00,63,00,72,00,6d,00,5c,0 0,63,00,6c,00,\ 69,00,65,00,6e,00,74,00,5c,00,62,00,69,00,6e,00,5c,00,63,00,7 2,00,6d,00,61,\ 00,64,00,64,00,69,00,6e,00,2e,00,64,00,6c,00,6c,00,00,00,6d,0 0,69,00,63,00,\ 72,00,6f,00,73,00,6f,00,66,00,74,00,20,00,64,00,79,00,6e,00,6 1,00,6d,00,69,\ 00,63,00,73,00,20,00,63,00,72,00,6d,00,00,00

Use this value for 32-bit versions of Microsoft Office and Microsoft Dynamics CRM for Outlook on 64-bit versions of Windows.
hex:01,00,00,00,8c,00,00,00,2e,00,00,00,63,00,3a,00,5c,00,70, 00,72,\ 00,6f,00,67,00,72,00,61,00,6d,00,20,00,66,00,69,00,6c,00,65,0 0,73,00,20,00,\ 28,00,78,00,38,00,36,00,29,00,5c,00,6d,00,69,00,63,00,72,00,6 f,00,73,00,6f,\ 00,66,00,74,00,20,00,64,00,79,00,6e,00,61,00,6d,00,69,00,63,0 0,73,00,20,00,\ 63,00,72,00,6d,00,5c,00,63,00,6c,00,69,00,65,00,6e,00,74,00,5 c,00,62,00,69,\ 00,6e,00,5c,00,63,00,72,00,6d,00,61,00,64,00,64,00,69,00,6e,0 0,2e,00,64,00,\ 6c,00,6c,00,00,00,6d,00,69,00,63,00,72,00,6f,00,73,00,6f,00,6 6,00,74,00,20,\ 00,64,00,79,00,6e,00,61,00,6d,00,69,00,63,00,73,00,20,00,63,0 0,72,00,6d,00,\ 00,00

Note This binary value is based on the default installation locations of the Crmaddin.dll file. By default, the Crmaddin.dll file is installed in one of the following file system locations: 150

C:\Program Files\Microsoft Dynamics CRM\Client\bin\crmaddin.dll C:\Program Files (x86)\Microsoft Dynamics CRM bin\crmaddin.dll If the Crmaddin.dll file is installed in a different location, the binary value in this step will be different. 7. Exit Registry Editor.

See Also
Microsoft Dynamics CRM 2011 for Outlook Installation Instructions Install Microsoft Dynamics CRM 2011 for Outlook without an Internet connection

Install Microsoft Dynamics CRM 2011 for Outlook without an Internet connection
This section applies to Microsoft Dynamics CRM for Microsoft Office Outlook when you use either Microsoft Dynamics CRM 2011 or Microsoft Dynamics CRM Online. There may be occasions when you have to install Microsoft Dynamics CRM for Outlook where there is no Internet connection available. Common occasions are when you are creating virtual demonstration environments, such as when you use Hyper-V, and environments that use firewalls or other security requirements that block Internet access. Note For more information about how to install other Microsoft Dynamics CRM 2011 and Microsoft Dynamics CRM Online applications, see How to install Microsoft Dynamics CRM 2011 without an Internet Connection. To install Microsoft Dynamics CRM for Outlook without an Internet connection, you must first download all prerequisite components. To do this, you will need a computer that has an Internet connection to download all the prerequisites beforehand. Notice that, when you download the Microsoft Dynamics CRM 2011 ISO from MSDN, or have a physical DVD that you are installing from, you will already have the Redist folder and all the prerequisites downloaded. However, if you download the Microsoft Dynamics CRM for Outlook installation media from the Microsoft Download Center, you must manually build this Redist prerequisite folder structure. 151

Step 1: Create the Redist folder structure

First, create the Redist folder structure in the installation media at the same level as the Server, Client, EmailRouter and BIDSExtensions folders. The installation media folder structure will appear similar to the following list. BIDSExtensions Client EmailRouter Redist Server Additional files such as autorun.inf, msvp100.dll, and so on. Important The folder structure mentioned here assumes that you are installing Microsoft Dynamics CRM 2011 for Outlook from the full installation media, such as from a DVD. When you download the Microsoft Dynamics CRM 2011 for Outlook installer from the Microsoft Download Center, the EmailRouter, Server, and BIDSExtensions folders are not included. In this situation, the Redist folder must be put in the parent directory where the installation files are initially extracted. For example, if the Microsoft Dynamics CRM for Outlook installation files are extracted to C:\mscrminstaller, then the Redist folder must be located in C:\mscrminstaller\Redist.

Step 2: Create the subfolders under the Redist folder

Create the following subfolders directly under the Redist folder. 1. dotNETFX 2. IDCRL 3. MSI45 4. MSOIDCRL 5. SQLCE 6. SQLExpr Only required if you install Microsoft Dynamics CRM for Microsoft Office Outlook with Offline Access 7. ReportViewer 152

8. WindowsIdentityFoundation

Step 3: Download the prerequisite files

Download the six prerequisite components and copy them into the Redist folder under the appropriate subfolders, by using the following list. 1. dotNETFX Prerequisite name: Microsoft .NET Framework 4 (stand-alone Installer) File name: dotNetFx40_Full_x86_x64.exe 2. IDCRL Prerequisite names: Windows Live ID Sign-in Assistant 6.5 (32-bit) Windows Live ID Sign-in Assistant 6.5 (64-bit) File names: wllogin_32.msi wllogin_64.msi 3. MSI45 Prerequisite names: Windows Installer 4.5 Redistributable (Windows 7 and Vista 32-bit) Windows Installer 4.5 Redistributable (Windows 7 and Vista 64-bit) Windows Installer 4.5 Redistributable (Windows XP 32-bit) File names: Windows6.0-KB942288-v2-x86.msu Windows6.0-KB942288-v2-x64.msu WindowsXP-KB942288-v3-x86.exe 4. MSOIDCRL Prerequisite names: Microsoft Online Services Sign-in Assistant (32-bit) 153

 Microsoft Online Services Sign-in Assistant (64-bit) File names: Note Both versions are named msoidcli. Therefore, you must rename each file by using the naming conventions described here. msoidcli_32.msi msoidcli_64.msi 5. SQLCE Prerequisite names: Microsoft SQL Server Compact 3.5 Service Pack 1 and Synchronization Services for ADO.NET
version 1.0 Service Pack 1 for Windows Desktop (32-bit)

Microsoft SQL Server Compact 3.5 Service Pack 1 and Synchronization Services for ADO.NET
version 1.0 Service Pack 1 for Windows Desktop (64-bit)

File names: SSCERuntime-ENU-x86.msi SSCERuntime-ENU-x64.msi 6. SQLExpr Prerequisite name: Microsoft SQL Server 2008 Express File name: SQLEXPR_x86_ENU.exe 7. ReportViewer Prerequisite name: Microsoft Report Viewer Redistributable 2010 File name: ReportViewer.exe 8. WindowsIdentityFoundation Prerequisite names: Note By default, Windows Identity Framework is included with Windows 8 and Windows Server 2012. Windows Identity Foundation, Windows 7 and Windows Server 2008 R2 (64-bit) 154

 Windows Identity Foundation, Windows 7 (32-bit) Windows Identity Foundation, Vista SP 2 and Windows Server 2008 SP 2 (64-bit) Windows Identity Foundation, Vista SP 2 and Windows Server 2008 SP 2 (32-bit) Windows Identity Foundation for Windows 2003 (64-bit) Windows Identity Foundation for Windows 2003 (32-bit) File names: Windows6.1-KB974405-x64.msu Windows6.1-KB974405-x86.msu Windows6.0-KB974405-x64.msu Windows6.0-KB974405-x86.msu Windows5.2-KB974405-x64.exe Windows5.2-KB974405-x86.exe Now that you have all the prerequisites downloaded and saved in the correct folders, you can continue with the Microsoft Dynamics CRM for Outlook installation without an Internet connection.

See Also
Installing on a computer that does not have Microsoft Dynamics CRM for Outlook installed Upgrade Microsoft Dynamics CRM 4.0 for Outlook to Microsoft Dynamics CRM 2011 for Outlook Microsoft Dynamics CRM 2011 Language Pack Installation Instructions

Microsoft Dynamics CRM 2011 Language Pack Installation Instructions

The Microsoft Dynamics CRM Language Pack enables users to change the language of the user interface or Help that is displayed in the application. For example, your multinational organization might have standardized on an English user interface to simplify internal training and troubleshooting, but if you prefer to read Help in your native language of German, you can specify that Microsoft Dynamics CRM display Help in German. 155

Overview -- Language Pack Installation

After installing and provisioning the Microsoft Dynamics CRM Language Pack, its capabilities and corresponding options are available from Microsoft Dynamics CRM client applications. Users do not start Microsoft Dynamics CRM Language Pack as a separate application. Note The Microsoft Dynamics CRM Language Pack installation software is separate from the Microsoft Dynamics CRM installation software, and is found in its own download or on its own installation disk. The Language Pack changes only the Microsoft Dynamics CRM user interface and Help.

In This Section
Install and deploy a Language Pack Upgrade and deploy a Language Pack Language Pack installation issues

See Also
Microsoft Dynamics CRM 2011 for Outlook Installation Instructions

Install and deploy a Language Pack

Follow the procedures in this section to install and deploy the Microsoft Dynamics CRM Language Pack.

In This Topic
Step1: Install the Language Pack in the deployment Step 2: Provision the Language Pack in your Microsoft Dynamics CRM deployment Step 3: Select the language to display the user interface and help

Step1: Install the Language Pack in the deployment

If you have users who are running Microsoft Dynamics CRM for Microsoft Office Outlook, in addition to installing Language Pack on the computer running Microsoft Dynamics CRM Server 156

2011, you must also install the same Language Packs on the computer where Microsoft Dynamics CRM for Outlook is installed.

To install a Language Pack in the deployment, follow these steps: 1. Log on to the computer where Microsoft Dynamics CRM Server 2011 or Microsoft Dynamics CRM for Outlook is installed. 2. Verify that you have Administrator privileges on the computer and either Full or Administrator privileges on Microsoft Dynamics CRM. 3. Where the Language Pack files are located, double-click the file MUISetup_<loc_code>_<proc_type>.msi, where: <loc_ code> is the locale code for the Language Pack that you are installing. (For example, "1031" for German or "1041" for Japanese.) <proc_type> specifies the type of processor the server is running. (For example, "amd64.") 4. On the End User License Agreement page, review the information and, if you accept the license agreement, click I accept the terms in the license agreement, and then click Install. Setup copies the Language Pack files to the correct locations in the Microsoft Dynamics CRM deployment. By default, the Language Pack files are copied to drive:\Program Files\Microsoft CRM\LangPacks\<loc_ code>, where <loc_ code> is the locale code for the Language Pack that you are installing. 5. To complete the installation, click Finish. Repeat the process for each Language Pack that you want to install.

Step 2: Provision the Language Pack in your Microsoft Dynamics CRM deployment
Before users can start using a Language Pack to display a language, the Language Pack must be provisioned in your Microsoft Dynamics CRM deployment.

To provision the Language Packs in your deployment, follow these steps: 157

1. Start the Microsoft Dynamics CRM web application. 2. Verify that you have either Full or Administrator privileges on Microsoft Dynamics CRM. 3. In the Navigation Pane, click Settings. 4. Under Settings, click Administration, and then click Languages. The Language Settings dialog box opens. In it, are listed each Language Pack installed in your Microsoft Dynamics CRM deployment, with a check box to the left of each listed Language Pack. 5. For each Language Pack that you want to provision (enable), select the check box next to it. For each Language Pack that you want to unprovision (disable), clear the check box. 6. Click Apply. 7. Click OK on any confirmation dialog boxes that open. Note It may take several minutes for Microsoft Dynamics CRM to provision or unprovision the languages. 8. To close the Language Settings dialog box, click Close.

Step 3: Select the language to display the user interface and help
Each User can select the language to display in both the Microsoft Dynamics CRM Web client and Microsoft Dynamics CRM for Outlook applications.

To select the language to display, follow these steps: 1. Open the Set Personal Options page, as follows: If you are using Microsoft Dynamics CRM Web client, click the File tab, and then click Options. If you are using Microsoft Dynamics CRM for Outlook, on the top menu bar, click CRM, and then click Options. 2. Click the Languages tab. 3. In the User Interface Language list, select the language in which you want to display 158

Microsoft Dynamics CRM. 4. In the Help Language list, select the language in which you want to display Microsoft Dynamics CRM Help. 5. To save your changes and close the dialog box, click OK. Note In Microsoft Dynamics CRM for Outlook, the user language settings only apply to Microsoft Dynamics CRM for Outlook features, such as the user interface display of the CRM menu, and do not affect other areas of Microsoft Office Outlook. To be able to display all the Microsoft Dynamics CRM for Outlook user interface or Help in multiple languages, you must install one or more Office Language Packs. For more information about Office Language Packs, see the Microsoft Dynamics CRM for Outlook Help.

See Also
Microsoft Dynamics CRM 2011 Language Pack Installation Instructions Upgrade and deploy a Language Pack

Upgrade and deploy a Language Pack

After you upgrade a Microsoft Dynamics CRM 4.0 Server to Microsoft Dynamics CRM Server 2011, you can then upgrade and provision Language Packs.

To upgrade and provision a Language Pack: 1. On each computer that was upgraded to Microsoft Dynamics CRM Server 2011, uninstall the Microsoft Dynamics CRM 4.0 Language Packs using the Windows Server uninstall function. 2. Reinstall and deploy each Language Pack, as described previously.

See Also
Install and deploy a Language Pack Language Pack installation issues

159

Language Pack installation issues

This section describes how to troubleshoot Language Pack installation issues.

You receive a "Setup could not install Language Pack Name" error message
This issue can occur when the Microsoft Dynamics CRM Server 2011 or Microsoft Dynamics CRM for Outlook applications are not installed on the computer before you run MUISetup_<loc_code>_<proc_type>.msi to install a Language Pack. To resolve this issue, you must perform the following procedures: If you are installing the Language Pack for the Microsoft Dynamics CRM deployment, you must install the Language Pack on the computer where Microsoft Dynamics CRM Server 2011 is installed. If you are installing the Language Pack for Microsoft Dynamics CRM for Outlook, you must install the Language Pack on the computer where Microsoft Dynamics CRM for Outlook is installed.

See Also
Microsoft Dynamics CRM 2011 Language Pack Installation Instructions Microsoft Dynamics CRM 2011 Uninstall, Repair, and Change Instructions

Microsoft Dynamics CRM 2011 Uninstall, Repair, and Change Instructions

This section describes how to uninstall, repair, or change a Microsoft Dynamics CRM application. Uninstalling Microsoft Dynamics CRM and purging the computer system of all Microsoft Dynamics CRM data and system changes involves a series of automated and manual procedures. These procedures are the same whether the Microsoft Dynamics CRM involves one computer or several. These procedures also involve working in the following areas: Microsoft Dynamics CRM Internet Information Services (IIS) Microsoft SQL Server 160

 Microsoft SQL Server Reporting Services Active Directory

In This Section
Uninstall, change, or repair Microsoft Dynamics CRM Server 2011 Uninstall or repair Microsoft Dynamics CRM Reporting Extensions Uninstall or repair Microsoft Dynamics CRM Report Authoring Extension Uninstall, change, or repair E-mail Router Uninstall or repair Microsoft Dynamics CRM for Outlook Uninstall or repair a Language Pack

See Also
Microsoft Dynamics CRM 2011 Language Pack Installation Instructions

Uninstall, change, or repair Microsoft Dynamics CRM Server 2011

To perform Microsoft Dynamics CRM Server 2011 maintenance, select from the following options that are available. Before selecting an option, you must start Programs and Features. Log on to the computer where the Microsoft Dynamics CRM application is installed. Then, click Start, type Programs and Feat ures, and then click Programs and Features in the Programs list. Uninstall. Selecting this option will remove Microsoft Dynamics CRM Server 2011 from the computer. To do this go to Programs and Features, right-click Microsoft Dynamics CRM Server 2011, click Uninstall/Change, select Uninstall to remove Microsoft Dynamics CRM Server 2011, and then click Uninstall. Follow the instructions that are on the screen. Important The Microsoft Dynamics CRM uninstall process does not remove some components, such as the SQL Server databases, Active Directory groups, or the Microsoft Dynamics CRM website (when the Web site is not created by Setup). Those components must be removed manually.

161

 Configure. To add or remove one or more Microsoft Dynamics CRM server roles, right-click Microsoft Dynamics CRM Server 2011, click Uninstall/Change, select Configure, and then click Next. Follow the instructions that are on the screen to select or clear one or more server roles. For more information about Microsoft Dynamics CRM server roles, see Microsoft Dynamics CRM 2011 Server roles in the Planning Guide. Repair. To repair a Microsoft Dynamics CRM Server 2011 installation, right-click Microsoft Dynamics CRM Server 2011, click Uninstall/Change, select Repair, and then click Next. Follow the instructions that are on the screen. Note Repairing a Microsoft Dynamics CRM Server 2011 installation reinstalls the program files. It has no effect on the databases. To recover from Microsoft Dynamics CRM database problems, you must restore the MSCRM_CONFIG and OrganizationName_MSCRM databases. For information about database backup and failure recovery, see Backing up SQL Server, including Reporting Services in Backing Up the Microsoft Dynamics CRM System in the Operating and Maintaining Guide.

Components not removed during a Microsoft Dynamics CRM Server 2011 uninstall
The following system components, although installed during Microsoft Dynamics CRM Server Setup, are not removed when you uninstall Microsoft Dynamics CRM Server 2011. Windows role services: Web Server Role Services Static Content Default Document Directory Browsing HTTP Errors ASP.NET Microsoft .NET Framework Extensibility ISAPI Extensions ISAPI Filters HTTP Logging 162

 Request Monitor Windows Authentication Request Filtering Static Content Compression Dynamic Content Compression IIS Management Console IIS 6 Metabase Compatibility File services role services: Indexing Service Windows features: Microsoft .NET Framework HTTP Activation Windows PowerShell Windows Process Activation

See Also
Microsoft Dynamics CRM 2011 Uninstall, Repair, and Change Instructions Uninstall or repair Microsoft Dynamics CRM Reporting Extensions

Uninstall or repair Microsoft Dynamics CRM Reporting Extensions

To perform Microsoft Dynamics CRM Reporting Extensions maintenance, select from the following options that are available. Before selecting an option, you must start Programs and Features. Log on to the computer where the Microsoft Dynamics CRM application is installed. Then, click Start, type Programs and Features, and then click Programs and Features in the Programs list. Uninstall. To remove (uninstall) the CRM Reporting Extensions, go to Programs and Features, right-click Microsoft Dynamics CRM Reporting Extensions, click 163

Uninstall/Change, select Uninstall, and then click Uninstall. Follow the instructions on the screen. Repair. To repair the CRM Reporting Extensions, right-click Microsoft Dynamics CRM Reporting Extensions, click Uninstall/Change, select Repair, and then click Next. Follow the instructions on the screen.

See Also
Microsoft Dynamics CRM 2011 Uninstall, Repair, and Change Instructions Uninstall or repair Microsoft Dynamics CRM Report Authoring Extension

Uninstall or repair Microsoft Dynamics CRM Report Authoring Extension

To perform Microsoft Dynamics CRM Report Authoring Extension maintenance, select from the following options. Before you select an option, you must start Programs and Features. Log on to the computer where the Microsoft Dynamics CRM application is installed. Then, click Start, type Programs and Features, and then click Programs and Features in the Programs list. Uninstall. To remove (uninstall) Microsoft Dynamics CRM Report Authoring Extension, go to Programs and Features, right-click Microsoft Dynamics CRM Report Authoring Extension, click Uninstall/Change, select Uninstall, and then click Uninstall. Follow the instructions on the screen. Repair. To repair Microsoft Dynamics CRM Report Authoring Extension, right-click Microsoft Dynamics CRM Report Authoring Extension, click Uninstall/Change, select Repair, and then click Next. Follow the instructions on the screen.

See Also
Microsoft Dynamics CRM 2011 Uninstall, Repair, and Change Instructions Uninstall, change, or repair E-mail Router

164

Uninstall, change, or repair E-mail Router

This section applies to Microsoft Dynamics CRM Online and on-premises versions of Microsoft Dynamics CRM 2011. To uninstall, change, or repair E-mail Router components, select from the following options. Before selecting an option, you must start Programs and Features. Log on to the computer where the Microsoft Dynamics CRM application is installed. Then, click Start, type Programs and Features, and then click Programs and Features in the Programs list. Uninstall. 1. On the Uninstall or change a program page, click Microsoft Dynamics CRM E-mail Router and then click Uninstall/Change. The Microsoft Dynamics CRM E-mail Router Maintenance wizard starts. 2. Select Uninstall and click Uninstall. 3. After the E-mail Router components have been uninstalled, click Finish on the Microsoft Dynamics CRM E-mail Router setup completed page. Change. To add or remove E-mail Router or Rule Deployment Wizard, follow these steps. 1. On the Uninstall or change a program page, right-click Microsoft Dynamics CRM E-mail Router and then click Uninstall/Change. The Microsoft Dynamics CRM E-mail Router Maintenance wizard starts. 2. Select Add/Remove Features and click Next. 3. On the Select Router Components page, select Microsoft Dynamics CRM E-mail Router Service or Rule Deployment Wizard, or you can select both items. Note Clearing the Microsoft Dynamics CRM E-mail Router Service or Rule Deployment Wizard check box does not cause the application to be uninstalled. 4. Click Next. Follow the instructions on the screen. Repair. 1. On the Uninstall or change a program page, click Microsoft Dynamics CRM E-mail Router and then click Uninstall/Change. The Microsoft Dynamics CRM E-mail Router Maintenance wizard starts. 2. Select Repair and click Next. Follow the instructions on the screen. Note 165

For on-premises deployment of Microsoft Dynamics CRM 2011, during Microsoft Dynamics CRM Server Setup, the computer where the E-mail Router is installed is added to the Active Directory PrivUserGroup security group. However, if the E-mail Router is uninstalled, the computer is not removed from the security group, and therefore has an unnecessary permission. If you uninstall the E-mail Router and decide not to reinstall it on the same computer, we recommend that you manually remove the computer from the PrivUserGroup security group. In Microsoft Dynamics CRM 4.0, the following configuration files were not deleted from the Drive:\Microsoft CRM Email\Service directory: EncryptionKey.xml, Microsoft.Crm.Tools.EmailAgent.Configuration.bin, and Microsoft.Crm.Tools.EmailAgent.xml. In Microsoft Dynamics CRM 2011 these files are removed if you uninstall the E-mail Router.

See Also
Microsoft Dynamics CRM 2011 Uninstall, Repair, and Change Instructions Uninstall or repair Microsoft Dynamics CRM for Outlook

Uninstall or repair Microsoft Dynamics CRM for Outlook

This section applies to Microsoft Dynamics CRM Online and on-premises versions of Microsoft Dynamics CRM 2011. Note If an uninstallation is not completed while you are logged on to the client computer as the user who originally installed the application, the offline database will remain attached to the instance of Microsoft SQL Server 2008 Express Edition. After the uninstallation is complete, you can manually detach the offline database. When you uninstall Microsoft Dynamics CRM for Outlook the program files are removed and the application is no longer available. Instead of uninstall, you can disable Microsoft Dynamics CRM for Outlook. To disable, click Start, click All Programs, click Microsoft Dynamics CRM 2011, and then click Diagnostics. On the Advanced Troubleshooting tab, click Disable, and then click Save. Later, you can enable Microsoft Dynamics CRM for Outlook by following the same procedure. 166

Uninstall or Repair To uninstall or repair Microsoft Dynamics CRM for Outlook, select from the following available options. Before you select an option, you must start Programs and Features. Log on to the computer where the Microsoft Dynamics CRM application is installed. Then, click Start, type Programs and Features, and then click Programs and Features in the Programs list.

To uninstall Microsoft Dynamics CRM for Outlook 1. On the Uninstall or change a program page, click Microsoft Dynamics CRM 2011 for Microsoft Office Outlook and then click Uninstall/Change. The Microsoft Dynamics CRM 2011 for Outlook Setup wizard starts. 2. On the Choose the installation you want page, click Uninstall. 3. When the wizard finishes, click Close. Note Uninstalling Microsoft Dynamics CRM for Outlook might require that you restart the computer.

To repair Microsoft Dynamics CRM for Outlook 1. On the Uninstall or change a program page, click Microsoft Dynamics CRM 2011 for Microsoft Office Outlook and then click Uninstall/Change. The Microsoft Dynamics CRM 2011 for Outlook Setup wizard starts. 2. On the Choose the installation you want page, click Repair. 3. When the wizard finishes, click Close. Note To uninstall or repair Microsoft Dynamics CRM for Microsoft Office Outlook on previous versions of Microsoft Windows, follow steps similar to those in the preceding procedures: Open the Microsoft Dynamics CRM 2011 for Outlook Setup wizard and then select Uninstall or Repair.

167

Files not removed during a Microsoft Dynamics CRM for Outlook uninstall
The following files, although installed during Microsoft Dynamics CRM 2011 for Outlook Setup, are not removed when you uninstall Microsoft Dynamics CRM for Outlook. Program Files\Microsoft Dynamics CRM\Client\ConfigWizard\CrmForOutlookInstaller.exe Program Files\Microsoft Dynamics CRM\Client\ConfigWizard\CrmForOutlookInstaller.exe Program Files\Microsoft Dynamics CRM\Client\DatabaseFixes\dbhotfix_client_install.xml Program Files\Microsoft Dynamics CRM\Client\DatabaseFixes\dbupdateactions\install\dbhotfix_release.xml Program Files\Microsoft Dynamics CRM\Client\DatabaseFixes\dbupdateactions\install\dbhotfix_test_111111.sql Program Files\Microsoft Dynamics CRM\Client\DatabaseFixes\dbupdateactions\install\dbhotfix_test_222222.sql Program Files\Microsoft Dynamics CRM\Client\DatabaseFixes\dbupdateactions\uninstall\dbhotfix_release.xml Program Files\Microsoft Dynamics CRM\Client\DatabaseFixes\dbupdateactions\uninstall\dbhotfix_test_111111.sql Program Files\Microsoft Dynamics CRM\Client\DatabaseFixes\dbupdateactions\uninstall\dbhotfix_test_222222.sql Windows\CrmClient.mif

See Also
Microsoft Dynamics CRM 2011 Uninstall, Repair, and Change Instructions Uninstall or repair a Language Pack

Uninstall or repair a Language Pack

To perform Language Pack maintenance, select from the following options that are available. Before you select an option, you must start Programs and Features. Log on to the computer where the Microsoft Dynamics CRM application is installed. Then, click Start, type Programs and Features, and then click Programs and Features in the Programs list. 168

Important Rather than uninstall a Language Pack that is installed on the Microsoft Dynamics CRM server, you can disable a Language Pack in the organization. After you do this, users will no longer be able to see the Microsoft Dynamics CRM user interface and Help in the language that you disabled. Later, you can enable the Language Pack by clicking the language in the Language Settings list. When a Language Pack is removed or disabled, users who have that Language Pack language selected on the Personal Preferences form will have to use the base language. For example, consider the following scenario. A Microsoft Dynamics CRM deployment has English as the base language, but the Spanish Language Pack was used in the organization. Then, when the system administrator disables (or uninstalls) the Spanish Language Pack, users who selected the user interface to be in Spanish will see it in English. To disable a Language Pack, see the Microsoft Dynamics CRM Help. Uninstall. Selecting this option will remove the selected Language Pack from the computer. If you uninstall a Language Pack, you must reinstall and then enable it before it is available to users again.

To uninstall a Language Pack 1. Right-click the Language Pack, such as Microsoft Dynamics CRM German Language Pack, and then click Uninstall. 2. If other users are logged on to the computer, you will receive a warning message. Click Continue if you want to continue and remove the Language Pack. 3. Click Yes to confirm that you want to remove the Language Pack and follow the instructions that are on your screen. Repair. To repair a damaged Language Pack installation, right-click Language Pack, click Repair, and then follow the instructions that are on your screen.

See Also
Microsoft Dynamics CRM 2011 Uninstall, Repair, and Change Instructions Use the Command Prompt to Install Microsoft Dynamics CRM 2011

169

Use the Command Prompt to Install Microsoft Dynamics CRM 2011

You can install Microsoft Dynamics CRM Server, Microsoft Dynamics CRM Reporting Extensions, Microsoft Dynamics CRM for Microsoft Office Outlook, and the Microsoft Dynamics CRM E-mail Router from their respective installation disks or file download location by using the command prompt. The required setup information is provided to the Setup program both as commandline parameters and as an XML configuration file that the Setup program references. One advantage of using the command prompt to install Microsoft Dynamics CRM is that you do not have to attend the installation. Attended installation requires you to make decisions and provide information so that installation can run successfully. Unattended installation, by using the command prompt, requires you to provide the installation information as command-line parameters and an XML configuration file. No other action is required until the Setup program is finished. Warnings and installation progress can be logged to a file that you can view and analyze later. Important If you install a Microsoft Dynamics CRM 2011 server application on Windows Server 2012 you must download the latest Setup update by using patch update = true in the XML configuration file. For more information about the patch XML element see Microsoft Dynamics CRM 2011 Server XML configuration file. Additionally, you must apply Microsoft Dynamics CRM 2011 Update Rollup 13 or a later update rollup after Setup is finished. For more information, see Supported Windows Server 2012 editions. Tip To help troubleshoot invalid XML error messages, open the XML configuration file by using Internet Explorer to help indicate where the problem occurs in the file.

General procedures
The procedures for accessing the Setup program on the individual installation disk or file download location are basically the same. The prerequisites for each of the Microsoft Dynamics CRM system components as discussed in previous sections also apply.

To access the Setup program, follow these steps: 1. Log on to the computer as a member of the Domain Users Active Directory directory service group and Administrators group on the local computer. If you are installing 170

Microsoft Dynamics CRM Server 2011 using a Full Server role, the user running Setup must be a member of the local administrators group on the computer that has Microsoft SQL Server installed, and permissions on the organizational unit to create or modify Active Directory groups in the domain where Microsoft Dynamics CRM Server 2011 is installed. If you are using pre-created groups, you must have read and write permission to each group. 2. If you are installing from an installation disk, insert the Microsoft Dynamics CRM Server 2011 or the Microsoft Dynamics CRM for Microsoft Office Outlook installation disk into the CD/DVD drive. The Autorun screen appears. Close the Autorun screen. 3. Open a Command Prompt window. 4. At the command prompt, change to the CD/DVD drive or change to the location where the Microsoft Dynamics CRM installation files are located: SetupServer.exe for Microsoft Dynamics CRM Server 2011 is located in the Server folder of the Microsoft Dynamics CRM Server 2011 installation disk or file download location. SetupSrsDataConnector.exe for the Microsoft Dynamics CRM Reporting Extensions is located in the \SrsDataConnector folder on the Microsoft Dynamics CRM Server 2011 installation disk or file download location. Setupclient.exe for Microsoft Dynamics CRM for Outlook is located in the Client folder of the Microsoft Dynamics CRM for Outlook installation disk or file download location. SetupEmailRouter.exe for Microsoft Dynamics CRM E-mail Router is located in the \EmailRouter folder on the Microsoft Dynamics CRM Server 2011 installation disk or file download location.

In This Section
Install Microsoft Dynamics CRM Server 2011 Microsoft Dynamics CRM 2011 Server XML configuration file Install Microsoft Dynamics CRM Server 2011 roles Install Microsoft Dynamics CRM Reporting Extensions (2) Install Microsoft Dynamics CRM for Outlook using a Command Prompt Install Microsoft Dynamics CRM E-mail Router Microsoft Dynamics CRM Server 2011 installation troubleshooting

171

See Also
Microsoft Dynamics CRM 2011 Installing Guide Microsoft Dynamics CRM 2011 Post-Installation and Configuration Guidelines

Install Microsoft Dynamics CRM Server 2011

The following command will install Microsoft Dynamics CRM Server 2011: SetupServer.exe [/Q] [/InstallAlways] [/L [drive:][[path] logfilename.log]] [/config [drive:] [[path] configfilename.xml]]

Parameters
None Used without parameters, Setup will run with all display screens. /Q Quiet mode installation. This parameter requires a configuration file in XML format. The /config parameter contains the name of the XML configuration file. No dialog boxes or error messages will appear on the display screen. /InstallAlways This parameter forces Setup to ignore the installation state and operate in install mode. When you use this parameter, Setup will try to install on a server where Microsoft Dynamics CRM is already installed. /QR Requires a configuration file in XML format specified by the /config parameter. Similar to the /Q parameter, but displays installation progress bars and all error messages. /L [drive:][[path] logfilename.log]] Specifies the location and name of the log file to record installation activity. Additional log files may be created during prerequisites installation and will be located in the path specified. The path value cannot be a relative path, such as ..\..\crmlog.txt. If you do not specify a name or location, a log file will be created in the drive:\Documents and 172

Settings\UserName\Application Data\Microsoft\MSCRM\Logs folder, where UserName is the account name of the user running Setup. /config [drive:] [[path] configfilename.xml]] The /config parameter uses the specified XML configuration file to provide Setup with the additional information to complete installation successfully. An example XML configuration file is discussed in the following section. Notice that when you specify a configuration file without the /Q or /QR parameter, Setup screens appear filled with the information from the configuration file.

See Also
Use the Command Prompt to Install Microsoft Dynamics CRM 2011 Microsoft Dynamics CRM 2011 Server XML configuration file

Microsoft Dynamics CRM 2011 Server XML configuration file

The /config [drive:] [[path] configfilename.xml]] command-line parameter provides Microsoft Dynamics CRM Server Setup with required information. The information supplied by the XML configuration file is the same required by each installation screen. Important The XML elements must be in English (US). An XML configuration file that has localized XML elements will not work correctly. For example, if you have a German version of Microsoft Dynamics CRM Server 2011, the XML file elements must still be English (US). By default, Setup will use UTF-8 encoding for the Setup XML configuration file. Setup cannot load an XML configuration file when there are extended characters in the file. You will receive an error message from Setup that the XML file is invalid. If the XML configuration file contains extended characters, you can work around this issue by saving the XML configuration file by using Unicode encoding. To do this, open the XML configuration file in Notepad, click Save As, in the Encoding list select Unicode, and then click Save. An explanation of each XML element and a sample XML file for a Full Server installation follows. For information about how to install separate server roles by using the command prompt, see Install Microsoft Dynamics CRM Server 2011 roles in this guide. 173

<CRMSetup> </CRMSetup>

The configuration file must be a valid XML file that uses <CRMSetup> as the root element.

<Server> </Server>

Specifies a Microsoft Dynamics CRM Server 2011 installation. All the Microsoft Dynamics CRM Server 2011 entries that follow must be inside the <Server> elements.

<InstallType>Uninstall/Repair/Configure</InstallType>

Specifies the type of installation that Setup will perform. The following options are available: Uninstall. Uninstalls Microsoft Dynamics CRM Server 2011. Repair. Starts Setup in repair mode. Configure. Starts Setup in configuration mode.

<Patch update="true"/"false">\\ServerName\ShareName\Patch_Location</Patch>

Determines the behavior of the update Microsoft Dynamics CRM Server Setup technology. This feature lets Setup perform a one-time search for, and if applicable, download to apply the latest installation files for Microsoft Dynamics CRM. By default, this element does not specify a location, which configures Setup to search for available updates by using Microsoft Update. If you want Setup to install updates from another location, such as a share on your network, add the file paths to the .msp file in the element, as shown in the following topic. update Specifies whether Setup will look for, download, and apply updates for Microsoft Dynamics CRM Server Setup. We recommend that you let Setup download the latest version by specifying true. By default, this value is set to false. If the value is set to false, Setup will ignore this step and continue with the installation. However, if running Setup by using the /Q or /QR parameter, 174

you must specify this element. For more information about how to obtain Setup updates, see How to obtain the setup updates for Microsoft Dynamics CRM 2011.

<SqlServer>SQLServername\InstanceName</SqlServer>

Specifies the name of the instance of Microsoft SQL Server that will manage the Microsoft Dynamics CRM Server 2011 database files. If you use the default instance, you can provide the name of the computer where SQL Server is installed. If SQL Server is running on the computer where you are installing Microsoft Dynamics CRM Server 2011, you can specify ". " or "localhost".

<Database create="true"/"false" update="true"/"false"/>

create Values for this parameter are either true or false. True causes Setup to create a new Microsoft Dynamics CRM configuration database. False causes Setup to connect to an existing Microsoft Dynamics CRM configuration database. update Values for this parameter are either true or false. When you select true, Setup will write the appropriate server deployment information to the configuration database (MSCRM_CONFIG). Select false only when you are using a preexisting configuration database and you do not want Setup to update the server deployment information. When you select false, the appropriate server deployment information for the computer where Microsoft Dynamics CRM Server 2011 is being installed must already exist in the configuration database for Setup to complete successfully. The default value is true.

<Organization>Organization friendly or long name</Organization>

Specifies the long name of your organization. The name can be up to 250 characters long and extended characters are supported.

175

<OrganizationUniqueName>Unique name</OrganizationUniqueName>

UniqueName Specifies the name of your organization that will be used in the URL that users will use to access the deployment. There is a 30 character limit. Extended characters or spaces are not allowed. If you do not specify this element or leave the value blank, Setup will generate a short name based on the <Organization> element value. Important The unique organization name will be used to construct the URL for users to sign-in to the application. Therefore, we recommend that you limit the length of the unique organization name to reduce the overall length of the URL.

<muoptin optin="true/false" />

Specifies whether to use Microsoft Update to download and install updates to Microsoft Dynamics CRM Server 2011 and other installed applications. After the installation is completed, this feature helps keep your computer up-todate on an ongoing basis. True. When you specify this option, Setup will opt in to Microsoft Update as the update service and use the Windows automatic updating settings on the computer. Windows automatic update settings can be viewed in Windows Update in Control Panel. Microsoft Update helps make sure that your computer has the latest technology, which can help reduce the risk of vulnerabilities and security issues. False. When you specify this option, Setup will not change the existing Windows automatic update settings. If the computer is not already configured to use Microsoft Update as the update service, we recommend that you have another method to install updates on the computer, such as by using Microsoft Windows Update Services (WSUS). If left blank, a value of false will be selected.

<OU> OU=value,DC=value,DC=value,DC=value,DC=value</OU>

The <OU> element specifies the Active Directory organizational unit (OU) where the security groups will be created, for example, <OU> OU=CRM, DC=MySubDomain, DC=MyDomain, DC=com</OU>.

176

Important You cannot use the <Groups> element with the <OU> element. Setup will not continue if you specify both elements together.

<PreferredDC>servername.domain.com</PreferredDC>

Specifies the domain controller to contact when performing operations that require Active Directory. If not specified, Setup will use the first domain controller available. This setting is only available when you use a configuration file.

<LicenseKey>KeyValue</LicenseKey>

Specifies the product key for this deployment. The configuration file can contain only one Microsoft Dynamics CRM product key. For example: <licenseKey>XXXXX-XXXXX-XXXXX-XXXXX-XXXXX</licenseKey> Note If you purchase Microsoft Dynamics CRM through a Microsoft Volume Licensing program, the license key is provided in the license.txt file. The license.txt file is included in the Microsoft Dynamics CRM installation files.

<WebsiteUrl Create="true"/"false" port="TCPportnumber">path</WebsiteUrl>

Specifies the Web site to be used for Microsoft Dynamics CRM Server 2011.Use Create="true" to create a new Microsoft Dynamics CRM website and leave the value between the element tags blank. Use port="TCPportnumber", where TCPportnumber is a valid and available TCP port number, to specify the port for connecting to the Microsoft Dynamics CRM Server 2011 application. If left blank, the port number that will be used is 5555. Specify Create="false" to use an existing Web site and then you must type the Web site path in the element tags by using one of the following formats. When you use the Create="false" attribute, the port attribute is ignored. For example: 177

 http://server:port/ or http:// server.contoso.com /LM/W3SVC/n, where n is the Web site ID. 1 is the default Web site.

<Help anonymous="true"/"false">http://host/Help</Help>

Optional element to specify a different URL where Microsoft Dynamics CRM Help is located. This setting is typically used in a multi-server deployment or to replace the default URL such as when using a host header. If you select false to disable anonymous access, it may produce repeated login prompts for users who access Microsoft Dynamics CRM Help. This setting is only available when you use a configuration file.

<InstallDir>c:\program files\Microsoft Dynamics CRM</InstallDir>

Specifies the folder in which application files will be installed. By default, Setup will use the folder C:\Program Files\Microsoft Dynamics CRM.

<basecurrency isocurrencycode="CurrencyCode" currencyname="CurrencyName" currencysymbol="CurrencySymbol" currencyprecision=2"/"3"/"4/>

isocurrencycode Specifies the ISO three-letter currency-code, display name, and symbol to use for the base currency. For example, if you want to use U.S. dollars as the base currency, use isocurrencycode="USD". You must use a valid ISO currency description for the isocurrencycode attribute. currencyname and currencysymbol You must also specify the currency-name and currency-symbol display names for the ISO base currency. For example, if the ISO currency code is USD, the currency name should be "US Dollar" and the currency symbol should be "$". However, you can use any string that you want for these attributes. Important After Setup is complete, you cannot change the base ISO currency code. However, you can change the base-currency name, base-currency symbol, and base-currency precision. 178

A list of currently supported ISO currency codes is available in Microsoft Dynamics CRM 2011 currency support in the Planning Guide. The currency codes are provided from Microsoft .NET Framework and may change. currencyprecision You must specify the precision for the base currency that you specified in the currencycode attribute. Valid values depend on the type of currency that you specify. For example, USD valid values are 1 9 and the default value is 2.

<OrganizationCollation>CollationName</OrganizationCollation>

This optional element specifies the SQL Server database collation name to use for the organization database. The default collation depends on the language of Microsoft Dynamics CRM Server 2011 that you are installing, for example, Latin1_General_Cl_Al, which is the default collation for English (US) language deployments. For more information about database collation, see the Microsoft MSDN Library Web site Using SQL Server Collations.

<CrmServiceAccount type="DomainUser"/"NetworkService"> <ServiceAccountLogin>Domain\User</ServiceAccou ntLogin> <ServiceAccountPassword>password</ServiceAccountPassword> </CrmServiceAccount>

Specifies the Microsoft Dynamics CRM service account used to run the Microsoft Dynamics CRM Unzip Service and ASP.NET AppPool application pool identity. Accepted values are DomainUser, which will use the specified domain user provided in the <prefixServiceAccount> element or NetworkService, which uses the Network Service system account. However, using the Network ServiceNetwork system account is not recommended because it may limit some database operations such as organization create, import, upgrade, or update. By default, Setup will use the DomainUser option. If DomainUser or no type is specified, <ServiceAccountLogin> and <ServiceAccountPassword> are required. When you run Setup by using the /Q or /QR parameter, if this element is not specified the Network Service account will be used. Warning Maintaining the configuration file that has <ServiceAccountLogin> and 179

<ServiceAccountPassword> values specified is a security risk because you are storing a password in plain text. Delete these elements as soon as the configuration file is used to install Microsoft Dynamics CRM Server 2011. We strongly recommend that you select a low-privilege domain account that is dedicated to running these services and is not used for any other purpose. Additionally, the user account that is used to run a Microsoft Dynamics CRM service cannot be a Microsoft Dynamics CRM user. This domain account must be a member of the Domain Users group. Additionally, if the Asynchronous Service and Sandbox Processing Service roles are installed, such as in a Full Server or a Back End Server installation, the domain account must a member of the Performance Log Users security group.

<SandboxServiceAccount type="DomainUser"/"NetworkService"> <ServiceAccountLogin>Domain\User</ServiceAccountLogin> <ServiceAccountPassword>password</ServiceAccountPassword></SandboxServiceAccount>

Specifies the service account to use for the Sandbox Processing Service. Accepted values are DomainUser, which will use the specified domain user provided in the <prefixServiceAccount> element or NetworkService, which uses the Network Service system account. However, using the Network Service system account is not recommended because it may limit some database operations such as organization create, import, upgrade, or update. By default, Setup will use the DomainUser option. If DomainUser or no type is specified, <ServiceAccountLogin> and <ServiceAccountPassword> are required. When you run Setup by using the /Q or /QR parameter, if this element is not specified the Network Service account will be used. Warning Maintaining the configuration file that has <ServiceAccountLogin> and <ServiceAccountPassword> values specified is a security risk because you are storing a password in plain text. Delete these elements as soon as the configuration file is used to install Microsoft Dynamics CRM Server 2011. If you do not specify this element, Setup will use the account specified in the <CrmServiceAccount> element to run this service. Therefore, we recommend that you specify a different low-privilege user account for each of the Microsoft Dynamics CRM service accounts.

180

<DeploymentServiceAccount type="DomainUser"/"NetworkService"><ServiceAccountLogin>Domain\User</ServiceAccountL ogin><ServiceAccountPassword>password</ServiceAccountPassword><DeploymentServiceAcc ount>

Specifies the service account to use for the Deployment Web Service. Accepted values are DomainUser, which will use the specified domain user provided in the <prefixServiceAccount> element or NetworkService, which uses the Network Service system account. However, using the Network Service system account is not recommended because it may limit some database operations such as organization create, import, upgrade, or update. By default, Setup will use the DomainUser option. If DomainUser or no type is specified, <ServiceAccountLogin> and <ServiceAccountPassword> are required. When you run Setup by using the /Q or /QR parameter, if this element is not specified the Network Service account will be used. Caution Maintaining the configuration file that has <ServiceAccountLogin> and <ServiceAccountPassword> values specified is a security risk because you are storing a password in plain text. Delete these elements as soon as the configuration file is used to install Microsoft Dynamics CRM Server 2011.If you do not specify this element, Setup will use the account specified in the <CrmServiceAccount> element to run this service. Therefore, we recommend that you specify a different low-privilege user account for each of the Microsoft Dynamics CRM service accounts.In addition to the permissions required by the other Microsoft Dynamics CRM service accounts, the Deployment Web Service account requires system administrator permission on the SQL Server, and must be a member of the local administrator group where SQL Server is running to be able to create or import organizations. Important To perform organization operations through the Deployment Web Service or Windows PowerShell, the Deployment Service account must have system administrator permissions on the computer that is running SQL Server and must be a member of the local administrators group where SQL Server is installed. Additionally, the user that is performing the organization operations should be a Deployment Administrator. The Deployment Administrator role in Microsoft Dynamics CRM is set in Deployment 181

Manager.

<AsyncServiceAccount type="DomainUser"/"NetworkService"><ServiceAccountLogin>Domain\User</ServiceAccountL ogin><ServiceAccountPassword>password</ServiceAccountPassword><AsyncServiceAccount>

Specifies the service account to use for the asynchronous processing services. Accepted values are DomainUser, which will use the specified domain user provided in the <prefixServiceAccount> element or NetworkService, which uses the Network Service system account. However, using the Network Service system account is not recommended because it may limit some database operations such as organization create, import, upgrade, or update. By default, Setup will use the DomainUser option. If DomainUser or no type is specified, <ServiceAccountLogin> and <ServiceAccountPassword> are required. Warning Maintaining the configuration file that has <ServiceAccountLogin> and <ServiceAccountPassword> values specified is a security risk because you are storing a password in plain text. Delete these elements as soon as the configuration file is used to install Microsoft Dynamics CRM Server 2011. If you do not specify this element, Setup will use the account specified in the <CrmServiceAccount> element to run this service. Therefore, we recommend that you specify a different low-privilege user account for each of the Microsoft Dynamics CRM service accounts.

<SQM optin=" true / false"/>

Specifies whether you will participate in the Customer Experience Improvement Program. If you specify true, you will participate in the program. Note For more information, see Microsoft Customer Experience Improvement Program.

182

<Reporting URL="http://srsserver1/ReportServer"/>

URL Specifies the URL of the Report Server.

<Groups autogroupmanagementoff="true/false"><PrivUserGroup>CN=value,OU=value,DC=value,DC=val ue,DC=value</PrivUserGroup><SQLAccessGroup>CN=value,OU=value,DC=value,DC=value,DC=v alue</SQLAccessGroup><ReportingGroup>CN=value,OU=value,DC=value,DC=value,DC=value</ ReportingGroup> <PrivReportingGroup>CN=value,OU=value,DC=value,DC=value,DC=value</PrivReportingGroup> </Groups>

When specified, Setup will use the existing groups in Active Directory instead of creating them during installation. If <automanagegroupsoff> is true, Setup will not add or remove any members to those groups. If you specify <automanagegroupsoff> as true, you must manually create and add the appropriate membership to these groups for users to be able to run the application, and you must continue to do so as new members are added or removed from Microsoft Dynamics CRM. Important You cannot use the <Groups> element with the <OU> element. Setup will not continue if you specify both elements together. Direct user account membership to the Microsoft Dynamics CRM privusergroup security group is required and group membership nesting under privusergroup currently is not supported. For example, if you add a security group named mycrmprivgroupusers to privusergroup, members of mycrmprivgroupusers will not resolve as privusergroup members. This includes the CRMAppPool or the SQL Server Reporting Services service identities, which if granted membership to privusergroup through another security group, can cause system-wide failures in the Microsoft Dynamics CRM web application and reporting features. This setting is only available when you use a configuration file.

<Reboot>"true" / "false"</Reboot>

If this option is not specified, the default is false. This means that the server will not automatically restart at the end of Setup. Also, this option applies only to a final install restart, and not previous restarts that may be required for 183

other components. Note The installation of Microsoft .NET Framework may require you to restart your computer before you can continue to run Microsoft Dynamics CRM Setup.

<Email><IncomingExchangeServer name="ServerName"/>

This optional element specifies the Microsoft Exchange Server computer or POP3 that will be used by the E-mail Router to route incoming e-mail messages. If not specified and later the E-mail Router is used in the deployment, the computer must be added to the PrivUserGroup security group.

</Email>

Specifies the e-mail server that will be used for e-mail routing.

<configdb>

This is the parent for the following encryption key elements: Warning By default, encryption keys are not stored in the configuration database in an encrypted format. We strongly recommend that you specify encryption when you run Setup by using the following entries.

<encryptionkeys certificate="CrmEncryptionCertificate" generate="true"/"False" password="SCpassword" keysource="uniqueID">

The <encryptionkeys> element specifies how, and whether, to encrypt the keys that are stored in the Microsoft Dynamics CRM system. Use generate="true" to enable the system-generated keys that are encrypted. The keysource may be any value, but must be different from other keysource values. SCpassword is the password that will be used to create the symmetric certificate. This setting is only available when you use a configuration file. Warning 184

Maintaining a configuration file that has password and keysource values specified is a security risk because you are storing a password and key information in plain text. We recommend that you save the password in a secure location from where it can be retrieved later for recovery. For more information about best practices for password storage, see the MSDN article Passwords Best practices. Then, delete these elements as soon as the configuration file is used to install Microsoft Dynamics CRM.

<encryptionkey physicalname="CrmSymmetricKey" virtualname="CrmKeyEncryptionKey"/>

Each <encryptionkeys> element specifies a mapping between a symmetric key store in the Microsoft SQL Server database to a virtual key name, hardcoded in Microsoft Dynamics CRM for encrypting data in the configuration database. This setting is only available when you use a configuration file.

</encryptionkeys></configdb>

<LaunchReportingExtensionsSetup>"false" / "true"</LaunchReportingExtensionsSetup>

Optional element that specifies whether to start Microsoft Dynamics CRM Reporting Extensions Setup immediately after Microsoft Dynamics CRM Server Setup completes. By default, the value for this element is false and Microsoft Dynamics CRM Reporting Extensions Setup will not start after Microsoft Dynamics CRM Server Setup completes. Additionally, Microsoft Dynamics CRM Reporting Extensions Setup will only start when the following conditions are true: Microsoft Dynamics CRM Server Setup will be creating or upgrading the first organization in the deployment The specified Report Server computer is the local computer where Setup is running

See Also
Use the Command Prompt to Install Microsoft Dynamics CRM 2011 Sample server XML configuration file

185

Sample server XML configuration file

The following configuration file installs an update file that is located on an internal share, installs a Full Server with all Microsoft Dynamics CRM Server 2011 components, and creates new databases on the default instance of a SQL Server that is named SQLServer:
<CRMSetup> <Server> <Patch update="true">\\server\share\patchfile.msp</Patch> <LicenseKey>XXXXX-XXXXX-XXXXX-XXXXX-XXXXX</LicenseKey> <SqlServer>SQLServer</SqlServer> <Database create="true"/> <Reporting URL="http://MyReportingServer/ReportServer"/> <OrganizationCollation>Latin1_General_CI_AI</OrganizationCollation> <basecurrency isocurrencycode="USD" currencyname="US Dollar" currencysymbol="$" currencyprecision="2"/> <Organization>Organization Display Name</Organization> <OrganizationUniqueName>Organization_Name</OrganizationUniqueName> <OU>OU=value,DC=subdomain,DC=subdomain,DC=subdomain,DC=com</OU> <WebsiteUrl create="true" port="5555"> </WebsiteUrl> <InstallDir>c:\Program Files\Microsoft Dynamics CRM</InstallDir>

<CrmServiceAccount type="DomainUser"> <ServiceAccountLogin>Contoso\CRMAppService</ServiceAccountLogin> <ServiceAccountPassword>password</ServiceAccountPassword> </CrmServiceAccount>

<SandboxServiceAccount type="DomainUser"> <ServiceAccountLogin>Contoso\CRMSandboxService</ServiceAccountLogin> <ServiceAccountPassword>password</ServiceAccountPassword> </SandboxServiceAccount>

<DeploymentServiceAccount type="DomainUser"> <ServiceAccountLogin>Contoso\CRMDeploymentService</ServiceAccountLogin>

186

<ServiceAccountPassword>password</ServiceAccountPassword> </DeploymentServiceAccount>

<AsyncServiceAccount type="DomainUser"> <ServiceAccountLogin>Contoso\CRMAsyncService</ServiceAccountLogin> <ServiceAccountPassword>password</ServiceAccountPassword> </AsyncServiceAccount>

<SQM optin="true"/> <muoptin optin="true"/> <Email> <IncomingExchangeServer name="ExchangeServerName"/> </Email> </Server> </CRMSetup>

Caution Maintaining the configuration file that has <ServiceAccountLogin> and <ServiceAccountPassword> values specified is a security risk because you are storing a password in plain text. Delete these elements as soon as the configuration file is used to install Microsoft Dynamics CRM Server 2011.

See Also
Microsoft Dynamics CRM 2011 Server XML configuration file Sample server XML configuration file for installing with pre-created groups

Sample server XML configuration file for installing with pre-created groups
To use the pre-created Active Directory directory service security groups, create an XML configuration file that uses the syntax that is similar to the following example. Modify the variables as appropriate. The list that follows the sample code describes how to modify the variables that are in this example. 187

In the following XML sample, the domain name is domain.domain_extension and the organizational units are Company Name. Replace these names with the actual names that are in your Active Directory deployment. The Active Directory hierarchy is as follows: root domain Company Name OU Company Name OU
<CRMSetup> <Server> <Groups AutoGroupManagementOff="false"> <PrivUserGroup>CN=PrivUserGroup,OU=Company Name,OU=Company Name,DC=<domain>,DC=<domain_extension></PrivUserGroup> <SQLAccessGroup>CN=SQLAccessGroup,OU=Company Name,OU=Company Name, DC=<domain>,DC=<domain_extension></SQLAccessGroup> <ReportingGroup>CN=ReportingGroup,OU=Company Name,OU=Company Name, DC=<domain>,DC=<domain_extension></ReportingGroup> <PrivReportingGroup>CN=PrivReportingGroup,OU=Company Name,OU=Company Name, DC=<domain>,DC=<domain_extension></PrivReportingGroup> </Groups> </Server> </CRMSetup>

See Also
Microsoft Dynamics CRM 2011 Server XML configuration file Install Microsoft Dynamics CRM Server 2011 roles

Install Microsoft Dynamics CRM Server 2011 roles

By default, Setup installs all Microsoft Dynamics CRM Server 2011 roles on the local computer. However, if you are installing Microsoft Dynamics CRM Server, you can install one or more server roles on a different computer, or have two or more computers running the same role, which can provide load balancing benefits. To do this, you can either select the roles that you want by running the Microsoft Dynamics CRM Server Setup Wizard or you can configure an XML 188

configuration file and then run Setup at a command prompt on the computer where you want the role installed. Note You can run Setup at a command prompt or from Programs and Features in Control Panel to add or remove server roles to a computer that already has one or more server roles installed. For more information about server roles, see Planning Deployment in the Planning Guide. For more information about recommendations for isolating server roles or running multiple computers with the same server role, see the Planning Deployment Advanced Topics in the Planning Guide.

Parameters
The supported command prompt parameters are the same as what was previously described under Install Microsoft Dynamics CRM Server 2011 in this guide.

Server role XML configuration file

The /config [drive:] [[path] configfilename.xml]] command-line parameter provides Microsoft Dynamics CRM Server Setup with required information. The information supplied by the XML configuration file is what is required by each installation screen. Important The XML elements must be in English (US). An XML configuration file that has localized XML elements will not work correctly. An explanation of each XML element and a sample XML file follows:
<Roles><Role name="RoleName1" Action="Add" / "Remove"/><Role name="RoleName2" Action="Add" / "Remove"/>

Action. This attribute is only required when you reconfigure an existing deployment by adding or removing server roles. Role name. Available values are as follows:

AsynchronousProcessingService

Installs the Asynchronous Service. This service is used to process queued asynchronous events, such as bulk e-mail or data import. 189

WebApplicationServer

Installs the components that are needed to run the Web application server.

OrganizationWebService

Installs the Organization Web Service components that are needed to run applications that use the methods described in the Microsoft Dynamics CRM SDK.

DeploymentWebService

Installs the Deployment Web Service component that is required to manage the deployment by using the methods described in the Microsoft Dynamics CRM SDK, such as create an organization or remove a Deployment Administrator role from a user.

DiscoveryWebService

Installs the Discovery Web Service component users need to find the organization that they are a member of in a multi-tenant deployment.

HelpServer

Installs the components that are needed to make Microsoft Dynamics CRM Help available to users.

SandboxProcessingService

Installs the components that are needed to provide custom code execution isolation.

DeploymentTools

Installs Deployment Manager and Windows PowerShell cmdlets that you can use to automate deployment tasks. Deployment Manager is a Microsoft 190

Management Console (MMC) snap-in that system administrators can use to manage organizations, servers, and licenses for deployments of Microsoft Dynamics CRM.

</Roles>

See Also
Microsoft Dynamics CRM 2011 Server XML configuration file Sample XML configuration file that installs only the WebApplicationServer role

Sample XML configuration file that installs only the WebApplicationServer role
The following example installs only the WebApplicationServer role on the local computer. The configuration database already exists.
<CRMSetup> <Server> <Patch update="true">\\server\share\patchfile.msp</Patch> <LicenseKey>XXXXX-XXXXX-XXXXX-XXXXX-XXXXX</LicenseKey> <SqlServer>SQLServer</SqlServer> <database create="false" /> <WebsiteUrl create="true" /> <InstallDir>c:\Program Files\Microsoft CRM</InstallDir> <Roles> <Role name="WebApplicationServer"/> </Roles> <SQM optin="true" /> <muoptin optin="true" />

<CrmServiceAccount type="DomainUser">

191

<ServiceAccountLogin>contoso\user1</ServiceAccountLogin> <ServiceAccountPassword>password</ServiceAccountPassword> </CrmServiceAccount>

</Server> </CRMSetup>

Caution Maintaining the configuration file that has <ServiceAccountLogin> and <ServiceAccountPassword> values specified is a security risk because you are storing a password in plain text. Delete these elements as soon as the configuration file is used to install Microsoft Dynamics CRM Server 2011.

See Also
Install Microsoft Dynamics CRM Server 2011 roles Install Microsoft Dynamics CRM Reporting Extensions (2)

Sample XML configuration file that installs only the HelpServer role
The following example installs only the Help Server role on the local computer.

<CRMSetup> <Server> <Patch update="true"/> <licenseKey>XXXXX-XXXXX-XXXXX-XXXXX-XXXXX</licenseKey> <SqlServer>SQLServerName</SqlServer> <database create="false"/> <WebsiteUrl create="true" port="5555">LM/W3SVC/1</WebsiteUrl> <Help anonymous="true">http://LocalHost/Help </Help> <InstallDir>c:\Program Files\Microsoft CRM</InstallDir> <Roles> <Role name="HelpServer"/>

192

</Roles> <SQM optin="true"/> <muoptin optin="true"/> <CrmServiceAccount type="DomainUser"> <ServiceAccountLogin>contoso\CRMHelpservice</ServiceAccountLogin> <ServiceAccountPassword>password</ServiceAccountPassword> </CrmServiceAccount> </Server> </CRMSetup>

Important Unless you use <Help anonymous="true">, the Help Server contents in IIS will not be configured for anonymous access. If the Help Server application is not configured for anonymous access, users may be prompted repeatedly for authentication credentials when they access Microsoft Dynamics CRM Help. By default, the Help Server uses the Web Application Server web address that appears in Deployment Manager. Additionally, Microsoft Dynamics CRM Server Setup does not update the URL when you install the Help Server on a separate computer. You must change the URL manually. To change the URL, run the following Windows PowerShell commands in the following topic on the computer that is running the Deployment Tools server role.

Change the Microsoft Dynamics CRM HelpServer URL

The following Windows PowerShell cmdlets change the Microsoft Dynamics CRM Help Server URL to https://crmhelpserver.contoso.com, an Internet-facing Help Server configured for SSL. Before you can run the Microsoft Dynamics CRM 2011 Help Server cmdlets, you must register them first. For more information, see Operating Microsoft Dynamics CRM. View existing web address settings. Notice that, if the Helpserverurl web address setting appears blank when you run the following Windows PowerShell command, the Help Server is using the same web address as the Web Application Server (WebAppRootDomain).
Get-Crmsetting webaddresssettings

Set the Help Server url.

$websetting = Get-CrmSetting WebAddressSettings $websetting.HelpServerUrl = https://crmhelpserver.contoso.com Set-CrmSetting $websetting

193

Verify the new URL by viewing the web address settings again.
Get-Crmsetting webaddresssettings

See Also
Sample XML configuration file that installs only the WebApplicationServer role Install Microsoft Dynamics CRM Reporting Extensions (2)

Install Microsoft Dynamics CRM Reporting Extensions (2)

Microsoft Dynamics CRM Reporting Extensions are data processing extensions that are installed on the Microsoft SQL Server Reporting Services server. Microsoft Dynamics CRM Reporting Extensions accept the authentication information from Microsoft Dynamics CRM Server 2011 and passes it to the Microsoft SQL Server Reporting Services server. Installing Microsoft Dynamics CRM Reporting Extensions installs two data processing extensions: Microsoft Dynamics CRM Fetch data processing extension and SQL data processing extension. The Fetch data processing extension is required to create, run, and schedule Fetch-based reports in Microsoft Dynamics CRM 2011. The SQL data processing extension is required to schedule SQL-based reports in Microsoft Dynamics CRM 2011.

Microsoft Dynamics CRM Reporting Extensions requirements

Microsoft Dynamics CRM Reporting Extensions has the following requirements: You must complete Microsoft Dynamics CRM Server Setup before you run Microsoft Dynamics CRM Reporting Extensions Setup. You must run Microsoft Dynamics CRM Reporting Extensions on a computer that has Microsoft SQL Server 2008 Reporting Services or Microsoft SQL Server 2008 R2 Reporting Services installed. You must run the Microsoft Dynamics CRM Reporting Extensions Setup on a computer that has Microsoft SQL Server 2008 Reporting Services installed. For smaller data sets and fewer users, you can use a single-server deployment or a multiple-server deployment. With larger datasets or more users, performance will decrease quickly when complex reports are run.

194

Use a multi-server deployment with one computer that is running SQL Server for Microsoft Dynamics CRM, and another server for Microsoft SQL Server Reporting Services.

Command example
Microsoft Dynamics CRM Reporting Extensions accepts the same command-line parameters as Microsoft Dynamics CRM Server 2011. To install Microsoft Dynamics CRM Reporting Extensions in quiet mode, which uses an XML configuration file named install-config.xml, and creates a log file named log.txt, run the Setup program that is located in the SrsDataConnector folder command from the installation media or the Microsoft Dynamics CRM Server 2011 installation files as follows: SetupSrsDataConnector /Q /CONFIG folderpath\install-config.xml /L c:\logfiles\crm\log.txt

See Also
Use the Command Prompt to Install Microsoft Dynamics CRM 2011 Microsoft Dynamics CRM Reporting Extensions XML configuration file

Microsoft Dynamics CRM Reporting Extensions XML configuration file

Before you run Microsoft Dynamics CRM Reporting Extensions Setup at a command prompt, you must modify the XML configuration file to include information, such as the name of the computer where the configuration database is located. A sample Microsoft Dynamics CRM Reporting Extensions configuration file named install-config.xml is located in the SrsDataConnector folder on the installation media or download location of the Microsoft Dynamics CRM Server 2011 installation files. The /config [drive:] [[path] configfilename.xml]] command-line parameter provides the Microsoft Dynamics CRM Reporting Extensions Setup with required information. The information this configuration file supplies is the same that each installation screen requires. The XML elements must be in English (US); special or extended characters cannot be used. An XML configuration file that has localized XML elements will not work correctly. An explanation of each XML element and a sample XML file follows:
<CRMSetup> </CRMSetup>

The configuration file must be a valid XML file that uses <CRMSetup> as the

195

root element.

<srsdataconnector>

The configuration file must be a valid XML file that uses <srsdataconnectorinstall> as the primary element. All the Microsoft Dynamics CRM Reporting Extensions entries that follow must be within the <srsdataconnectorinstall> tags.

<InstallType>Uninstall/Repair</InstallType>

Specifies the type of installation that Setup will perform. The following options are available: Uninstall. Uninstalls Microsoft Dynamics CRM Reporting Extensions. Repair. Starts Setup in repair mode.

<Patch update="true"/"false">\\ServerName\ShareName\Patch_Location</Patch>

If you do not specify a location, by default Setup will go online to a location that is managed by Microsoft to search for available updates. Or, you can point Setup to install a Microsoft Dynamics CRM Reporting Extensions Setup update .msp file from a different location, such as an internal share. update Specifies whether Setup will look for, download, and apply updates for Microsoft Dynamics CRM Server Setup. We recommend that you let Setup download the latest version by selecting true. By default, this value is set to false. If the value is set to false, Setup will ignore this step and continue with the installation.

<configdbserver>SQLServerName\Instancename</configdbserver>

Specifies the instance of SQL Server that stores the configuration database. If you specify the default instance, use SQLServerName, or if you use a named instance use SQLServerName\InstanceName. 196

<InstallDir>c:\program files\Microsoft CRM</InstallDir>

Specifies the folder in which the Microsoft Dynamics CRM Reporting Extensions files will be copied.

<autogroupmanagementoff>1/0</autogroupmanagementoff>

If <automanagegroupsoff> is 1 (true), Setup will not add or remove any members to the security group in Active Directory directory service. Therefore, you must manually add the Microsoft SQL Server Reporting Services service account for the associated instance of SQL Server to the PrivReportingGroup security group.

See Also
Install Microsoft Dynamics CRM Reporting Extensions (2) Sample Microsoft Dynamics CRM Reporting Extensions XML configuration file

Sample Microsoft Dynamics CRM Reporting Extensions XML configuration file

The following XML configuration sample will install the Microsoft Dynamics CRM Reporting Extensions. This has all databases on the local computer named SQLServer:
<crmsetup> <srsdataconnector> <configdbserver /> <autoupdateconfigdb>1</autoupdateconfigdb> <autogroupmanagementoff>0</autogroupmanagementoff> <instancename>MSSQLSERVER</instancename> <patch update="false" /> </srsdataconnector> </crmsetup>

197

Logging
By default, Setup creates a file that is named SrsDataConnectorSetup.log in the <drive:>%appdata%\Microsoft\MSCRM\Logs folder on the computer where Setup is run.

See Also
Microsoft Dynamics CRM Reporting Extensions XML configuration file Command example Microsoft Dynamics CRM Report Authoring Extension

Command example Microsoft Dynamics CRM Report Authoring Extension

The following command will install Microsoft Dynamics CRM Reporting Extensions: SetupBIDSExtensions.exe [/Q] [/config configfile.xml]
/Q

Quiet mode installation. This parameter requires a configuration file in XML format. The /config parameter contains the name of the XML configuration file. No dialog boxes or error messages will appear on the display screen.

/config [drive:] [[path] configfilename.xml]]

The /config parameter uses the specified XML configuration file to provide Setup with the additional information to complete installation successfully. An example XML configuration file is discussed in the following section. Notice that when you specify a configuration file without the /Q parameter, Setup screens appear filled with the information from the configuration file.

/uninstall

Uninstalls Microsoft Dynamics CRM Reporting Extensions. This is a maintenance mode option that is only available when the application is 198

already installed.

See Also
Sample Microsoft Dynamics CRM Report Authoring Extension XML configuration file Microsoft Dynamics CRM Report Authoring Extension XML configuration file

Microsoft Dynamics CRM Report Authoring Extension XML configuration file

The following is an explanation of each XML element and a sample XML file for installing Microsoft Dynamics CRM Report Authoring Extension:
<CRMSetup> </CRMSetup>

The configuration file must be a valid XML file that uses <CRMSetup> as the root element.

<patchUpdateValue>True/False</patchUpdateValue>

Determines the behavior of the update Setup technology. This feature lets Setup perform a one-time search for, and if applicable, download to apply the latest installation files for Microsoft Dynamics CRM.

<muoptin optin="true/false" />

Specifies whether to use Microsoft Update to download and install updates to Microsoft Dynamics CRM Server 2011 and other installed applications. After the installation is completed, this feature helps keep your computer up-todate on an ongoing basis. True. When you specify this option, Setup will opt in to Microsoft Update as the update service and use the Windows automatic updating settings on the computer. Windows automatic update settings can be viewed in Windows Update in Control Panel. Microsoft Update helps make sure that your computer has the latest technology, which can help reduce the risk 199

of vulnerabilities and security issues. False. When you specify this option, Setup will not change the existing Windows automatic update settings. If the computer is not already configured to use Microsoft Update as the update service, we recommend that you have another method to install updates on the computer, such as by using Microsoft Windows Update Services (WSUS). If left blank, a value of false will be selected.

<InstallType>uninstall</InstallType>

Uninstalls Microsoft Dynamics CRM Report Authoring Extension. This is a maintenance mode option that is only available when the application is already installed.

<InstallDir>c:\program files\Microsoft Dynamics CRM</InstallDir>

Specifies the folder in which application files will be installed. By default, Setup uses the folder C:\Program Files\Microsoft Dynamics CRM.

See Also
Install Microsoft Dynamics CRM Reporting Extensions (2) Sample Microsoft Dynamics CRM Reporting Extensions XML configuration file

Sample Microsoft Dynamics CRM Report Authoring Extension XML configuration file
The following XML configuration contents will install Microsoft Dynamics CRM Report Authoring Extension that will opt-in to use Microsoft Update, search and apply existing updates, and install Microsoft Dynamics CRM Report Authoring Extension in the C:\Program Files (x86)\Microsoft Dynamics CRM Report Authoring Extension folder.
<crmsetup> <bidsextensions> <patch update="True" />

200

<muoptin optin="True" /> <installdir>C:\Program Files (x86)\Microsoft Dynamics CRM Report Authoring Extension</installdir> </bidsextensions> </crmsetup>

See Also
Microsoft Dynamics CRM Report Authoring Extension XML configuration file Install Microsoft Dynamics CRM for Outlook using a Command Prompt

Install Microsoft Dynamics CRM for Outlook using a Command Prompt

This section applies only to on-premises versions of Microsoft Dynamics CRM 2011. Installing Microsoft Dynamics CRM for Outlook is a two-step procedure. First, you must run Setup to install the files on the computer. Next, you run the Microsoft Dynamics CRM Configuration Wizard to configure the application and complete the installation. Important If there is a conflict between a value in the configuration file and a value in the command-line parameters, the command-line parameter takes precedence.

In This Topic
Step 1: Install files Step 2: Configure Microsoft Dynamics CRM for Outlook by using an XML configuration file Command examples for Microsoft Dynamics CRM for Outlook configuration Microsoft Dynamics CRM for Outlook XML configuration file elements User credentials are required when you run the Configuration Wizard Sample Microsoft Dynamics CRM for Outlook XML configuration file for configuration

201

Step 1: Install files

The following command displays the available options to run Microsoft Dynamics CRM for Outlook Setup at the command prompt: Setupclient.exe [/A] [/Q] [/X] [/L or /LV "[drive:][[path] logfilename.log]"] [/targetdir "[drive:][path]"] [/installofflinecapability] [/disableofflinecapability] [/ignoreofflinequeue]

Command examples for Microsoft Dynamics CRM for Outlook installation

For users who travel or who are not always connected to the Microsoft Dynamics CRM Server 2011, Microsoft Dynamics CRM for Microsoft Office Outlook with Offline Access provides access to their customer data. To install Microsoft Dynamics CRM for Microsoft Office Outlook with Offline Access in quiet mode:
Setupclient /Q /l c:\clientinstalllog.txt /installofflinecapability /targetdir "c:\Program Files\Microsoft Dynamics CRM Client"

To uninstall Microsoft Dynamics CRM for Microsoft Office Outlook with Offline Access in quiet mode:
SetupClient /x /q

Parameters for Microsoft Dynamics CRM for Outlook installation

None

Used without parameters, Setupclient.exe will run with all display screens.

installofflinecapability

Determines whether offline capability will be installed. When you include this parameter, offline capability and components will be installed. If you do not specify this parameter, the online-only client will be installed.

/targetdir <"drive:\path">

Specifies the folder in which Microsoft Dynamics CRM for Outlook files will be installed.

202

/A

Creates an administrative installation of Microsoft Dynamics CRM for Outlook by creating a Windows Installer package. This package lets users run Setup from a network share or lets nonadministrative users run Setup that is driven from a group policy. This parameter must be used with the /targetdir parameter described earlier. When using this parameter, the /targetdir value does not have to be located on the local computer. A mapped drive or network share, such as \\share\mscrm_client_admin, can be used. Important If you do not specify a target folder by using the /targetdir parameter, Setup installs the administrative installation to the default folder <drive:>Program Files\Microsoft Dynamics CRM. For example, the command:
Setupclient /Q /A /targetdir "\\share\mscrm_client_admin"

/Q

Quiet mode installation. This parameter requires a configuration file in XML format. The /i parameter contains the name of the XML configuration file. No dialog boxes or error messages will appear on the display screen. To capture error message information, include the log file parameter (/L or /LV).

/L [drive:][[path] logfilename.log]

Creates a log file of installation activity. You must specify the file name of the log file and where to put it, but the path cannot be a relative path, such as %appdata%\CRMLogs.

/LV [drive:][[path] logfilename.log]

Creates a verbose log file of installation activity. You must specify the file name of the log file and where to put it, but the path cannot be a relative path, such as %appdata%\CRMLogs.

203

disableofflinecapability

When you specify this parameter, Microsoft Dynamics CRM for Outlook is configured to hide the go offline button in the application. This button lets users easily switch to Microsoft Dynamics CRM for Outlook with offline capability.

ignoreofflinequeue

When you specify this parameter, Setup will not attempt to synchronize items that may remain in the offline queue during upgrade.

/X

Uninstalls Microsoft Dynamics CRM for Outlook. This is a maintenance mode option that is only available when the application is already installed.

Sample Microsoft Dynamics CRM for Outlook XML configuration file for installation
The following configuration-file example installs Microsoft Dynamics CRM for Outlook without offline access capability into the Program Files folder. Note You can use the same file that includes both the installation and configuration elements. Setup and the Configuration Wizard will ignore the elements that are not relevant to the operation.
<Deployments> <TargetDir>c:\program files\Microsoft Dynamics CRM\Client</TargetDir> <InstallOfflineCapability>false</InstallOfflineCapability> </Deployments>

204

Step 2: Configure Microsoft Dynamics CRM for Outlook by using an XML configuration file
After you install Microsoft Dynamics CRM for Outlook, you must configure it. You can do this by running the client Configuration Wizard at the command prompt. The client Configuration Wizard file is named Microsoft.Crm.Application.Outlook.ConfigWizard.exe and is located in the Client\ConfigWizard folder where Microsoft Dynamics CRM for Outlook is installed. By default, the folder is C:\Program Files\Microsoft Dynamics CRM. Note The credentials of the user who will run Microsoft Dynamics CRM for Outlook are used to authenticate to Microsoft Dynamics CRM. Therefore, to perform a silent configuration of Microsoft Dynamics CRM for Outlook, you must run the Configuration Wizard under the user's context, such as by running a user-invoked batch file or as a one-time entry in a login script. For more information, see User credentials are required when you run the Configuration Wizard. For information about how to configure Microsoft Dynamics CRM for Outlook by using System Center Configuration Manager, see Install
Microsoft Dynamics CRM for Outlook by using Microsoft System Center Configuration Manager 2007 in this guide. To deploy Microsoft Dynamics CRM for Outlook by using Microsoft

Group Policy, see Deploy Microsoft Dynamics CRM for Outlook by using Group Policy in the Planning Guide. If a path to the configuration file is not specified, the Configuration Wizard looks for the default configuration file (default_client_config.xml) in the non-roaming profile folder (%localappdata%\Microsoft\MSCRM\). If the file is not located in the non-roaming profile folder, the Configuration Wizard looks for the folder where Microsoft Dynamics CRM for Outlook is installed. By default, Microsoft Dynamics CRM for Outlook is installed in the C:\Program Files\Microsoft Dynamics CRM folder. If the configuration file is located in the roaming location used by other applications (AppData\Roaming\Microsoft\MSCRM\), it will not be honored.

Command examples for Microsoft Dynamics CRM for Outlook configuration

The following command configures Microsoft Dynamics CRM for Outlook with Offline Access by using a file named config_client.xml in quiet mode, and outputs a log file named clientinstall.log:

205

Microsoft.Crm.Application.Outlook.ConfigWizard.exe /Q /i c:\config_client.xml /xa /l c:\clientinstall.log

The /Q quiet mode configuration parameter requires a configuration file in XML format. No dialog boxes or error messages will appear on the display screen. To capture error message information, include the log file parameter (/L) or verbose logging (/LV). Important Valid user credentials stored in the Windows Vault are required to run the Configuration Wizard in quiet mode. For information, see User credentials are required when you run the Configuration Wizard. The /i [drive:] [[path] configfilename.xml]] command-line parameter provides Microsoft Dynamics CRM for Outlook Setup with required information. It is the same information that each installation screen requires. The XML elements must be in English (US); special or extended characters cannot be used. An XML configuration file that has localized XML elements will not work correctly. An explanation of each XML element and a sample XML file follows: The /xa parameter when used with the /q parameter removes all organizations that are configured for Microsoft Dynamics CRM for Outlook. The /R parameter may be used to suppress the Configuration Wizard user interface and only display the progress dialog box. This parameter requires a valid XML Setup file that is named Default_Client_Config.xml and must be located in either the local user AppData or Client installation folder.

Microsoft Dynamics CRM for Outlook XML configuration file elements

<Deployments> </Deployments>

The configuration file must be a valid XML file that uses <Deployment> as the root element.

<InstallOfflineCapability>true/false</InstallOfflineCapability>

Specifies the type of Microsoft Dynamics CRM for Outlook installation. Specifying true, will install Microsoft Dynamics CRM for Outlook with Offline Access capability.

206

<TargetDir>drive:\path</TargetDirectory>

Specifies the folder in which Microsoft Dynamics CRM for Outlook files will be installed.

<Deployment> </Deployment>

Parent element for all of the following elements.

<DiscoveryUrl>https://website:portnumber</DiscoveryUrl>

Specifies the URL for the Microsoft Dynamics CRM Discovery Web Service. For an on-premises deployment of Microsoft Dynamics CRM 2011, the supported binding can be HTTPS or HTTP. If the Discovery Web Service is using a port other than the default ports 80 (HTTP) or 443 (HTTPS), you must specify the port number. If this is a Full Server deployment of Microsoft Dynamics CRM Server 2011, the Discovery Web Service URL is the same as the URL for the web application, such as http://crmserver . For Microsoft Dynamics CRM Online, use the full organization URL, such as https://orgname.crm.dynamics.com, or depending on your online environment and location, use the discovery service URL, in the form https://disco.crm.dynamics.com. For a list of URLs, see Discovery Service.

<Organizations> </Organizations>

This is the parent element for the following <Organization> element.

<Organization FriendlyName="My Friendly Organization Name" IsPrimary="true"/"false">OrganizationName</Organization>

Specifies the name of the organization that the client will connect to. FriendlyName. Specifies a different display name other than the organization name in Outlook. IsPrimary. Specifies the organization that will be configured as the synchronizing organization in Microsoft Dynamics CRM for Outlook.

207

Note OrganizationName is case-sensitive.

User credentials are required when you run the Configuration Wizard
The Configuration Wizard requires user credentials. During a silent configuration, by using /Q with Microsoft.Crm.Application.Outlook.ConfigWizard.exe, the Configuration Wizard will look for the users credentials in the Windows Vault. If the Configuration Wizard cannot find the credentials, or the credentials are not in the required format, the configuration will not finish and an error will be recorded to the configuration log file. Notice that the Configuration Wizard does not support adding the user UPN or password in the XML configuration file. For information about how to add user credentials from a command script to the Windows Vault, see Silent configuration of CRM for Outlook client in CRM 2011 claims enabled environment . For more information about the Windows Vault and Credential Manager, see What is Credential Manager?

Sample Microsoft Dynamics CRM for Outlook XML configuration file for configuration
The following configuration file example configures Microsoft Dynamics CRM for Outlook to connect to a primary organization named Contoso and another organization named AdventureWorksCycle on the Microsoft Dynamics CRM Server 2011 that is named crmserver. Note You can use the same file that includes both the installation and configuration elements. Setup and the Configuration Wizard will ignore the elements that are not relevant to the operation.
<Deployments> <Deployment> <DiscoveryUrl>http://crmserver</DiscoveryUrl> <Organizations> <Organization IsPrimary='true'>Constoso</Organization> <Organization>AdventureWorksCycle</Organization> </Organizations>

208

</Deployment> </Deployments>

Note The example above specifies two different organizations that the user has access. The value in the Organization elements cannot contain special characters or spaces. You can find the organization name in the Name column in the Organizations area of Deployment Manager.

To configure Microsoft Dynamics CRM for Outlook using a script 1. Write a script that automatically updates the configuration settings for users of Microsoft Dynamics CRM for Outlook. You could use lines such as the following to perform the basic configuration actions, based on a new configuration file that is stored on the computer indicated as <servername>. In the following script, the default client configuration file is overwritten, previously configured organizations are removed, user credentials are added to the Windows Vault, and the new organization is installed:
copy /y \\<servername>\share\Default_Client_Config.xml "c:\Program Files\Microsoft Dynamics CRM\Default_Client_Config.xml" "C:\Program Files\Microsoft Dynamics CRM\Client\ConfigWizard\Microsoft.Crm.Application.Outlook.Con figWizard.exe" /q /xa cmdkey /generic:Microsoft_CRM_https://contoso.crm.dynamics.com/ /user:user@contoso.com /password "C:\Program Files\Microsoft Dynamics CRM\Client\ConfigWizard\Microsoft.Crm.Application.Outlook.Con figWizard.exe" /q /i "C:\Program Files\Microsoft Dynamics CRM\Default_Client_Config.xml"

Tip Consider running your script as a logon script, or forcing the script to run at a specific time, such as by using Microsoft System Center Configuration Manager 2007. In the script, you might also want to include detection logic that determines 209

whether the client computer has already been configured. If it has, you can have the script exit without taking action. Example Default_Client_Config.xml file
<Deployment> <DiscoveryUrl>http://CrmDiscoveryUrl</DiscoveryUrl> <Organizations> <Organization IsPrimary='true'>Organization1</Organization> </Organizations> </Deployment>

2. Run the script on each client computer in the organization whose server has changed. You can run the script in various ways, including through the Profile tab of the user properties dialog box in Active Directory Users and Computers (ADUC), or through Group Policy Objects (GPO).

See Also
Install Microsoft Dynamics CRM Reporting Extensions (2) Install Microsoft Dynamics CRM E-mail Router

Install Microsoft Dynamics CRM E-mail Router

The E-mail Router accepts the same command prompt parameters as Microsoft Dynamics CRM Server 2011. To install the E-mail Router in quiet mode, run the SetupEmailRouter.exe command in the EmailRouter folder on the installation media, or download location of the Microsoft Dynamics CRM Server 2011 installation files as follows: SetupEmailRouter /Q /CONFIG folderpath\install-config.xml /L c:\temp\log.txt This installation uses an XML configuration file named install-config.xml and creates a log file named log.txt.

210

E-mail Router XML configuration file

The /config [drive:] [[path] configfilename.xml]] command-line parameter provides Microsoft Dynamics CRM E-mail Router Setup with required information. It is the same information that each installation screen requires. Important To use the E-mail Router after it is installed, you must run the E-mail Router Configuration Manager to configure it. You cannot configure the E-mail Router by using an XML configuration file. The XML elements must be in English (US). An XML configuration file that has localized XML elements will not work correctly. An explanation of each XML element and a sample XML file follows:
<CRMSetup> </CRMSetup>

The configuration file must be a valid XML file that uses <CRMSetup> as the root element.

<EmailRouter> </ EmailRouter>

Specifies a Microsoft Dynamics CRM E-mail Router installation. The <EmailRouter> tag must be within the <CRMSetup> open and end tags. All the E-mail Router entries that follow must be within the <EmailRouter> tags.

<InstallType>Uninstall/Repair</InstallType>

Specifies the type of installation that Setup will perform. The following options are available: Uninstall Uninstalls Microsoft Dynamics CRM E-mail Router. Repair Starts Setup in repair mode.

211

<Patch update="true"/"false">\\ServerName\ShareName\Patch_Location</Patch>

If you do not specify a location, by default Setup will go online to a location that is managed by Microsoft to search for available updates. Or, you can point Setup to install a Microsoft Dynamics CRM E-mail Router Setup update .msp file from a different location, such as an internal share. update Specifies whether Setup will look for, download, and apply updates for Microsoft Dynamics CRM E-mail Router Setup. We recommend that you let Setup download the latest version by selecting true. By default, this value is set to false. If the value is set to false, Setup will ignore this step and continue with the installation.

<InstallDir>c:\Program Files\Microsoft CRM Email</InstallDir>

Specifies the folder where the E-mail Router will be installed. By default, the E-mail Router is installed to C:\Program Files\Microsoft CRM Email.

<Features></Features>

If a value is not specified, Setup installs the E-mail Router service and the Email Router Configuration Manager, but does not install the Rule Deployment Wizard. The following features are available:
<SinkService />

Add this entry if you want to install the E-mail Router service and E-mail Router Configuration Manager.

<RulesWizard />

Add this entry if you want to install the Rule Deployment Wizard.

212

Sample Microsoft Dynamics CRM E-mail Router XML configuration file

The following configuration-file sample instructs Setup to check a Microsoft Web site for available updates to E-mail Router Setup. It applies the updates, and then installs the E-mail Router service and Rule Deployment Wizard in the C:\Program Files\Microsoft Dynamics CRM Email Router folder:
<CRMSetup> <EmailRouter> <Features> <SinkService /> <RulesWizard /> </Features> <Patch update="true"></Patch> <InstallDir>c:\Program Files\Microsoft Dynamics CRM Email Router</InstallDir> </EmailRouter> </CRMSetup>

See Also
Install Microsoft Dynamics CRM for Outlook using a Command Prompt Microsoft Dynamics CRM Server 2011 installation troubleshooting

Microsoft Dynamics CRM Server 2011 installation troubleshooting

The following section describes known issues and troubleshooting steps when you are installing Microsoft Dynamics CRM at a command prompt.

213

Setup fails or client receives an unhandled exception when trying to connect after you install Microsoft Dynamics CRM Server 2011
Setup may not complete successfully or any of the Microsoft Dynamics CRM 2011 clients may receive an error message when trying to connect to the Microsoft Dynamics CRM Server 2011 that is similar to items in the following list: Exception from HRESULT. 0x80048306. Description. An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details. System.Runtime.InteropServices.COMException: Exception from HRESULT: 0x80048306. Source Error. An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. This problem can occur if you run Microsoft Dynamics CRM Server Setup when the following conditions are true: One or more of the following Active Directory security groups was created in the organizational unit where you are installing Microsoft Dynamics CRM 2011: PrivUserGroup ReportingGroup SQLAccessGroup PrivReportingGroup The previously mentioned security groups do not have the correct group membership. You use the automanagegroupsoff=false attribute and value in the <Groups> entry for the Setup XML configuration file. To use a configuration file, you must install Microsoft Dynamics CRM Server 2011 at the command prompt. To resolve this issue, you must manually add the correct membership to each of the required security groups in Active Directory, and then run Microsoft Dynamics CRM Server Setup again. Important 214

Direct user account membership to the Microsoft Dynamics CRM privusergroup security group is required and group membership nesting under privusergroup currently is not supported. For example, if you add a security group named mycrmprivgroupusers to privusergroup, members of mycrmprivgroupusers will not resolve as privusergroup members. This includes the CRMAppPool or the SQL Server Reporting Services service identities, which if granted membership to privusergroup through another security group, can cause system-wide failures in the Microsoft Dynamics CRM web application and reporting features. To manually add the objects to Active Directory, use Active Directory Users and Computers. The following table contains the users and computers that you must add to each security group.

Security Group PrivUserGroup

Object Type User

Description User who is running Microsoft Dynamics CRM Server Setup. Computer where Microsoft Dynamics CRM Server 2011 is installed. Computer where the Microsoft Dynamics CRM Email Router is installed (if you are using the E-mail Router). Computer where Microsoft Dynamics CRM Server 2011 is installed. Computer where Microsoft Dynamics CRM Reporting Extensions is installed. User who is running Microsoft Dynamics CRM Server Setup. Any user who will run Microsoft Dynamics CRM. 215

PrivUserGroup

Computer

PrivUserGroup

Computer

SQLAccessGroup

Computer

PrivReportingGroup

Computer

ReportingGroup

User

ReportingGroup

User

You Receive an Unknown Error (0x80005000) error message during a quiet-mode installation
You may receive an "Unknown Error (0x80005000)" during a quiet-mode installation. This issue can occur when you try to install Microsoft Dynamics CRM Server 2011 on a Windows Server computer that does not have Internet Information Services (IIS) installed and configured. To resolve this issue, install Internet Information Services (IIS) and then run Setup again. For more information about how to install Internet Information Services (IIS), see the Windows Server Help.

See Also
Install Microsoft Dynamics CRM E-mail Router Microsoft Dynamics CRM 2011 Post-Installation and Configuration Guidelines

Microsoft Dynamics CRM 2011 Post-Installation and Configuration Guidelines

This section describes several of the Microsoft Dynamics CRM components and tasks that the administrator should configure after installing the application. Because Microsoft Dynamics CRM has a rich feature and functionality set, this section is not meant to be an exhaustive resource used to configure any and all deployments. Instead, use this section as a guideline to determine what components to configure, based on your organization's needs.

In This Topic
Make Microsoft Dynamics CRM client-to-server network communications more secure Configure a Microsoft Dynamics CRM Internet-facing deployment Add or remove sample data Configuration guidelines for new deployments Install a solution from the Microsoft Dynamics Marketplace Instructions for removing the Resource Center

216

Make Microsoft Dynamics CRM client-to-server network communications more secure

With any network design, it is important to consider the security of your organization's client-toserver communications. When making necessary decisions that can help protect data, we recommend that you understand the following information about Microsoft Dynamics CRM network communication and about the technology options that are available to you that provide more secure data transmissions. If you installed Microsoft Dynamics CRM or upgraded to Microsoft Dynamics CRM 2011 to an internally-facing Web site that is not already configured for HTTPS, Microsoft Dynamics CRM client-to-server communications are not encrypted. When using a Web site that supports only HTTP, information from Microsoft Dynamics CRM clients is transmitted in clear text and, therefore, possibly vulnerable to malicious intent, such as "man-in-the-middle" type attacks that could compromise content by adding scripts to perform harmful actions.

Configuring Microsoft Dynamics CRM for HTTPS

Configuring a site for HTTPS will cause a disruption in the Microsoft Dynamics CRM application so plan the configuration when it will result in minimal disruption to users. The high-level steps for configuring Microsoft Dynamics CRM for HTTPS are as follows: 1. In Microsoft Dynamics CRM Deployment Manager, disable the server where the Web Application Server, Organization Web Service, Discovery Web Service, and Deployment Web Service roles are running. If this is a Full Server deployment, all server roles are running on the same computer. For information about how to disable a server, see Microsoft Dynamics CRM Deployment Manager Help. 2. Configure the Web site where the Web Application Server role is installed to use HTTPS. For more information about how to do this, see Internet Information Services (IIS) Help. 3. Set the binding in Microsoft Dynamics CRM Deployment Manager. This is done on the Web Address tab of the Properties page for the deployment. For more information about how change the bindings see the "Microsoft Dynamics CRM deployment properties" topic in Microsoft Dynamics CRM Deployment Manager Help. 4. If you want to make other Microsoft Dynamics CRM services more secure and Microsoft Dynamics CRM is installed by using separate server roles, repeat the previous steps for the additional server roles.

217

Configure a Microsoft Dynamics CRM Internet-facing deployment

You can deploy Microsoft Dynamics CRM so that remote users can connect to the application through the Internet. For more information, see Configure a Microsoft Dynamics CRM Internetfacing deployment.

Add or remove sample data

Sample data is available to help you become familiar with how Microsoft Dynamics CRM works. By using sample data, work with records and see how they relate to each other, how data displays in charts, and see what information is in reports. Sample data can be added or removed from within the Microsoft Dynamics CRM application. For more information about sample data, see the "Manage Sample Data" topic in Microsoft Dynamics CRM Help.

Configuration guidelines for new deployments

After you've completed installing Microsoft Dynamics CRM, but before the business users in your organization start using it, there are some basic tasks that you, as the Microsoft Dynamics CRM administrator, should complete. These tasks include defining business units and security roles, adding users, and importing data. For more information, see Getting started for Microsoft Dynamics CRM administrators.

Install a solution from the Microsoft Dynamics Marketplace

Use solutions to extend functionality and the user interface. Customizers and developers distribute their work as solutions. Organizations use Microsoft Dynamics CRM to install and uninstall the solution. For more information about how to install a solution, see Install, upgrade, or uninstall a solution from the Microsoft Dynamics Marketplace.

Instructions for removing the Resource Center

The Microsoft Dynamics CRM Resource Center is a place in the application where users, administrators, and implementers will find information to help them use and configure 218

Microsoft Dynamics CRM 2011. The Resource Center displays content hosted by Microsoft and is not displayed when users are offline. If Microsoft Dynamics CRM users do not have access to the content on the Resource Center, it can be removed from the application.

Remove the Resource Center from the application 1. Export the Site Map by using the Export Customizations feature. 2. Select one of the following options: Export the Default solution. Add the Site Map to a new or existing solution. i. In the solution, click Components.

ii. On the Actions toolbar, click Add Existing and then click Site Map. iii. Export the solution as an unmanaged solution. 3. Extract the files from the compressed .zip file. 4. Open the customizations.xml file by using a text editor such as Microsoft Visual Studio or Microsoft Notepad. 5. Locate the following node in the file:
/ImportExportXml/SiteMap/SiteMap/Area Id="ResourceCenter"

6. Comment the area by using <!-- and -- > tags where the Id attribute is set to "ResourceCenter" as follows:
<!--<Area Id="ResourceCenter" ResourceId="Area_ResourceCenter" Icon="/_imgs/resourcecenter_24x24.gif" DescriptionResourceId="ResourceCenter_Area_Description"> <Group Id="ResourceCenter"> <SubArea Id="nav_lc_overview" ResourceId="Homepage_LearningOverview" DescriptionResourceId="LearningOverview_SubArea_Description"

219

Icon="/_imgs/ico_18_129.gif" Url="/resourcecenter/overview.aspx" AvailableOffline="false" /> <SubArea Id="nav_lc_customization" ResourceId="Homepage_LearningCustomization" DescriptionResourceId="LearningCustomization_SubArea_Descript ion" Icon="/_imgs/area/18_settings.gif" Url="/resourcecenter/customization.aspx" AvailableOffline="false"> <Privilege Privilege="CreateEntity" /> <Privilege Entity="solution" Privilege="Create" /> <Privilege Privilege="ImportCustomization" /> </SubArea> </Group> </Area>-->

Note By commenting the Resource Center area you preserve the capability to restore it in the future by repeating this procedure and removing the comment tags. 7. Save your changes to the customizations.xml file. 8. Create a new compressed zip file using all the extracted solution files, including your edited customizations.xml. Tip In Windows Explorer, select all the files, then right-click, and in the context menu, click Send To and Compressed (zipped) folder. 9. Import the new solutions file. a. In the Microsoft Dynamics CRM application Navigation Pane, click Settings, click Customization, and then click Solutions. b. Click Import. 220

c. Click Browse, locate your modified solutions .zip file created in step 8, click Next, and then click Import. d. When the import completes, click Publish All Customizations. e. Click Close to close the Import Solutions dialog box. 10. Verify that the Resource Center area was removed. The import process performs validations on the Site Map. However, it is still possible that some errors might occur. If errors occur, the default Site Map will be applied and an error message will be displayed. You must fix the errors in the Site Map and import it again.

See Also
Microsoft Dynamics CRM 2011 Installing Guide

Microsoft Dynamics CRM 2011 Operating and Maintaining Guide

221