locked
Redeployment Tool for MS CRM 3.0 install in same domain? RRS feed

  • Question

  • Hi all,

    I want 2 separate CRM 3.0 installations like this:

    1. CRM 3.0 Server A with database A
    2 CRM 3.0 Server B with database B(its copy of database A)

    within same Domain.

    I already have one installation in a domain.

    Do I have to use the redeployment tool? I believe we only use this tool to deploy CRM 3.0 onto a different domain. However, I read somewhere that you need to use the tool as there might be possible conflicts with the GUIDS in the copy of the database A (database B)?

    Otherwise it does make sense to just run the intall and then point to the existing database when the screen comes up about selecting the sql server.

    Stanley 

    Friday, October 8, 2010 6:17 AM

Answers

  • Note: Thanks Ivan
    You can have two instances of Microsoft CRM 3.0 on the same domain. Security roles in earlier versions of Microsoft CRM were implemented in Active Directory. However, in version 3.0, security roles are stored in the Microsoft CRM database and you can configure the same user with different security roles in each instance. While Microsoft CRM 3.0 leverages Active Security to validate a user's credentials when the user logs into the application, access to specific functionality in the application is controlled by security roles which are native to Microsoft CRM database.

    The Microsoft CRM 3.0 setup does create four groups in Active Directory to store information about the users and computers included in a Microsoft CRM instance. These groups are called:

     

    UserGroup

    UserPrivGroup

    ReportingGroup

    SQLAccessGroup

    They are used to grant access to various system resources to users and do not control access to application functionality directly the way that security roles do. By default, the Microsoft CRM setup creates these groups in Active Directory and hard-codes their names as listed above. You may choose to use a second set of Active Directory groups for your second Microsoft CRM instance in order to eliminate any concurrency issues between the two instances. You can do that by running the Microsoft CRM setup from the command line and specifying an XML configuration file for the configuration. This XML configuration file allows you to specify different names for the aforementioned Active Directory groups. For more information on installing Microsoft CRM using an XML configuration file, refer to Chapter 19 in the Microsoft CRM 3.0 Implementation Guide.

    Although you can install two instances of Microsoft CRM 3.0 on the same domain, each instance will require its own hardware. If you need to have two separate instances of Microsoft CRM, it may be a better use of your resources to upgrade to Microsoft CRM 4.0, which supports multi-tenancy and allows you to install two instances of Microsoft CRM on the same hardware. This approach will not only limit your hardware investment, but will also simplify maintenance and provide access to some of the great new functionality available in Microsoft CRM 4.0.

    For asssitance in conifguration please feel free to contact me.

    Jeff Loucks | Available Technology | 888-474-2237 | http://msmvps.com/blogs/jeffloucks

    • Proposed as answer by Jeff Loucks Friday, October 8, 2010 6:47 PM
    • Marked as answer by Stanley_Lai Monday, October 11, 2010 8:33 AM
    Friday, October 8, 2010 6:45 PM

All replies

  • Note: Thanks Ivan
    You can have two instances of Microsoft CRM 3.0 on the same domain. Security roles in earlier versions of Microsoft CRM were implemented in Active Directory. However, in version 3.0, security roles are stored in the Microsoft CRM database and you can configure the same user with different security roles in each instance. While Microsoft CRM 3.0 leverages Active Security to validate a user's credentials when the user logs into the application, access to specific functionality in the application is controlled by security roles which are native to Microsoft CRM database.

    The Microsoft CRM 3.0 setup does create four groups in Active Directory to store information about the users and computers included in a Microsoft CRM instance. These groups are called:

     

    UserGroup

    UserPrivGroup

    ReportingGroup

    SQLAccessGroup

    They are used to grant access to various system resources to users and do not control access to application functionality directly the way that security roles do. By default, the Microsoft CRM setup creates these groups in Active Directory and hard-codes their names as listed above. You may choose to use a second set of Active Directory groups for your second Microsoft CRM instance in order to eliminate any concurrency issues between the two instances. You can do that by running the Microsoft CRM setup from the command line and specifying an XML configuration file for the configuration. This XML configuration file allows you to specify different names for the aforementioned Active Directory groups. For more information on installing Microsoft CRM using an XML configuration file, refer to Chapter 19 in the Microsoft CRM 3.0 Implementation Guide.

    Although you can install two instances of Microsoft CRM 3.0 on the same domain, each instance will require its own hardware. If you need to have two separate instances of Microsoft CRM, it may be a better use of your resources to upgrade to Microsoft CRM 4.0, which supports multi-tenancy and allows you to install two instances of Microsoft CRM on the same hardware. This approach will not only limit your hardware investment, but will also simplify maintenance and provide access to some of the great new functionality available in Microsoft CRM 4.0.

    For asssitance in conifguration please feel free to contact me.

    Jeff Loucks | Available Technology | 888-474-2237 | http://msmvps.com/blogs/jeffloucks

    • Proposed as answer by Jeff Loucks Friday, October 8, 2010 6:47 PM
    • Marked as answer by Stanley_Lai Monday, October 11, 2010 8:33 AM
    Friday, October 8, 2010 6:45 PM
  • Thanks no redeployment tool was needed and everything seems fine.
    Monday, October 11, 2010 8:33 AM