4

I finally went through with this the other day. Got DNS/AD setup, seized FSMO roles on the 2012 server, migrated DHCP etc. I thought I was ready to go so I turned off the 2008 server yesterday. Everything worked fine for a few hrs, then network drives started breaking and a couple of apps broke that must somehow be pointed to the 2008 server for DNS. I initially ignored a WINS migration because I thought that was more or less a legacy service for older versions of Windows. I'm kind of scratching my head on this, any help is appreciated.

edit I've since turned the old DC on to keep things from breaking.

Mike Hawk
  • 41
  • 2
  • 1
    Did you update all of the domain clients to use the new DC for DNS? Aside from that, it could literally be anything. Look at the event logs, run DCDIAG, run the relevant BPA's, etc., etc. – joeqwerty Nov 28 '18 at 19:10
  • If you have shortcuts or printers with the previous server name, it may be possible to create a DNS CNAME for the previous server that points to the new server. – Greg Askew Nov 28 '18 at 21:01
  • Although WINS is legacy, that doesn't necessarily mean you're not unknowingly depending on it if your DNS isn't comprehensive. Typically I think it would be preferable to identify and correct any problems with the DNS than to just keep using WINS, but I suppose it depends on the scenario. – Harry Johnston Nov 28 '18 at 21:19
  • Assuming the IP address of the new DC is different than the IP of the old DC, you need to make sure all your clients have obtained the new IP address for the DNS server. DHCP should be updated to hand out the new DNS IP address. Make sure you haven’t mistakingly set the clients to use your modem or ISP for DNS. – Appleoddity Nov 29 '18 at 06:04

1 Answers1

0

It sounds like you have your answer already:

Everything worked fine for a few hrs, then network drives started breaking and a couple of apps broke that must somehow be pointed to the 2008 server for DNS.

Are you running DNS on the new server, and are your clients pointing to it?

Did you forget to authorize the new DHCP server? Update the DHCP server with the new IP address of the new server for DNS?

J. DuBois
  • 41
  • 2