locked
Changing Existing Deployment to Load Balanced - On Premise RRS feed

  • Question

  • We currently have the following in an existing deployment:  CRM1 - app server, all outlook clients are pointed here, SQL1 - db server, RPT1, reports.  We also have a server in production, CRM2, that is pointed to SQL1 but we are not using it.  It was built with the intention of load balancing the app server one day.  We want to go ahead and load balnce the app servers. 

    Leading plan is to keep the name of the CRM instance as CRM1 so we don't have to reconfigure the outlook clients.  So that means we need to rename the current CRM1 server to something like CRM3, and then have the lb name be CRM1. 

    Any suggestions for the best way to do this?  Are there any special considerations so that we don't break anything?  How well does CRM handle application server name changes?

    Thanks
    Monday, October 26, 2009 6:20 PM

Answers

  • To be safe, I'd do the following:
    - Install on crm2, using the existing database
    - Uninstall from crm1
    - Rename crm1 to crm3
    - Install on crm3, using the existing database
    - create the F5 entry called crm1 including the 2 member servers.

    When using load balancing, you need to use a domain account for your service accounts, using network service can lead to issues with SPN's.
    Matt, MVP - Dynamics CRM
    • Proposed as answer by Matt Parks Wednesday, October 28, 2009 2:48 AM
    • Marked as answer by Jim Glass Jr Wednesday, October 28, 2009 3:15 PM
    • Unmarked as answer by duplic8 Thursday, November 19, 2009 9:31 PM
    • Marked as answer by Jim Glass Jr Thursday, April 15, 2010 3:43 PM
    Wednesday, October 28, 2009 2:48 AM

All replies

  • Thank you.  We've looked at that as well as the implementation guide.  Our concern is that CRM won't like it if we change the name of one of the servers it resides on.  Also, we will be using F5 to manage the load balancing. 
    Monday, October 26, 2009 8:36 PM
  • Hi,

    The F5s should work good for load balancing.  If at all possible, I'd recommend testing this change over in a test environment even if it is all made of virtual servers.  Renaming a server can have 'small glitches', but should work.  Nothing that can't be over come, but care must be taken to make sure that:  domain membership is ok, dns udpated, iis still responds ok, any scripts that rely on server name?, etc.

    One thing you may have to do is to 'reconfigure' the outlook crm clients after this change. 

    Good luck :-)
    Alex Fagundes - www.PowerObjects.com
    Monday, October 26, 2009 11:45 PM
  • To be safe, I'd do the following:
    - Install on crm2, using the existing database
    - Uninstall from crm1
    - Rename crm1 to crm3
    - Install on crm3, using the existing database
    - create the F5 entry called crm1 including the 2 member servers.

    When using load balancing, you need to use a domain account for your service accounts, using network service can lead to issues with SPN's.
    Matt, MVP - Dynamics CRM
    • Proposed as answer by Matt Parks Wednesday, October 28, 2009 2:48 AM
    • Marked as answer by Jim Glass Jr Wednesday, October 28, 2009 3:15 PM
    • Unmarked as answer by duplic8 Thursday, November 19, 2009 9:31 PM
    • Marked as answer by Jim Glass Jr Thursday, April 15, 2010 3:43 PM
    Wednesday, October 28, 2009 2:48 AM