Robert R.ParticipantAug 08, 2011 at 4:06 pm #155792
Forest 01: dev.x.tld
single domain: dev.x.tld (domain controllers: dc01.dev.x.tld , dc02.dev.x.tld )
Forest 02: x.tld
domain: x.tld (domain controllers: dc01.x.tld , dc02.x.tld )
domain: prod.x.tld (domain controllers: dcp01.prod.x.tld , dcp02.prod.x.tld )
domain: office.x.tld (domain controllers: dco01.office.x.tld , dco02.office.x.tld )
domain: devo.x.tld (domain controllers: dcd01.devo.x.tld , dcd02.devo.x.tld )
All domain controllers are Windows 2008 R2 Standard.
User accounts reside in OFFICE.x.tld, and are used to access resources in PROD.x.tld and (inter-forest) DEV.x.tld
A trust relationship exists between OFFICE.x.tld and DEV.x.tld
All servers are VMs running in a WMware vSphere 4.1 environment.
We would like have a domain named dev.x.tld in Forest 02 , to keep with our planned naming conventions.
However, Forest 01 dev.x.tld was the first data center of we created. Unfortunately, we did not foresee the naming conflicts that would result with the future data center in Forest 02.
i.e., we were not aware that we could not have two domain controllers named dc01 in the forest, even though the FQDNs were different (dc01.x.tld vs dc01.dev.x.tld)
Our current plan is to
(1) join the servers in DEV to DEVO
(2) decommission DEV
(3) rename DEVO to DEV using rendom
If anyone has done this, what are some undocumented pitfalls we should be aware of?
And is there a better way to do this?
PS – I didn’t realize it, but this is my 101st post!
You must be logged in to reply to this topic.