Best practices for MS Dynamics Dev/UAT installation
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.
Microsoft DynamicsMicrosoft IIS Web ServerExchange