locked
what should we consider while moving CRM4 servers from one domain to another? RRS feed

  • Question

  • Hi all,

    we have 2 domains. and the CRM4 server and CRM db server are in domain A.
    Now we would like to move the computers from domain A to domain B.
    all applications will still on the original computers, just change the computers' domain. Would it affect the CRM4 system?
    we already created the AD accounts for every user in the 2 domains. what should we do to ensure the CRM4 working well in the new domain?

    Thanks in advance.
    Regards,
    Alan

    www.ProSourceDev.com
    Wednesday, July 22, 2009 2:26 AM

Answers

  • Hi Alan,

    see this article how to do that:
     

    http://support.microsoft.com/default.aspx?scid=kb;en-us;952934&sd=rss&spid=12976


    Viele Grüße

    Michael Sulz
    axcentro GmbH
    MVP für Microsoft Dynamics CRM
    Wednesday, July 22, 2009 7:12 AM
  • Hi Alan,

    you write, you want to move the server(CRM and SQL) from Domain A to Domain B.
    In this case, you have to save the db in domain A, restore the db in Domain B with the SQL server management studio and then use the deployment manager to import the organisation.
    Viele Grüße

    Michael Sulz
    axcentro GmbH
    MVP für Microsoft Dynamics CRM
    Wednesday, July 22, 2009 8:30 AM
  • Hi Alan,

    yes, you have to uninstall CRM before domain change.
    Viele Grüße

    Michael Sulz
    axcentro GmbH
    MVP für Microsoft Dynamics CRM
    Wednesday, July 22, 2009 9:32 AM
  • You will also need to do some extra steps on the SQL server.
    Remember that the machine account for the SQL server has attributes within active Directory.   These attributes are not going to appear by themselves.

    Also the instance on the SQL server should be dropped and then readded.

    I did something like this for a Great Plains server as well.
    http://www.sqlmag.com/Articles/ArticleID/96265/96265.html?Ad=1


    select * from sys.servers

    Therefore a new instance name was necessary also. I used the SQL Server 2005 sp_dropserver and sp_addserver stored procedures as follows to fix this problem:

    sp_dropserver computercs 
    GO sp_addserver DEVGPSQL2005, LOCAL GO

    Then, I again ran

    select * from sys.servers 

    Wednesday, July 22, 2009 12:52 PM
    Moderator

All replies

  • Hi Alan,

    see this article how to do that:
     

    http://support.microsoft.com/default.aspx?scid=kb;en-us;952934&sd=rss&spid=12976


    Viele Grüße

    Michael Sulz
    axcentro GmbH
    MVP für Microsoft Dynamics CRM
    Wednesday, July 22, 2009 7:12 AM
  • Hi Michael,

    thanks your response.
    I've reviewed that article. But not sure which one meet my situation.


    what I must do is reinstalling CRM, right?
    And can I use the domain B CRM deployment manager import the crm db on the SQL server in domain A?

    Regards,
    Alan
    www.ProSourceDev.com
    Wednesday, July 22, 2009 7:28 AM
  • Hi Alan,

    you write, you want to move the server(CRM and SQL) from Domain A to Domain B.
    In this case, you have to save the db in domain A, restore the db in Domain B with the SQL server management studio and then use the deployment manager to import the organisation.
    Viele Grüße

    Michael Sulz
    axcentro GmbH
    MVP für Microsoft Dynamics CRM
    Wednesday, July 22, 2009 8:30 AM
  • the crm server and sql server will still on the current machine, just the machines' domain will be change to domain B.
    So I still need to save the db and then restore the db after domain change?

    thanks,
    Alan
    www.ProSourceDev.com
    Wednesday, July 22, 2009 8:35 AM
  • since the new CRM instance will be installed on the same server (just change the computer's domain from A to B), should I uninstall the CRM before domain change? and the custom reports should be saved manually, right? 

    Thanks,
    Alan
    www.ProSourceDev.com
    Wednesday, July 22, 2009 8:51 AM
  • Hi Alan,

    yes, you have to uninstall CRM before domain change.
    Viele Grüße

    Michael Sulz
    axcentro GmbH
    MVP für Microsoft Dynamics CRM
    Wednesday, July 22, 2009 9:32 AM
  • You will also need to do some extra steps on the SQL server.
    Remember that the machine account for the SQL server has attributes within active Directory.   These attributes are not going to appear by themselves.

    Also the instance on the SQL server should be dropped and then readded.

    I did something like this for a Great Plains server as well.
    http://www.sqlmag.com/Articles/ArticleID/96265/96265.html?Ad=1


    select * from sys.servers

    Therefore a new instance name was necessary also. I used the SQL Server 2005 sp_dropserver and sp_addserver stored procedures as follows to fix this problem:

    sp_dropserver computercs 
    GO sp_addserver DEVGPSQL2005, LOCAL GO

    Then, I again ran

    select * from sys.servers 

    Wednesday, July 22, 2009 12:52 PM
    Moderator
  • thank you Curt for the reminder.

    I applied the hotfix 950680, but the workflows still do not work.

    Those workflows were installed by the eService portal for Dynamics CRM4 installation.

    Is there a way to make the workflows and eService portal work?

    Thanks in advance.
    Regards,
    Alan
    www.ProSourceDev.com
    Thursday, July 23, 2009 8:21 AM
  • the workflows work well now. just the CRM asynchronous processing service was stopped.
    start that service, the workflows work.
    www.ProSourceDev.com
    Friday, July 24, 2009 7:13 AM