Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Several CRM 3.0 servers on one physical server? RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi all,

     

    is it possible to install several CR servers on one physical server? We have situation, that 3 different companies are on the same domain forest and they are sharing their IT infrustructure. One company already intalled CRM server and are using it. Now other company wants to install new server, as they do not need to share data. They would like to use existing physical server for CRM server, and SQL server for both installations. They do not use exchange email router.

     

    thanks for quick replies Smile

     

     

     

    Sunday, January 27, 2008 9:39 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

     

    As Imran points out this is not supported under CRM 3.0.

     

    There are two other possibilities:

     

    1) Use Virtual Server on the physical server to create a new server.

    2) Use Business Units and security to manage and separate the three companies - though this may be unacceptable to the businesses and would be messy.

    Monday, January 28, 2008 12:18 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    By default CRM 3 support one crm deployment per domain. However your requirement can be acheived by using business units, security roles, java scripting and filtering some entities like product. The only problem you will get is that you would not be able to filter the calenders and users can see everyone's calenders. If that is not an issue than you can add different companies on the existing deployment. The company wouldn't be able to see each other's data and you would not require additional hardware or server side softwares. 

     

    Monday, January 28, 2008 1:37 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

     

    You need to have 1 of following solutions:

     

    1. Buy MS CRM 3.0 Enterprise Lisence

    Enterprise license supports you to have multiple Organizations in a single deployment. This won't make separate databases for each organization, rather 1 database will manage all the organizations. This will involve additional cost.

     

    2. Manage scenario using Business Units

    Make a basic Business Unit and make its 3 child business units, each representing a different organization. Don't put any user on the first basic Business Unit [elsethan System Administrator]. Make further Child business units in each Buniess Unit representing the organizations.

    This solution won't involve any additional cost but user & role management will become more critical.

     

    3. Switch to MS CRM 4.0 [Titan]

    Switching to MS CRM 4 is easy using a simple upgrade. It offers you multi-tency option, which allows multiple deployments of CRM server under a single active directory. Don't forget to test it into your test environment before you deploy it. MS CRM 4.0 still contains few bugs, which may affect your work.

     

    So 2nd solution is most recommanded, as it involves less cost. But role & busniess unit management is critical in it. Again it whole data will be managed in a single Database in both 1st and 2nd scenario.

     

    So, let people know which solution you are going to opt...

     

    Regards,

    Sohaib Ahmad

    Tuesday, January 29, 2008 1:00 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    With CRM 3.0 , it is not possible,

     

    With CRM 4.0 multi-tenancy / multiple organization base architecture, you need Enterprise License and it will work.

     

    Best Regards,

    Imran

     

    http://microsoftcrm3.blogspot.com

     

     

    Monday, January 28, 2008 5:19 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

     

    As Imran points out this is not supported under CRM 3.0.

     

    There are two other possibilities:

     

    1) Use Virtual Server on the physical server to create a new server.

    2) Use Business Units and security to manage and separate the three companies - though this may be unacceptable to the businesses and would be messy.

    Monday, January 28, 2008 12:18 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    By default CRM 3 support one crm deployment per domain. However your requirement can be acheived by using business units, security roles, java scripting and filtering some entities like product. The only problem you will get is that you would not be able to filter the calenders and users can see everyone's calenders. If that is not an issue than you can add different companies on the existing deployment. The company wouldn't be able to see each other's data and you would not require additional hardware or server side softwares. 

     

    Monday, January 28, 2008 1:37 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

     

    You need to have 1 of following solutions:

     

    1. Buy MS CRM 3.0 Enterprise Lisence

    Enterprise license supports you to have multiple Organizations in a single deployment. This won't make separate databases for each organization, rather 1 database will manage all the organizations. This will involve additional cost.

     

    2. Manage scenario using Business Units

    Make a basic Business Unit and make its 3 child business units, each representing a different organization. Don't put any user on the first basic Business Unit [elsethan System Administrator]. Make further Child business units in each Buniess Unit representing the organizations.

    This solution won't involve any additional cost but user & role management will become more critical.

     

    3. Switch to MS CRM 4.0 [Titan]

    Switching to MS CRM 4 is easy using a simple upgrade. It offers you multi-tency option, which allows multiple deployments of CRM server under a single active directory. Don't forget to test it into your test environment before you deploy it. MS CRM 4.0 still contains few bugs, which may affect your work.

     

    So 2nd solution is most recommanded, as it involves less cost. But role & busniess unit management is critical in it. Again it whole data will be managed in a single Database in both 1st and 2nd scenario.

     

    So, let people know which solution you are going to opt...

     

    Regards,

    Sohaib Ahmad

    Tuesday, January 29, 2008 1:00 PM