Microsoft Dynamics CRM 2011 - Register an Azure-Aware Plug-in with Plug-in Registration Tool

This blog demonstrates how to configure Windows Azure Access Control Service (ACS) and register the ServiceBusPlugin plug-in using the Plug-in Registration tool. The ServiceBusPlugin plug-in is provided with Microsoft Dynamics CRM 2011 and Microsoft Dynamics CRM Online and supports posting the execution context of the current Microsoft Dynamics CRM operation to a Windows Azure solution endpoint. For this walkthrough, the plug-in is registered to post the execution context of the CreateRequest message for an Account entity.

The following prerequisites must be completed before starting this walkthrough:

• Build the Plug-in Registration tool according to the instructions in its Readme file. For more information, see SDK\Tools\PluginRegistration\Readme.docx.  

• Obtain access to Microsoft Dynamics CRM 2011 or Microsoft Dynamics CRM Online. 

• Your system user account must have the System Customizer or System Administrator role to register a plug-in.

• Have access to a Windows Azure platform service namespace, that uses ACS version 1 or 2, to which Microsoft Dynamics CRM will post a message.

Important: Only the Plug-in Registration tool from the 5.0.6 or newer version of the Microsoft Dynamics CRM SDK supports ACS v2.

•  If you are using Microsoft Dynamics CRM 2011, the server must be configured for Windows Azure integration. 

• There must be a listener application actively listening to the specified solution endpoint for Microsoft Dynamics CRM to successfully post.

Connect to the Microsoft Dynamics CRM Server

•  Run the Plug-in Registration tool.

Note: The Microsoft.Crm.Sdk.Proxy.dll and Microsoft.Xrm.Sdk.dll assemblies must be in the same folder as the tool’s executable file or in your computer’s Global Assembly Cache (GAC) for the tool to run.

•  Click Create New Connection.

• In the Connections panel, enter a name for the connection, the URL of the server where the Microsoft Dynamics CRM Discovery service is hosted, and your logon system user name.

Connection Form Fields

• Check Use Saved Credentials if your logon credentials are saved in the Windows credential cache on your computer. Otherwise, do not check this box and you will be prompted to enter your password.

• Click Connect. 

You should now see a list of available organizations that you belong to in the Connections panel.

Create a Service Endpoint Configuration

• Double-click an organization in the Connections tree view.

• Navigate to the Register menu and select Register New Endpoint.

• Fill out the Service Endpoint Details dialog box with the information related to your solution as shown in the following figure and described in the table that follows. Make sure the contract you specify is the same contract used by your solution’s listener application.

Register a New Endpoint

UI Element: Name (field)   
Description: A name for your service endpoint registration.

UI Element: Description (field)  
Description: A description of this endpoint registration.

UI Element: Solution Namespace (field)  
Description: The name of the solution’s service namespace.

UI Element: Path (field)  
Description: The path of your project. For example, given a service endpoint URL of https://crmsdkdemo-sb.accesscontrol.windows.net/TwoWayService/Demo, the path is TwoWayService/Demo.

UI Element: Contract (drop-down menu)   
Description: The endpoint contract. A listener application must use this contract to read the posted message.

UI Element: Claim (drop-down menu)  
Description: The claims to send to Windows Azure. Use None for the standard claim. Specify UserId or UserInfo to send additional information about the logged on user.

UI Element: Federated Mode (checkbox)  
Description: Check this box to use federated mode.

UI Element: ID (field)
Description: Non-writeable field that is filled in automatically with the ID of your endpoint configuration.

UI Element: Save & Configure ACS (button)
Description: Saves the configuration you entered and automates the process of configuring ACS for you. Provides an interactive way.

UI Element: Save & Verify Authentication (button)
Description: Saves the configuration you entered and verifies that ACS is configured correctly.

UI Element: Save (button)
Description: Saves the configuration you entered and closes the dialog.

• If you have not yet configured Windows Azure ACS integration with Microsoft Dynamics CRM, and you would like the Plug-in Registration tool to do the configuration for you, click Save & Configure ACS, and then follow the instructions in the next section of this walkthrough. If you have already configured ACS, click Save & Verify Authentication or Save and continue. 

Configure ACS

• After clicking Save & Configure ACS, the ACS Configuration dialog box appears. 

Enter the appropriate data values into the form fields as described in the following table:  

Field Name: Management Key   
Description: The management key for your solution. You can obtain this key value from the Windows Azure Management Portal.

Field Name: Certificate File   
Description: The public certificate file that was used to configure Microsoft Dynamics CRM for integration with Windows Azure.

For Microsoft Dynamics CRM 2011 and Microsoft Dynamics CRM Online, you can download this certificate file from the server. In the Microsoft Dynamics CRM Web application select Settings, select Customizations, and then select Developer Resources. Download and save the certificate file.

Field Name: Issuer Name   
Description: The name of the issuer. This name must be the same name that was used to configure Microsoft Dynamics CRM for Windows Azure integration.

• Click Configure ACS. A log of the configuration process is displayed in the output area of the form.

• Click Close.

• Click Save & Verify Authentication in the Service Endpoint Details dialog box. After the verification is finished you can close the dialog boxes. 

Register the ServiceBusPlugin Plug-in for an Event

• Select the endpoint that you previously registered in the tree view of the tool.

• Navigate to the Register menu and select Register New Step.

• Fill out the Register New Step dialog box for an account create event as shown in the following figure.

Register an Endpoint Step

• Click Register New Step.

The ServiceBusPlugin plug-in will now post the current message containing the execution context to the Service Bus whenever an account is created. The post is performed asynchronously and is not executed immediately. 

Test the Endpoint Registration

After you register the endpoint you can test it. A listener must be running or a queue available on the target endpoint for the service bus post from the plug-in to happen.

Test the Endpoint Registration:

1. Open the Microsoft Dynamics CRM Web application for the same organization that you registered the endpoint under. 
2. Navigate to the workplace, select Accounts, and then click New.
3. Enter an account name, for example: Adventure Works Cycle, into the Account Name field, then click Save & Close.
4. Wait about 10 minutes for the post to occur.
5. Select Settings, and then select System Jobs.
6. Open the system job that has the same name that you specified for your service endpoint. Check the status to see if the post was successful, is waiting, or failed.

You can now unregister the endpoint, if so desired, by selecting it in the tool’s tree view and clicking Unregister.

My above blog is based on Microsoft's Official information.

I hope this blog about 'Microsoft Dynamics CRM 2011 - Register an Azure-Aware Plug-in with Plug-in Registration Tool' was informative. Please feel free to leave your comments.

Microsoft Dynamics CRM 2011 - Using the Plug-in Registration Tool

Summary

Do you have a need to extend Microsoft Dynamics CRM 2011 and Microsoft Dynamics CRM Online by writing and integrating custom code? Whether you are writing a plug-in or a custom workflow activity, you will use the Plug-in Registration tool, provided in the Microsoft Dynamics CRM SDK, to register your custom code with the Microsoft Dynamics CRM system. This blog complements the documentation in the SDK by providing detailed information on how to use the Plug-in Registration tool to register custom code with Microsoft Dynamics CRM 2011 and Microsoft Dynamics CRM Online. However, registering custom workflow activities with Microsoft Dynamics CRM Online is not supported using the registration tool or any other means.

Applies To

Microsoft Dynamics CRM 2011, Microsoft Dynamics CRM Online, Microsoft Visual Studio 2010

Introduction

A plug-in is custom business logic that you can integrate with Microsoft Dynamics CRM 2011 and Microsoft Dynamics CRM Online to modify or augment the standard behavior of the system. Plug-ins are event handlers. They execute in response to a particular event being fired by the platform. You can also write custom workflow activities to add new functionality to processes (formerly known as workflows) that you create.

After you write (or purchase) a plug-in or custom workflow activity, you must register it with Microsoft Dynamics CRM. The Plug-in Registration tool is one of three ways you can register plug-ins and custom workflow activities. The other two methods are: by adding a registered plug-in or custom workflow activity to a solution and installing that solution or by writing custom code that uses the SDK plug-in registration classes. When developing a plug-in or custom workflow activity, the most common registration method is to use the tool. Later when you are ready to package your code for production deployment, you can make use of solutions.

This blog complements the plug-in registration walkthrough provided in the SDK by providing more information about the Plug-in Registration tool itself, where the walkthrough focuses more on the process of plug-in registration. The information in this article applies to all three Microsoft Dynamics CRM deployments: On-premises, IFD, and Online.

Downloading and Building the Tool

The Plug-in Registration tool is provided as a source code sample in the Tools folder of the Microsoft Dynamics CRM SDK download. Review the instructions provided in the Tools/PluginRegistration/Readme.docx file for more information about the tool and instructions on how to build the tool.

Connecting to a Microsoft Dynamics CRM Server

The first operation to perform with the tool is to connect to one or more Microsoft Dynamics CRM 2011 and Microsoft Dynamics CRM Online servers. You can do this by selecting the Create New Connection button in the toolbar.

Connections Toolbar

Enter the connection information for your target Microsoft Dynamics CRM server in the Connection Information part of the Connections pane, and then select Connect. Notice that you are just entering the http[s]://server-name[:port] part of the discovery URL. Enter the user name and password of your Microsoft Dynamics CRM user account as appropriate for the type of server you are connecting to.

Connection Information

A list of organizations that you are a member of is shown in the Connections pane. Select an organization from the list and click Connect or just double-click the organization’s name. A view of registration information related to the selected server and organization is opened in a tabbed pane. Each server and organization you connect to gets its own tab. Select Save if you want to save this connection information for when the tool is run again.

The Reload Organizations button in the toolbar refreshes the connections list and the Remove Connection button deletes the selected connection from the list.

The Main Window

The main window of the tool is shown in the following figure. Notice that Connections pane has been closed in the figure to conserve space. The Registered Plugins & Custom Workflow Activities list displays assemblies, plug-ins, steps, images, custom workflow activities, and service endpoints that are currently registered with the associated server and organization.

Main window after Connecting to an Organization

By default, the Microsoft.Crm.ObjectModel assembly and its related plug-ins and steps are registered with the system. The tool does not allow you to unregister these objects because they are required by Microsoft Dynamics CRM.

You can expand the nodes in the Registered Plugins & Custom Workflow Activities list and select any list item to view registration information about that selected item. You can change the way the list is displayed, according to assembly, entity, or message, by selecting a view in the View menu.

Registering a Plug-in or Custom Workflow Activity

To register a plug-in or custom workflow activity, you must first register the assembly containing that compiled code. You register an assembly by selecting Register New Assembly in the Register menu and then filling out the dialog box that is displayed.

Register New Plug-in Dialog

At the top of the figure in Step #1, I selected the ellipsis button … to the right of the text field and navigated to a plug-in assembly that I built from the SampleCode\CS\Plugins folder of the SDK. Next, in Step #2, I checked two plug-ins to register: AccountNumberPlugin and FollowupPlugin. If instead of plug-ins these were custom workflow activities, I could then just click Register Selected Plug-ins and be done. However, when registering plug-ins, you should proceed to Step #3 and Step #4.

In Step #3, check Sandbox to register the selected plug-ins to execute in the sandbox, an isolated run-time environment. Otherwise, select None. Always specify None when registering a custom workflow activity.

In Step #4, specify where on the server you want the plug-in assembly deployed: in the Microsoft Dynamics CRM database, on the server’s disk under <crmwebroot>\server\bin\assembly, or in the GAC. The most commonly specified option is Database while the Disk option is maintained mostly for backward compatibility with Microsoft Dynamics CRM 4.0. If registering your plug-in or custom workflow activity in the database, you can still debug it.

Finally, select Register Selected Plugins. The assembly and selected plug-ins or custom workflow activities are displayed in the Registered Plugins & Custom Workflow Activities list. However, any registered plug-ins will not execute until you register a step for the plug-in as described in the next topic. On the other hand, custom workflow activities are ready to be included in a workflow.

Registered Assembly and Plug-ins

To update or unregister items in the list, other than a system required item, select the item and click Update or Unregister. Alternately, for an update, simply double-click the item. Notice that to update a plug-in you have to update the registration of its assembly.

Registering a Step

After you have registered an assembly and one or more plug-ins, you can register a step for each plug-in. A step defines when and how you want the plug-in to execute. A plug-in will not execute unless there is one or more steps registered for it.

In the view Display by Assembly, select a plug-in in the list and then select Register New Step in the Register menu. The Register New Step dialog box is displayed.

Register New Step Dialog

The following describe the values you can enter or set in the dialog box:

Control Label: Message
Description: The message that must be processed by the Microsoft Dynamics CRM execution pipeline for the plug-in to execute.

Control Label: Primary Entity
Description: The entity that must be processed by the execution pipeline for the plug-in to execute. No entity value in this field indicates any/all entities.

Control Label: Secondary Entity
Description: Some messages require a secondary entity. See the documentation on the specific message for more information.

Control Label: Filtering Attributes
Description: A list of entity attributes that, when changed, cause the plug-in to execute. A value of null causes the plug-in to execute if any of the attributes change. When you specify a message that supports filtering attributes, for example Update, an ellipsis … button is displayed that, when clicked, allows you to select attributes from a list.

Control Label: Event Handler
Description: The plug-in that is to be executed.

Control Label: Name
Description: A name for the step. The tool sets a suggested name in the field automatically, but you can change it.

Control Label: Run in User’s Context   
Description: Specify the system account that owns any data changes the plug-in makes. The Calling User is the logged on user that initiated the message to be processed.

Control Label: Execution Order   
Description: Specifies the order, also known as rank, that plug-ins are executed within a pipeline stage. Plug-ins registered with an order value of 1 are executed first, followed by plug-ins registered with an order of 2, and so on. However, if there is more than one plug-in in a stage with the same order value, then the plug-in with the earliest compilation date is called first.

Control Label: Eventing Pipeline Stage of Execution    
Description: Specifies when you want the plug-in to execute: before (Pre) or after (Post) the core operation that processes the message.

Control Label: Execution Mode
Description: For plug-ins registered to execute in a Post stage, specify if you want them to execute immediately (Synchronous) or queued to execute later (Asynchronous). For post operations, specifying asynchronous execution results in improved system performance as compared to synchronous execution.

Control Label: Deployment   
Description: Specify where you want the plug-in deployed: on the server, on the Microsoft Dynamics CRM for Outlook with Offline Access, or both.

Control Label: Triggering Pipeline (CRM4 Only)   
Description: For plug-ins developed using the Microsoft Dynamics CRM 4.0 SDK, the plug-ins can execute in one of two supported pipelines: parent and child.

Control Label: Delete AsyncOperation if StatusCode = Successful
Description: When any asynchronous operation completes, a System Job entity is created to record the completion status. You can view these system jobs in the Web application by selecting Settings, and then click System Job. Check this option if you want plug-in related system jobs automatically deleted when the status is successful.

Control Label: Description
Description: A description of the step. Typically, you can describe the purpose of the step for other developers or administrators that might run the registration tool at a later date.

Control Label: Unsecure Configuration, Secure Configuration
Description: If you have written a constructor for the plug-in that takes one or two string arguments, any string values you specify in these fields are passed to the plug-in constructor at run-time.

After you register a step, you will see a new step item under the node of the associated plug-in in the Registered Plugins & Custom Workflow Activities list.

Registering an Image

To register an image, select Register New Image from the Register menu. The Register New Image dialog box is displayed.

Register New Image Dialog

Follow these steps to register an image with a step:

1. Select an existing step in the list.
2. Specify an image type. A pre-image is a snapshot of the entity’s attribute before the core operation. A post-image is a snapshot of the entity’s attribute after the core operation.
3. Enter a descriptive name for the image.
4. Enter an entity alias. The entity alias value you specify is used by your plug-in code as the key into the image collection.
5. Click the ellipsis … button to select the primary entity attributes that should be included in the image. For improved system performance, only select those attributes that you need.
6. Click Register Image.

Registering a Windows Azure Endpoint

When you register a service endpoint you are providing Microsoft Dynamics CRM with the information it needs to communicate with a Windows Azure AppFabric solution endpoint. Once established, this communication channel supports posting the execution context of the message currently being processed by Microsoft Dynamics CRM to the AppFabric Service Bus.

Step-by-step instructions about how to register a service endpoint, configure Windows Azure AppFabric ACS, and register a plug-in to post the execution context can be found in my blog Microsoft Dynamics CRM 2011 - Register an Azure-Aware Plug-in with Plug-in Registration Tool.

This article provides detailed information about the features of the Plug-in Registration tool and an explanation of the various form fields, settings, and data entry values. The topics covered also provide links to the related SDK documentation for more in-depth research. Try registering some of the sample plug-ins or custom workflow activities provided in the SDK download. Soon, you will be writing and registering your own custom plug-ins or custom workflow activities.

My above blog is based on Microsoft's Official information (by Peter Hecke). Peter Hecke is a programming writer on the Microsoft Dynamics CRM SDK team and is co-author of the SDK since version 1.3.

I hope this blog about 'Microsoft Dynamics CRM 2011 - Using the Plug-in Registration Tool' was informative. Please feel free to leave your comments.

Microsoft Dynamics CRM 2011 and Microsoft Dynamics CRM Online - Entity Relationship Diagram For Activities Entity Model

This Microsoft Office Visio 2010 diagram shows the logical entity relationship (logical database structure) for Microsoft Dynamics CRM 2011 and Microsoft Dynamics CRM Online - Activities Entity Model.

The logical relationships reflect the programming model for Microsoft Dynamics CRM 2011 and Microsoft Dynamics CRM Online - Activities Entity Model.

Entity Relationship Diagram For Activities Entity Model

I have highlighted different areas of this entity relationship diagram image, so that it is more clearly visible.

1) Below image highlights the main entities "fax", "email" and "phonecall". It highlights the relationship with "queueitem".

Entity Relationship Diagram For Activities Entity Model - Highlight 1

2) Below image highlights the relationship with "orderclose", "service", "lead", "incident", "userentityinstancedata" and "activitymimeattachment".

Entity Relationship Diagram For Activities Entity Model - Highlight 2

3) Below image highlights the relationship with "campaignactivityitem", "account", "subscription", "activityparty" and "bulkdeletefailure".

Entity Relationship Diagram For Activities Entity Model - Highlight 3

4) Below image highlights the relationship with "owner", "task", "contact" and "incidentresolution".

Entity Relationship Diagram For Activities Entity Model - Highlight 4

5) Below image highlights the relationship with "campaign" and "annotation".

Entity Relationship Diagram For Activities Entity Model - Highlight 5

6) Below image highlights the relationship with "processsession", "connection", "quote" and "transactioncurrency".

Entity Relationship Diagram For Activities Entity Model - Highlight 6

7) Below image highlights the relationship with "emailhash", "duplicaterecord", "campaignresponse" and "bulkoperation".

Entity Relationship Diagram For Activities Entity Model - Highlight 7

8) Below image highlights the relationship with "campaignactivity", "contract", "recurrencerule" and "opportunityclose".

Entity Relationship Diagram For Activities Entity Model - Highlight 8

9) Below image highlights the relationship with "invoice", "quoteclose", "asyncoperation" and "recurringappointmentmaster".

Entity Relationship Diagram For Activities Entity Model - Highlight 9

10) Below image highlights the relationship with "principalobjectattributeaccess", "serviceappointment", "bulkoperationlog" and "salesorder".

Entity Relationship Diagram For Activities Entity Model - Highlight 10

 11) Below image highlights the relationship with "opportunity" and "appointment".

Entity Relationship Diagram For Activities Entity Model - Highlight 11

My above blog is based on Microsoft's Official information.

I hope this blog about 'Microsoft Dynamics CRM 2011 and Microsoft Dynamics CRM Online - Entity Relationship Diagram For Activities Entity Model' was informative. Please feel free to leave your comments.

Microsoft Dynamics CRM 2011 E-mail Router Deployment Scenarios. On Premises Scenario 1: Configure Microsoft Dynamics CRM to use the E-mail Router for incoming and outgoing e-mail. PART-8 in Series [Test and publish the new profiles and deployment]

This blog will show how to configure the E-mail Router to transfer e-mail messages to and from Microsoft Dynamics CRM. This blog series has 8 parts and this is the eighth part, PART-8.

The last step in configuring Microsoft Dynamics CRM to use the E-mail Router is to publish the new incoming and outgoing configuration profiles and deployment. Before you start this step, you must test connectivity to verify that everything connects successfully.

To test connectivity

1.    Start the E-mail Router Configuration Manager.

2.    Click the Users, Queues, and Forward Mailboxes tab.

3.    Under Select a CRM Deployment to view users and mailboxes, select the deployment that you created.

Click Users and Queues and click Load Data. This displays the Microsoft Dynamics CRM users who are configured to use the E-mail Router.

Notes:
If an error appears when you click Load Data, verify that the correct organization name is listed under Select a CRM Deployment to view users and mailboxes.

Clicking Load Data displays only users with approved e-mail addresses, regardless of the e-mail  settings of those users.

If no users are listed after you click Load Data, or if users are missing, make sure that the missing user's settings are correct by following the steps in "Set e-mail access type to E-mail Router in Microsoft Dynamics CRM".

4.    If you want to change the Incoming or Outgoing configuration profile that will be used for a particular user, double-click the user record to open it, change the selection for the Incoming Configuration Profile or Outgoing Configuration Profile, and then click OK.

Note:
Creating individual profiles for users can be a tedious task: You first need to gather mailbox credentials for each user and then create profiles and assign them to each user. You can avoid this if you can take advantage of the Delegation/Impersonation rights of an Administrator account on your e-mail server. That is, if you know of a single Administrator account that has Delegation/Impersonation rights over all other user accounts, you need to create only one incoming profile and one outgoing profile in which you specify the credentials of the Administrator account. When you do this, you use this single profile for all users.

5.    Click Test Access. The E-mail Router Configuration Manager performs tests on selected users for both the incoming and the outgoing profile. A successful test displays a "Succeeded" message in green text. To close the Test Access window, click Close.

6.    Click Publish. Successfully publishing the configuration displays the message: "Configuration changes have been saved and the E-mail Router settings have been published." Click OK to close the message box. 

Note:
Publishing the configuration saves it to an .xml file that is located in the following folder:
<Drive>:\Program Files\Microsoft CRM Email\Service\Microsoft.Crm.Tools.EmailAgent.xml

You have now successfully configured Microsoft Dynamics CRM to use the E-mail Router for incoming and outgoing Microsoft Dynamics CRM e-mail.


Previous Part in this Series: PART-7: Microsoft Dynamics CRM 2011 E-mail Router Deployment Scenarios. On Premises Scenario 1: Configure Microsoft Dynamics CRM to use the E-mail Router for incoming and outgoing e-mail. PART-7 in Series [Set e-mail access type to E-mail Router in Microsoft Dynamics CRM]

My above blog is based on Microsoft's Official information.

I hope this blog about 'Microsoft Dynamics CRM 2011 E-mail Router Deployment Scenarios. On Premises Scenario 1: Configure Microsoft Dynamics CRM to use the E-mail Router for incoming and outgoing e-mail. PART-8 in Series [Test and publish the new profiles and deployment]' was informative. Please feel free to leave your comments.

Microsoft Dynamics CRM 2011 E-mail Router Deployment Scenarios. On Premises Scenario 1: Configure Microsoft Dynamics CRM to use the E-mail Router for incoming and outgoing e-mail. PART-7 in Series [Set e-mail access type to E-mail Router in Microsoft Dynamics CRM]

This blog will show how to configure the E-mail Router to transfer e-mail messages to and from Microsoft Dynamics CRM. This blog series has 8 parts and this is the seventh part, PART-7.

Before users can send and receive e-mail by using the Microsoft Dynamics CRM E-mail Router, you must configure each user for this functionality. To do this, follow these steps:

To set a user's e-mail access type

1.    Open the Microsoft Dynamics CRM Web client as a user who has the Microsoft Dynamics CRM system administrator role.

2.    Click Settings, click Administration, and then click Users.

3.    Double-click the user's name to open the user record.

4.    Select E-mail Router from the E-mail access type - Incoming list.

5.    Select E-mail Router from the E-mail access type - Outgoing list.

6.    Click Save & Close.

Note:
By default, after a user is added or a user's e-mail address is changed, that e-mail address must be approved by a system administrator. However, you can change the requirement that e-mail addresses must be approved; to do this, follow the steps in To change the requirement for approval of users:

To change the requirement for approval of users

1.    As a system administrator, open the Microsoft Dynamics CRM Web application.

2.    Click Settings and then, under System, click Administration.

3.    On the Administration page, click System Settings. The System Settings - Webpage Dialog dialog box appears.

4.    Click the E-mail tab.

5.    Under Configure e-mail processing, check or clear the following check boxes:

• Process e-mails only for approved users

• Process e-mails only for approved queues

Previous Part in this Series: PART-6: Microsoft Dynamics CRM 2011 E-mail Router Deployment Scenarios. On Premises Scenario 1: Configure Microsoft Dynamics CRM to use the E-mail Router for incoming and outgoing e-mail. PART-2 in Series [Configure the Microsoft Dynamics CRM deployment]

Next Part in this Series: PART-8: Microsoft Dynamics CRM 2011 E-mail Router Deployment Scenarios. On Premises Scenario 1: Configure Microsoft Dynamics CRM to use the E-mail Router for incoming and outgoing e-mail. PART-8 in Series [Test and publish the new profiles and deployment]

My above blog is based on Microsoft's Official information.

I hope this blog about 'Microsoft Dynamics CRM 2011 E-mail Router Deployment Scenarios. On Premises Scenario 1: Configure Microsoft Dynamics CRM to use the E-mail Router for incoming and outgoing e-mail. PART-7 in Series [Set e-mail access type to E-mail Router in Microsoft Dynamics CRM]' was informative. Please feel free to leave your comments.

Microsoft Dynamics CRM 2011 E-mail Router Deployment Scenarios. On Premises Scenario 1: Configure Microsoft Dynamics CRM to use the E-mail Router for incoming and outgoing e-mail. PART-6 in Series [Configure the incoming e-mail profile - Steps for POP3 E-mail Server Type]

This blog will show how to configure the E-mail Router to transfer e-mail messages to and from Microsoft Dynamics CRM. This blog series has 8 parts and this is the sixth part, PART-6.

Configure Microsoft Dynamics CRM to use the E-mail Router for incoming e-mail using POP3 E-mail Server Type

If your e-mail server type is not POP3, see Steps for Exchange E-mail Server Type.

Note:
For the POP3 E-mail Server Type, you can choose between two authentication types:

E-mail Server Type: POP3
Protocols: POP3
Authentication Types: NTLM

E-mail Server Type: POP3   
Protocols: POP3
Authentication Types: Clear Text

1.    Notice that the Protocol is automatically set to POP3.

2.    For Authentication Type, specify the authentication method that is used to connect the E-mail Router to the POP3 account.

• If you are connecting to an internal Exchange POP3 server, you can select NTLM authentication.

• If you are connecting to an external Exchange POP3 server, you can select Clear Text authentication.

• If your POP3 account resides with an ISP, contact the ISP to obtain the authentication type to access this account.

3.    For E-mail Server, type the POP3 server name and domain. For example, type POP3servername.domain.com. If the POP3 account resides with an ISP, obtain the server name from the ISP.

Note:
This is the same incoming e-mail server name you would use to connect Outlook to the POP3 account. To obtain the correct URL, refer to the POP3 account connection information, which is usually available in the online Help at the site where you registered for the POP3 account.

Alternatively, you can find the POP3 server name and domain in the account properties of the e-mail account, located in Microsoft Outlook.

4.    Select the Use SSL check box if you want to require Secure Sockets Layer (SSL) for the connection to the outgoing e-mail server.

5.    Access Credentials determines the type of credentials that the E-mail Router will use to access the mailbox of the Microsoft Dynamics CRM user. If a choice is available, select Other Specified.

However, if a deployment has been defined that specifies Microsoft Dynamics CRM Online, Other Specified is automatically selected for Access Credentials.

6.    The User Name of the POP3 user's account is automatically set. Type the password for this user.

7.    Click OK to complete the configuration of the incoming profile.

8.    Select the Use SSL check box if you want to require Secure Sockets Layer (SSL) for the connection to the incoming e-mail server.

9.    For Access Credentials, select the type of credentials that the E-mail Router will use to access the mailbox of the Microsoft Dynamics CRM user. The available credential types are Other Specified and User Specified:

• If you select Other Specified, the User Name of the POP3 user's account is automatically obtained from Microsoft Dynamics CRM at runtime, but you must still type the password.

Notes:
Other Specified is typically used for POP3 Microsoft Dynamics CRM queue accounts.
If you select Other Specified, all users or queues that are set to use one particular incoming profile must have the same password in order to connect. You can, however, create multiple incoming profiles for multiple POP3 accounts and assign a different password to each one.

• If you select User Specified, each Microsoft Dynamics CRM user must perform additional configuration steps to grant the E-mail Router access to the POP3 mailbox. (Users can do this by following the steps in the procedure Configure users to allow Microsoft Dynamics CRM E-mail Router access to mailbox.)

10.    Click OK to complete the configuration of the incoming profile.

Configure users or queues to allow Microsoft Dynamics CRM E-mail Router access to mailbox

If your deployment is not SSL enabled, certain functionalities are disabled, including setting a mailbox user name and password to be used by the E-mail Router. This happens for security reasons, because the user name and password that are entered on this page would be transferred in clear text to the Microsoft Dynamics CRM Server.

The best way to re-enable these functionalities is to move your deployment to use SSL for the Microsoft Dynamics CRM Web site. However, you can still enable these functionalities on a non-SSL Microsoft Dynamics CRM Web site. Do this for each deployment.

1.    Open the Microsoft Dynamics CRM Web client.

2.    Click File, and then click Options.

3.    In the Set Personal Options dialog box, click the E-mail tab.

4.    Select the Allow E-mail Router to use my credentials to send and receive e-mail on my behalf check box.

Note:
The E-mail Router works only if the user's primary e-mail address has been approved by a system administrator.

5.    For User name, provide account credentials that are used to access the mailbox. You can use either the user's e-mail address or the user's domain and user name in the format domain\username, for example, contoso\myalias.

6.    For Password, type the user's domain password.

7.    Click OK to close the Set Personal Options dialog box.

Notes:
If the passwords of Microsoft Dynamics CRM users are set to expire periodically in Active Directory, you must complete these steps every time the password changes.

The Allow credentials for the E-mail Router check box is also available on Queue records in Microsoft Dynamics CRM.

8.    Continue with the procedure "Set e-mail access type to E-mail Router in Microsoft Dynamics CRM".


Previous Part in this Series: PART-5: Microsoft Dynamics CRM 2011 E-mail Router Deployment Scenarios. On Premises Scenario 1: Configure Microsoft Dynamics CRM to use the E-mail Router for incoming and outgoing e-mail. PART-5 in Series [Configure the incoming e-mail profile - Steps for Exchange E-mail Server Type]

Next Part in this Series: PART-7: Microsoft Dynamics CRM 2011 E-mail Router Deployment Scenarios. On Premises Scenario 1: Configure Microsoft Dynamics CRM to use the E-mail Router for incoming and outgoing e-mail. PART-7 in Series [Set e-mail access type to E-mail Router in Microsoft Dynamics CRM]

My above blog is based on Microsoft's Official information.

I hope this blog about 'Microsoft Dynamics CRM 2011 E-mail Router Deployment Scenarios. On Premises Scenario 1: Configure Microsoft Dynamics CRM to use the E-mail Router for incoming and outgoing e-mail. PART-6 in Series [Configure the incoming e-mail profile - Steps for POP3 E-mail Server Type]' was informative. Please feel free to leave your comments.

Microsoft Dynamics CRM 2011 E-mail Router Deployment Scenarios. On Premises Scenario 1: Configure Microsoft Dynamics CRM to use the E-mail Router for incoming and outgoing e-mail. PART-5 in Series [Configure the incoming e-mail profile - Steps for Exchange E-mail Server Type]

This blog will show how to configure the E-mail Router to transfer e-mail messages to and from Microsoft Dynamics CRM. This blog series has 8 parts and this is the fifth part, PART-5.

Configure Microsoft Dynamics CRM to use the E-mail Router for incoming e-mail using Exchange E-mail Server Type

Note:
If your organization used the E-mail Router in Microsoft Dynamics CRM 4.0, you can re-use the configuration profiles that you created for Microsoft Dynamics CRM 4.0.

To configure the incoming e-mail profile

1.    Start the E-mail Router Configuration Manager.

2.    Click Configuration Profiles and then click New.

3.    In the E-mail Router Configuration Profile dialog box, type a profile name. For example, type IncomingEmail.

Note:
You might eventually need to create multiple incoming profiles. For this reason, specify profile names that are unique and easy to understand.

4.    For Direction, select Incoming.

5.    For E-mail Server Type, select the type of e-mail server that processes incoming e-mail for your organization.

6.    In the remaining configuration steps, you provide the protocol and authentication information that the E-mail Router will use to communicate with the e-mail server. Your choices for these settings depend on the type of e-mail server. In this blog I will show you the Steps for Exchange E-mail Server Type.

Steps for Exchange E-mail Server Type

Note:
For each E-mail Server Type, specific options are available for protocol and authentication type:
 
E-mail Server Type: Exchange 2003
Protocol: WebDAV
Authentication Type: Windows Authentication

E-mail Server Type: Exchange 2007
Protocol: WebDAV or Exchange Web Services
Authentication Type: Windows Authentication

E-mail Server Type: Exchange 2010
Protocol: Exchange Web Services
Authentication Type: Windows Authentication

E-mail Server Type: Exchange Online
Protocol: Exchange Web Services
Authentication Type: Clear Text

1.    Select the Protocol:

• If your E-mail Server Type is Exchange 2007, select WebDAV or Exchange Web Services.

• If your E-mail Server Type is not Exchange 2007, the Protocol is automatically selected for you.

Note:
For information about the differences between the WebDAV and Exchange Web Services protocols, see Migrating from Exchange 2007 Legacy APIs (http://msdn.microsoft.com/en-us/library/cc535018(exchg.80).aspx).

2.    Notice that the Authentication Type is also automatically selected, regardless of the version of Microsoft Exchange.

3.    Indicate the Location of the e-mail server.

• If the Protocol is WebDAV, type the HTTP-DAV location of the Microsoft Exchange server in the E-mail Server field. Please note the following:

A single installation of Microsoft Exchange Server can consist of multiple endpoints. Specify an endpoint that has HTTP-DAV enabled. (For example, on an Exchange 2003 installation, the endpoint used for Outlook Web Access (OWA) has HTTP-DAV enabled.)

Enter this location in URL format: https://ExchangeServerName or https://ExchangeServerName.domain.com.

If Microsoft Exchange is not installed on the default Web site and port, include the port number. For example: https://ExchangeServerName:8080

• If the Protocol is Exchange Web Services, type the location of the Microsoft Exchange server in the Exchange Web Services URL field.

• A single installation of Microsoft Exchange Server can consist of multiple endpoints. Specify the endpoint that has EWS enabled. Typically, the CAS role server has the EWS endpoint enabled.

Enter this location as a URL in Exchange Web Services (EWS) format: https://ExchangeServerName/EWS/Exchange.asmx.

• If Microsoft Exchange is not installed on the default Web site and port, include the port number. For example: https://ExchangeServerName:8080/EWS/Exchange.asmx.

4.    For Access Credentials, select the type of credentials that the E-mail Router will use to access the mailbox of the Microsoft Dynamics CRM record. The available credential types are Local System Account, User Specified, and Other Specified.

Note:
The account you specify must have full access to the Microsoft Exchange mailbox of the Microsoft Dynamics CRM record. Verify that the rights are set correctly within the mailbox of the account. (These include, at a minimum, the rights to open the mailbox, read mailbox items, create folders, and move mailbox items.) For systems that use Microsoft Exchange 2003, you can change user mailbox rights in the Active Directory Users and Computers tool. For systems that use Microsoft Exchange Server 2007 or Microsoft Exchange Server 2010, use the Exchange Management Shell tool or the Exchange Management Console to change permissions on mailboxes.

If the E-mail Router is installed on the Exchange Server and the Access Credentials are set to Local System Account, no additional Exchange administration is required.

5.    If you select User Specified for Access Credentials, each Microsoft Dynamics CRM user must perform additional configuration steps to grant the E-mail Router access to the Exchange mailbox. To do this, see below "Configure users or queues to allow Microsoft Dynamics CRM E-mail Router access to mailbox".

6.    Click OK to complete the configuration of the incoming profile.

7.    Follow the steps in the procedure below "Configure users or queues to allow Microsoft Dynamics CRM E-mail Router access to mailbox". 

Configure users or queues to allow Microsoft Dynamics CRM E-mail Router access to mailbox

If your deployment is not SSL enabled, certain functionalities are disabled, including setting a mailbox user name and password to be used by the E-mail Router. This happens for security reasons, because the user name and password that are entered on this page would be transferred in clear text to the Microsoft Dynamics CRM Server.

The best way to re-enable these functionalities is to move your deployment to use SSL for the Microsoft Dynamics CRM Web site. However, you can still enable these functionalities on a non-SSL Microsoft Dynamics CRM Web site; to do so, follow the steps mentioned in Keep user credentials secure (on page 35) to set a Windows registry key. Do this for each deployment.

1.    Open the Microsoft Dynamics CRM Web client.

2.    Click File, and then click Options.

3.    In the Set Personal Options dialog box, click the E-mail tab.

4.    Select the Allow E-mail Router to use my credentials to send and receive e-mail on my behalf check box.

Note:
The E-mail Router works only if the user's primary e-mail address has been approved by a system administrator.

5.    For User name, provide account credentials that are used to access the mailbox. You can use either the user's e-mail address or the user's domain and user name in the format domain\username, for example, contoso\myalias.

6.    For Password, type the user's domain password.

7.    Click OK to close the Set Personal Options dialog box.

Notes:
If the passwords of Microsoft Dynamics CRM users are set to expire periodically in Active Directory, you must complete these steps every time the password changes.

The Allow credentials for the E-mail Router check box is also available on Queue records in Microsoft Dynamics CRM.

8.    Continue with the procedure "Set e-mail access type to E-mail Router in Microsoft Dynamics CRM".

Previous Part in this Series: PART-4: Microsoft Dynamics CRM 2011 E-mail Router Deployment Scenarios. On Premises Scenario 1: Configure Microsoft Dynamics CRM to use the E-mail Router for incoming and outgoing e-mail. PART-4 in Series [Configure the outgoing e-mail profile - Use SMTP for outbound e-mail]

Next Part in this Series: PART-6: Microsoft Dynamics CRM 2011 E-mail Router Deployment Scenarios. On Premises Scenario 1: Configure Microsoft Dynamics CRM to use the E-mail Router for incoming and outgoing e-mail. PART-6 in Series [Configure the incoming e-mail profile - Steps for POP3 E-mail Server Type]

My above blog is based on Microsoft's Official information.

I hope this blog about 'Microsoft Dynamics CRM 2011 E-mail Router Deployment Scenarios. On Premises Scenario 1: Configure Microsoft Dynamics CRM to use the E-mail Router for incoming and outgoing e-mail. PART-5 in Series [Configure the incoming e-mail profile - Steps for Exchange E-mail Server Type]' was informative. Please feel free to leave your comments.

Microsoft Dynamics CRM 2011 E-mail Router Deployment Scenarios. On Premises Scenario 1: Configure Microsoft Dynamics CRM to use the E-mail Router for incoming and outgoing e-mail. PART-4 in Series [Configure the outgoing e-mail profile - Use SMTP for outbound e-mail]

This blog will show how to configure the E-mail Router to transfer e-mail messages to and from Microsoft Dynamics CRM. This blog series has 8 parts and this is the fourth part, PART-4.

Configure the outgoing e-mail profile: Use SMTP for outbound e-mail

Note:
If your organization used the E-mail Router in Microsoft Dynamics CRM 4.0, you can re-use the configuration profiles that you created for Microsoft Dynamics CRM 4.0.

1.    Start the E-mail Router Configuration Manager.

2.    Click Configuration Profiles and then click New.

3.    In the E-mail Router Configuration Profile dialog box, type a profile name. For example, type OutgoingEmail.

Note:
You might eventually need to create multiple incoming profiles. For this reason, specify profile names that are unique and easy to understand.

4.    For Direction, select Outgoing.

5.    For E-mail Server Type, select SMTP. The value for Protocol automatically changes to SMTP.

6.    Change the value in the Authentication Type list to the authentication that your SMTP server accepts. Available authentication types include Windows Authentication, Clear Text, and Anonymous.

• If you are using the SMTP protocol of Microsoft Exchange Server, the authentication types that are supported are Clear Text and Windows Authentication.

• If you are using a third-party SMTP server, confirm with your ISP the correct Authentication Type to set.

7.    Type the name of the SMTP server in the E-mail Server field. Use the NetBIOS name or the Fully Qualified Domain Name (FQDN) of the server.

8.    Select Use SSL if you want to require Secure Sockets Layer (SSL) for the connection to the e-mail server that will process outgoing e-mail.

9.    In the Access Credentials list, select how the E-mail Router will gain access to the SMTP server. First, select the type of credentials to use. These are your choices:

• Local System Account. Select this option if you want to authenticate by using the local system account of the computer where the E-mail Router is running. (This choice is available only if Windows Authentication is selected for Authentication Type.)     

• Other Specified. Select this option if you want the E-mail Router to authenticate by using the credentials of a specified user.

10.    If you selected Other Specified, type the credentials to be used by the E-mail Router in the User name and Password fields.
Note:
Whether you selected Local System Account or Other Specified, the credentials used by the E-mail Router must have sufficient rights to send e-mail to the designated SMTP server.

11.    Click OK.

Note:  
If you configure your outgoing e-mail profile to use a Microsoft Exchange server as the SMTP server, additional configuration might be required. This additional configuration is described in Microsoft Knowledge Base (KB) article 915827 (http://support.microsoft.com/kb/915827/en-us). Specifically, follow the procedure about configuring the Microsoft Exchange server to allow relay messages from the Microsoft Dynamics CRM Server 2011.

12.    Go to my blog on Configure Microsoft Dynamics CRM to use the E-mail Router for incoming e-mail. There are 4 parts:

• PART-5: Microsoft Dynamics CRM 2011 E-mail Router Deployment Scenarios. On Premises Scenario 1: Configure Microsoft Dynamics CRM to use the E-mail Router for incoming and outgoing e-mail. PART-5 in Series [Configure the incoming e-mail profile - Steps for Exchange E-mail Server Type]

• PART-6: Microsoft Dynamics CRM 2011 E-mail Router Deployment Scenarios. On Premises Scenario 1: Configure Microsoft Dynamics CRM to use the E-mail Router for incoming and outgoing e-mail. PART-6 in Series [Configure the incoming e-mail profile - Steps for POP3 E-mail Server Type]

• PART-7: Microsoft Dynamics CRM 2011 E-mail Router Deployment Scenarios. On Premises Scenario 1: Configure Microsoft Dynamics CRM to use the E-mail Router for incoming and outgoing e-mail. PART-7 in Series [Set e-mail access type to E-mail Router in Microsoft Dynamics CRM]

• PART-8: Microsoft Dynamics CRM 2011 E-mail Router Deployment Scenarios. On Premises Scenario 1: Configure Microsoft Dynamics CRM to use the E-mail Router for incoming and outgoing e-mail. PART-8 in Series [Test and publish the new profiles and deployment]

Previous Part in this Series: PART-3: Microsoft Dynamics CRM 2011 E-mail Router Deployment Scenarios. On Premises Scenario 1: Configure Microsoft Dynamics CRM to use the E-mail Router for incoming and outgoing e-mail. PART-3 in Series [Configure the outgoing e-mail profile - Use Exchange Online for outbound e-mail]

Next Part in this Series: PART-5: Microsoft Dynamics CRM 2011 E-mail Router Deployment Scenarios. On Premises Scenario 1: Configure Microsoft Dynamics CRM to use the E-mail Router for incoming and outgoing e-mail. PART-5 in Series [Configure the incoming e-mail profile - Steps for Exchange E-mail Server Type]

My above blog is based on Microsoft's Official information.

I hope this blog about 'Microsoft Dynamics CRM 2011 E-mail Router Deployment Scenarios. On Premises Scenario 1: Configure Microsoft Dynamics CRM to use the E-mail Router for incoming and outgoing e-mail. PART-4 in Series [Configure the outgoing e-mail profile - Use SMTP for outbound e-mail]' was informative. Please feel free to leave your comments.

Microsoft Dynamics CRM 2011 E-mail Router Deployment Scenarios. On Premises Scenario 1: Configure Microsoft Dynamics CRM to use the E-mail Router for incoming and outgoing e-mail. PART-3 in Series [Configure the outgoing e-mail profile - Use Exchange Online for outbound e-mail]

This blog will show how to configure the E-mail Router to transfer e-mail messages to and from Microsoft Dynamics CRM. This blog series has 8 parts and this is the third part, PART-3.

Configure the outgoing e-mail profile: Use Exchange Online for outbound e-mail

1.    Start the E-mail Router Configuration Manager.

2.    On the Configuration Profiles tab, click New.

3.    In the E-mail Router Configuration Profile dialog box, type a profile name. For example, type OutgoingEmail.

4.    For Direction, select Outgoing.

5.    For E-mail Server Type, select ExchangeOnline. The value for Protocol automatically changes to Exchange Web Services, the value for Authentication Type automatically changes to Clear Text, and the value for Access Credentials automatically changes to Other Specified.

Note:
Clear Text is secure because SSL is required when ExchangeOnline is the e-mail server.

6.    In the Exchange Web Services URL field, enter the complete URL for the outgoing e-mail server. Use the Exchange Web Services (EWS) URL format (EWS/exchange.asmx), as shown in the following examples:

• https://autodiscover-red001.mail.microsoftonline.com/ews/exchange.asmx - US Data Center

• https://autodiscover-red002.mail.emea.microsoftonline.com/ews/exchange.asmx - EMEA Data Center

• https://autodiscover-red003.mail.apac.microsoftonline.com/ews/exchange.asmx - APAC Data Center

Note:
Instead of typing a URL, you can select the Use Autodiscover option to use the Autodiscover service as the way to obtain the Exchange Web Services URL.

7.    In the Access Credentials section, you specify how the E-mail Router will gain access to the Exchange Online server. Because the Other Specified option is selected, the E-mail Router will authenticate by using the credentials of a specified user. Now, select the User Type. The choices are Administrator and User. If you select User as the user type, the E-mail Router will connect to the mailbox whose credentials consist of the user's e-mail address (used as the User Name) and a password taken from the Password box. If you select Administrator as the user type, the E-mail Router can use the specified credentials to connect to any mailbox within the Exchange Online tenant to send e-mail messages. The send method can be either Delegate Access or Send as permission, depending on which access type that you select.

• For User Name and Password, enter the credentials that the E-mail Router will use to retrieve e-mail messages from the Exchange Online mailbox to which this profile is mapped. The credentials can be either those of the Exchange Online mailbox or those of the Exchange Online tenant administrator. Enter the user name in the username@fulldomain format.

• If you select Administrator as the user type, you must select either Delegate Access or Send as permission as the access type. Delegate Access causes e-mail to be sent as "Send on behalf of" messages. Send as permission causes e-mail to be sent as "Send As" messages.

Notes:
To use delegate access when processing outgoing e-mail messages for Exchange Online, the credentials specified in the outgoing profile must have "PublishingEditor" permissions (Delegate Access) on the Exchange Online mailboxes that need to be accessed. The Exchange Online administrator has this permission by default.

To use Impersonation ("Send as" permission), you must first log a support call with the Exchange Online team to ask for impersonation rights.

8.    To save the configuration profile, click Publish.

9.    Go to my blog on Configure Microsoft Dynamics CRM to use the E-mail Router for incoming e-mail. There are 4 parts:

• PART-5: Microsoft Dynamics CRM 2011 E-mail Router Deployment Scenarios. On Premises Scenario 1: Configure Microsoft Dynamics CRM to use the E-mail Router for incoming and outgoing e-mail. PART-5 in Series [Configure the incoming e-mail profile - Steps for Exchange E-mail Server Type]

• PART-6: Microsoft Dynamics CRM 2011 E-mail Router Deployment Scenarios. On Premises Scenario 1: Configure Microsoft Dynamics CRM to use the E-mail Router for incoming and outgoing e-mail. PART-6 in Series [Configure the incoming e-mail profile - Steps for POP3 E-mail Server Type]

• PART-7: Microsoft Dynamics CRM 2011 E-mail Router Deployment Scenarios. On Premises Scenario 1: Configure Microsoft Dynamics CRM to use the E-mail Router for incoming and outgoing e-mail. PART-7 in Series [Set e-mail access type to E-mail Router in Microsoft Dynamics CRM]

• PART-8: Microsoft Dynamics CRM 2011 E-mail Router Deployment Scenarios. On Premises Scenario 1: Configure Microsoft Dynamics CRM to use the E-mail Router for incoming and outgoing e-mail. PART-8 in Series [Test and publish the new profiles and deployment]

Previous Part in this Series: PART-2: Microsoft Dynamics CRM 2011 E-mail Router Deployment Scenarios. On Premises Scenario 1: Configure Microsoft Dynamics CRM to use the E-mail Router for incoming and outgoing e-mail. PART-2 in Series [Configure the Microsoft Dynamics CRM deployment]

Next Part in this Series: PART-4: Microsoft Dynamics CRM 2011 E-mail Router Deployment Scenarios. On Premises Scenario 1: Configure Microsoft Dynamics CRM to use the E-mail Router for incoming and outgoing e-mail. PART-4 in Series [Configure the outgoing e-mail profile - Use SMTP for outbound e-mail]

My above blog is based on Microsoft's Official information.

I hope this blog about 'Microsoft Dynamics CRM 2011 E-mail Router Deployment Scenarios. On Premises Scenario 1: Configure Microsoft Dynamics CRM to use the E-mail Router for incoming and outgoing e-mail. PART-3 in Series [Configure the outgoing e-mail profile - Use Exchange Online for outbound e-mail]' was informative. Please feel free to leave your comments.

Microsoft Dynamics CRM 2011 E-mail Router Deployment Scenarios. On Premises Scenario 1: Configure Microsoft Dynamics CRM to use the E-mail Router for incoming and outgoing e-mail. PART-2 in Series [Configure the Microsoft Dynamics CRM deployment]

This blog will show how to configure the E-mail Router to transfer e-mail messages to and from Microsoft Dynamics CRM. This blog series has 8 parts and this is the second part, PART-2.

Configure the Microsoft Dynamics CRM deployment

Perform the steps in the following procedure after you have created the outgoing and incoming e-mail profiles.

• To configure a new deployment

1.    Start the E-mail Router Configuration Manager.

2.    Click the Deployments tab.
 
3.    Click New to create a new deployment.
 
4.    Leave the default Deployment option set to My Company.
 
5.    For Microsoft Dynamics CRM Server, type the URL address to open the Microsoft Dynamics   
       CRM Web site. For example, assume the following:

The Microsoft Dynamics CRM Server 2011 name is CRMWEB.

The Microsoft Dynamics CRM Web site runs on port 5555.

The OrganizationName is Adventure Works Cycles.

In this scenario, you would type https://crmweb:5555/AdventureWorksCycles.

Notes 

For OrganizationName on the Deployments tab, use the OrganizationUniqueName of your organization. The OrganizationUniqueName part of the URL must be spelled exactly as it appears in Microsoft Dynamics CRM. To determine the OrganizationUniqueName, start the Microsoft Dynamics CRM Web application as a user who has the System Customizer role. Click Settings and expand Customization. On the Customization page, click Developer Resources. The OrganizationUniqueName is displayed below the Organization Unique Name label.

If this URL address is entered incorrectly, the deployment will be created successfully but you will get an error when you click Load Data on the Users, Queues, and Forward Mailboxes page.  

6.    For Access Credentials, select the type of credentials from Local System Account or Other Specified:

Use Local System Account if you wish to use the machine account to connect to the Microsoft Dynamics CRM Server.

To do so, the E-mail Router must be in the same domain as the Microsoft Dynamics CRM Server and the E-mail Router machine account is added to the Priv User Group in Active Directory.

Alternatively, you may use the Other Specified account to specify the credentials of a user of with the System Administrator Role to connect to Microsoft Dynamics CRM.

7.    For Incoming configuration profile, select the incoming profile that should be mapped to all users and queues by default. The Incoming configuration profile field is optional, so you can leave it blank.

8.    For Outgoing configuration profile, select the outgoing profile that you created.

9.    Click OK to finish creating the deployment. 

Previous Part in this Series: PART-1: Microsoft Dynamics CRM 2011 E-mail Router Deployment Scenarios. On Premises Scenario 1: Configure Microsoft Dynamics CRM to use the E-mail Router for incoming and outgoing e-mail. PART-1 in Series [Overview]

Next Part in this Series: PART-3: Microsoft Dynamics CRM 2011 E-mail Router Deployment Scenarios. On Premises Scenario 1: Configure Microsoft Dynamics CRM to use the E-mail Router for incoming and outgoing e-mail. PART-3 in Series [Configure the outgoing e-mail profile - Use Exchange Online for outbound e-mail]

My above blog is based on Microsoft's Official information.

I hope this blog about 'Microsoft Dynamics CRM 2011 E-mail Router Deployment Scenarios. On Premises Scenario 1: Configure Microsoft Dynamics CRM to use the E-mail Router for incoming and outgoing e-mail. PART-2 in Series [Configure the Microsoft Dynamics CRM deployment]' was informative. Please feel free to leave your comments.