Best practices for MS Dynamics Dev/UAT installation

Hello Everyone

We are planning to to install Microsoft Dynamics in our organization in production environment but before we do that we wanted to test it in a development/UAT environment. To achieve this do we need to keep the Dev/UAT installation in completely separate AD domain so that when we install it on the production environment it doesn't create any AD problem or we can install both dev/uat and production dynamics installation on same AD ? Just wanted your expert opinion on this.
LVL 4
James GlenIT EngineerAsked:
Who is Participating?
 
Feridun KadirConnect With a Mentor Principal ConsultantCommented:
Assuming you mean Dynamics CRM, then there is no reason why you can't have production and development in the same AD domain.

CRM uses AD for user authentication and to create security groups for each installation (deployment). The security groups that the CRM installation creates include a GUID in the name so if more than deployment is installed you will have two sets of security groups and naming is not an issue.

Depending on your requirements and how separate you want the production and development environment to be you could have one deployment of CRM and two organizations within the deployment (one for production and one for development).
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.