Microsoft Dynamics

1 Introduction

Microsoft Dynamics CRM is a Customer Relationship Management (CRM) software package developed for businesses. It aims to drive sales, productivity and marketing effectiveness through social insights, business intelligence and campaign management in the cloud, on-premises or with a hybrid combination of both.

Such a powerful tool requires reliable and powerful support. The KEMP LoadMaster delivers an exceptional, cost-effective and easy to use solution which, by employing Adaptive Load Balancing, balances requests across Microsoft Dynamics. Microsoft Dynamics consists of Dynamics CRM servers.

When deployed as a pair, two LoadMasters give the security of High Availability (HA). HA allows two physical or virtual machines to become one logical device. Only one of these units is ever handling traffic at any particular moment. One unit is active and the other is a hot standby (passive). This provides redundancy and resiliency, meaning if one LoadMaster goes down for any reason, the hot standby can become active, therefore avoiding any downtime. For more information on HA please refer to: High Availability (HA), Feature Description.

Introduction.png

1.1 Document Purpose

This document is intended to provide guidance on how to deploy Microsoft Dynamics CRM with a KEMP LoadMaster. The KEMP Support Team is available to provide solutions for scenarios not explicitly defined.

The KEMP support site can be found at: https://support.kemptechnologies.com.

1.2 Intended Audience

This document is intended to be used by anyone deploying Microsoft Dynamics CRM with a KEMP LoadMaster.

2 Template

KEMP has developed a template containing our recommended settings for this workload. You can install this template to help when creating Virtual Services, as it automatically populates the settings. This is quicker and easier than manually configuring each Virtual Service. If needed, changes can be made to any of the Virtual Service settings after using the template.

Download released templates from the Templates section on the KEMP documentation page: http://kemptechnologies.com/documentation.

For more information and steps on how to import and use templates, refer to the Virtual Services and Templates, Feature Description on the KEMP Documentation Page.

For steps on how to manually add and configure each of the Virtual Services using the recommended settings, refer to the steps in this document.

3 Enable Subnet Originating Requests Globally

It is best practice to enable the Subnet Originating Requests option globally.

In a one-armed setup (where the Virtual Service and Real Servers are on the same network/subnet) Subnet Originating Requests is usually not needed. However, enabling Subnet Originating Requests should not affect the routing in a one-armed setup.

In a two-armed setup where the Virtual Service is on network/subnet A, for example, and the Real Servers are on network B - Subnet Originating Requests should be enabled on LoadMasters with firmware version 7.1-16 and above.

When Subnet Originating Requests is enabled, the LoadMaster will route traffic so that the Real Server will see traffic arriving from the LoadMaster interface that is in that network/subnet not the Virtual Service address.

When Subnet Originating Requests is enabled globally, it is automatically enabled on all Virtual Services. If the Subnet Originating Requests option is disabled globally, you can choose whether or not to enable Subnet Originating Requests on a per-Virtual Service basis.

To enable Subnet Originating Requests globally, follow the steps below:

1. In the main menu of the LoadMaster Web User Interface (WUI), go to System Configuration > Miscellaneous Options > Network Options.

SCMONO002.png

2. Tick the Subnet Originating Requests check box.

4 Configure Microsoft Dynamics Virtual Services

The environment in which Microsoft Dynamics CRM is deployed determines which of the following set-ups should be used.

4.1 Microsoft Dynamics CRM HTTP

The following are the steps involved and the values required to configure Microsoft Dynamics HTTP Virtual Service:

1. In the main menu of the LoadMaster Web User Interface (WUI), go to Virtual Services > Add New.

Microsoft Dynamics CRM HTTP.png

2. Enter a valid IP address in the Virtual Address text box.

3. Enter 80 in the Port text box.

4. Enter a recognizable Service Name, for example MS Dynamic CRM HTTP.

5. Ensure tcp is selected as the Protocol.

6. Click Add this Virtual Service.

7. Expand the Standard Options section.

Microsoft Dynamics CRM HTTP_1.png

8. Deselect the Transparency check box.

9. Select Super HTTP from the Mode drop-down list.

10. Select 1 Hour from the Timeout drop-down list.

11. Select least connection from the Scheduling Method drop-down list.

12. Set the Idle Connection Timeout to 660 and click the Set Idle Timeout button.

13. Expand the Advanced Properties section.

VSVSAP019.png

14. Select Legacy Operation (X-ClientSide) from the Add HTTP Headers drop-down list.

15. Expand the Real Servers section.

Microsoft Dynamics CRM HTTP_3.png

16. Select the HTTP Protocol from the Real Server Check Parameters drop-down list.

17. Enter / in the URL text box and click Set URL.

18. Ensure HEAD is selected from the HTTP Method drop-down list.

Microsoft Dynamics CRM HTTP_4.png

19. Add the Real Servers:

a) Click the Add New button.

b) Enter the IP address of the CRM Server.

c) Enter 80 as the Port.

The Real Server Port should match the Virtual Service Port.

The Forwarding method and Weight values are set by default. An administrator can change these.

d) Click Add this Real Server. Click OK to the pop-up message.

e) Repeat steps b) to d) above to add more Real Servers as needed, based on the environment.

4.2 Microsoft Dynamics CRM HTTPS

KEMP recommends two Virtual Services be configured for Microsoft Dynamics CRM HTTPS.

The following are the steps involved and the values required to configure the Microsoft Dynamics HTTPS Virtual Services:

4.2.1 Microsoft Dynamics HTTPS (Redirect)

1. In the main menu of the LoadMaster Web User Interface (WUI), go to Virtual Services > Add New.

Microsoft Dynamics HTTPS Redirect.png

2. Enter a valid IP address in the Virtual Address text box.

3. Enter 80 in the Port text box.

4. Enter a recognizable Service Name, for example MS Dynamic CRM HTTPS Redirect.

5. Ensure tcp is selected as the Protocol.

6. Click Add this Virtual Service.

7. Expand the Standard Options section.

Microsoft Dynamics HTTPS Redirect_1.png

8. Deselect the Transparency check box.

9. Select None from the Mode drop-down list.

10. Select round robin from the Scheduling Method drop-down list.

11. Expand the Advanced Properties section.

VSVSAP020.png

12. Select Legacy Operation (X-ClientSide) from the Add HTTP Headers drop-down list.

13. Select 302 Found from the Error Code drop-down list.

14. Enter https://%h%s in the Redirect URL text box and click Set Redirect URL.

4.2.2 Microsoft Dynamics HTTPS (Certificate Installed on Real Server)

1. In the main menu of the LoadMaster Web User Interface (WUI), go to Virtual Services > Add New.

Microsoft Dynamics HTTPS Certificate.png

2. Enter a valid IP address in the Virtual Address text box.

3. Enter 443 in the Port text box.

4. Enter a recognizable Service Name, for example MS Dynamic CRM HTTPS.

5. Ensure tcp is selected as the Protocol.

6. Click Add this Virtual Service.

7. Expand the Standard Options section.

8. Ensure the Force L4 check box is clear.

9. Ensure the Transparency check box is clear.

10. Select Source IP Address from the Mode drop-down list.

11. Select 1 Hour from the Timeout drop-down list.

12. Select least connection from the Scheduling Method drop-down list.

13. Enter 660 as the Idle Connection Timeout and click Set Idle Timeout.

14. Expand the Real Servers section.

Microsoft Dynamics HTTPS Certificate_1.png

15. Select HTTPS Protocol from the Real Server Check Parameters drop-down list.

16. Enter / in the URL text box and click Set URL.

17. Select HEAD from the HTTP Method drop-down list.

Microsoft Dynamics HTTPS Certificate_2.png

18. Add the Real Servers:

a) Click the Add New button.

b) Enter the IP address of the CRM Server.

c) Enter 443 as the Port.

The Real Server Port should match the Virtual Service Port.

The Forwarding method and Weight values are set by default. An administrator can change these.

d) Click Add this Real Server. Click OK to the pop-up message.

e) Repeat steps b) to d) above to add more Real Servers as needed, based on the environment.

 

4.3 Microsoft Dynamics HTTPS Re-encrypt

KEMP recommends two Virtual Services be configured for Microsoft Dynamics CRM HTTPS Re-encrypt.

The following are the steps involved and the values required to configure the Microsoft Dynamics HTTPS Re-encrypt Virtual Services:

4.3.1 Microsoft Dynamics CRM HTTPS Reencrypted Redirect

1. In the main menu of the LoadMaster Web User Interface (WUI), go to Virtual Services > Add New.

Microsoft Dynamics CRM HTTPS_1.png

2. Enter a valid IP address in the Virtual Address text box.

3. Enter 80 in the Port text box.

4. Enter a recognizable Service Name, for example MS Dynamic CRM HTTPS Reencrypted-Redirect.

5. Ensure tcp is selected as the Protocol.

6. Click Add this Virtual Service.

7. Expand the Standard Options section.

Microsoft Dynamics CRM HTTPS_1_1.png

8. Deselect the Transparency check box.

9. Select None from the Mode drop-down list.

10. Select round robin from the Scheduling Method drop-down list.

11. Expand the Advanced Properties section.

VSVSAP021.png

12. Select Legacy Operation (X-ClientSide) from the Add HTTP Headers drop-down list.

13. Select 302 Found from the Error Code drop-down list.

14. Enter https://%h%s in the Redirect URL text box and click Set Redirect URL.

4.3.2 Microsoft Dynamics CRM HTTPS Reencrypt

1. In the main menu of the LoadMaster Web User Interface (WUI), go to Virtual Services > Add New.

Microsoft Dynamics CRM HTTPS_2.png

2. Enter a valid IP address in the Virtual Address text box.

3. Enter 443 in the Port text box.

4. Enter a recognizable Service Name, for example MS Dynamic CRM HTTPS Re-encrypt.

5. Ensure tcp is selected as the Protocol.

6. Click Add this Virtual Service.

7. Expand the SSL Properties section.

Microsoft Dynamics CRM HTTPS_2_1.png

8. Select the Enabled and Reencrypt check boxes for SSL Acceleration.

9. Select the three TLS check boxes for Supported Protocols.

While the Cipher Set automatically selects Default from the drop-down list, users may select BestPractices to ensure all security scans are passed without issue.

10. Expand the Standard Options section.

Microsoft Dynamics CRM HTTPS_2_2.png

11. Ensure Transparency is Disabled.

12. Select Super HTTP from the Mode drop-down list.

13. Select 1 Hour from the Timeout drop-down list.

14. Select least connection from the Scheduling Method drop-down list.

15. Expand the Real Servers section.

Microsoft Dynamics HTTPS Certificate_1.png

16. Select HTTPS Protocol from the Real Server Check Parameters drop-down list.

17. Enter / in the URL text box and click Set URL.

18. Select HEAD from the HTTP Method drop-down list.

Microsoft Dynamics HTTPS Certificate_2.png

19. Add the Real Servers:

a) Click the Add New button.

b) Enter the IP address of the CRM Server.

c) Enter 443 as the Port.

The Real Server Port should match the Virtual Service Port.

The Forwarding method and Weight values are set by default. An administrator can change these.

d) Click Add this Real Server. Click OK to the pop-up message.

e) Repeat steps b) to d) above to add more Real Servers as needed, based on the environment.

 

References

Unless otherwise specified, the following documents can be found at: https://kemptechnologies.com/documentation.

Virtual Services and Templates, Feature Description.

High Availability (HA), Feature Description

Document History

 

Date

Change

Reason for Change

Version

Resp.

Dec 2015

Initial Draft

First draft of document

1.0

KG

Jan 2016

Minor change

Updated Copyright Notices

2.0

LB

Mar 2016

Release updates

Updated for 7.1-34 release

3.0

LB

Oct 2016

Release updates

Updated for 7.2.36 release

4.0

POC

Jan 2017

Minor change

Updated Copyright Notices

5.0

LB

July 2017 Release updates Updated for 7.2.39 release 6.0 CMC

 

 

Was this article helpful?

0 out of 0 found this helpful

Comments