JC_IT
asked on
Exch / AD setup question
I have inherited a very small (<50 users) active directory setup with the domain like example.local
There is only one domain controller which is also a HyperV Host (2008R2).
I want to move the domain controller to a VM on that host and also change the domain to internal.example.com
Exchange has not been installed yet but will be soon.
Nothing but an address book and group policy is really being done with AD.
There is one SQL server on a joined server (another physical machine) but it doesn't rely on AD.
My question is which would be the least work and least likely to cause problems?
1) Create the new VM DC with the new domain internal.example.com and migrate
or
2) Create the new VM DC with the old name example.local and then demote the existing DC on this HyperV host and then rename the domain
or if there is a better 3rd option.
There is only one domain controller which is also a HyperV Host (2008R2).
I want to move the domain controller to a VM on that host and also change the domain to internal.example.com
Exchange has not been installed yet but will be soon.
Nothing but an address book and group policy is really being done with AD.
There is one SQL server on a joined server (another physical machine) but it doesn't rely on AD.
My question is which would be the least work and least likely to cause problems?
1) Create the new VM DC with the new domain internal.example.com and migrate
or
2) Create the new VM DC with the old name example.local and then demote the existing DC on this HyperV host and then rename the domain
or if there is a better 3rd option.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.