2008R2 - Replacing both Domain Controllers - Questions and best practice ideas are appreciated


first off, taking time read post.

i'm thankfully doing testing in test environment before doing in production , has seemed have gone far (knock on wood)

here's scenario:

created virtual images of (2) server 2008 domain controllers operating in production environment.

moved them virtualized test environment (all of below takes place in test environment)

spun (2) server 2008 r2 datacenter machines , promoted them both dc's.

single forest.  both global catalogs.

one has following fsmo roles:  schema mater, domain naming master, pdc , rid.  running dhcp , dns.

the second 1 has following fsmo role:  infrastructure master.  running dhcp , dns.

transferred roles off old dcs new dcs, separated above, , demoted (2) old dc's.

logs great , ad replication status tool shows no errors.

**now testing begins**

i have captured image of win7 machine that's in production , brought on test environment.

keep in mind dns server ip addresses win7 machine has no longer valid i've demoted , have 2 new dcs different ips.

when power on win7 machine unable log on user doesn't have profile.  when try create new profile says "there no logon servers available service logon request"

i have found out if change dns server ip addresses on network card point new servers works (duh), but, , here's question, when decide make these 2 new dcs in production , demote current dcs machines in organization still have ips of old dns servers. have go each machine , change dns ip addresses point new servers?  i'm sure can done in group policy , haven't looked yet how suggest tackle this?

should create alias records in ad point old ip address new ip address?

is suggested drop each machine workgroup , rejoin domain after new dcs in place?

are there small things might missing you've experienced when doing similar.

to test further have powered off first dc schema mater, domain naming master, pdc , rid.  running dhcp , dns.

this leaves 2nd dc infrastructure master on.  running dhcp , dns.

why logs of 2nd dc have following errors:

1)  active directory domain services role: error 2087 "active directory domain services not resolve following dns host name of source domain controller , ip address"

  • yes source dc 1 that's powered off.
  • i understand error says changes in ad not replicated, once again because other off. 
  • will error correct when other dc comes online or there other steps need done once other online?

2)  dhcp server role: error 1059 "the dhcp service failed see directory server authorization"

  • once again yes other dc powered off since has dhcp role on (split pool between two) shouldn't see directory server?
  • why ip address on win7 machine 192.168.198.x when dhcp roles set lease 10.0.0.x addresses?

any feedback @ appreciated , again taking time read :)

when power on win7 machine unable log on user doesn't have profile.  when try create new profile says "there no logon servers available service logon request"
 
have found out if change dns server ip addresses on network card point new servers works (duh), but, , here's question, when decide make these 2 new dcs in production , demote current dcs machines in organization still have ips of old dns servers. have go each machine , change dns ip addresses point new servers?  i'm sure can done in group policy , haven't looked yet how suggest tackle this?


no, should done dhcp server. in dhcp server, can specify dns server clients need resolve dns names. type ip address of new dns server, or type name , click resolve, wizard determine ip address you. can add both of dns servers balance workload.



Windows Server  >  Windows Server General Forum



Comments

Popular posts from this blog

Motherboard replacement

Cannot create Full Text Search catalog after upgrading to V12 - Database is not fully started up or it is not in an ONLINE state

Remote Desktop App - Error 0x207 or 0x607