I’ve done a bunch of NT to SBS2003, SBS03 to 08, etc., not sure if I’m just missing something stupid or what. I have a SBS2003 (all patched) that I’m migrating to a bunch of non-SBS 2008 R2 SP1 servers on Hyper-V. I started looking into AD/DNS when the one Mac can connect fine to the old SBS2003 server (with Mac services) but not the 2008 R2 DC. I then promoted my 2nd 2008 DC, Mac can connect to netlogon share just fine. DCPromo 1st 2008 DC back down, then back up, still same thing (no, I didn’t test file share when it was a member server). Since 2nd DC has been up for a while (almost 24 hours), I figured I would change the DNS settings on it to only point to 127.0.0.1 (instead of also pointing to SBS server), restart times when from roughly 90 seconds to over 5 minutes, network location went from Domain to Public, and I have a bunch of AD & DNS errors, and Windows Firewall on 2008 is off. ASUC won’t come up on 2008 server as it says the domain is unavailable. If I switch the DNS client on the server to just point to SBS and 127.0.0.1 as secondary, all is fine again. But obvioiusly something isn't working.
My process for dcpromo is to just run dcpromo without AD Services or DNS roles installed, at which point DCPromo installs them. I also found TechNet cc708131 that says when running DCPromo, uncheck/clear the DNS Server during DCPromo (same screen as Global Catalog), although I’m not sure why you’d want to do this? Should I let it use the SBS DNS, and then add 2008 DNS later? But nowhere does it state adding DNS. I prefer to have DCPromo install/setup DNS, that way I know I can't screw anything up by doing it manually.
Only thing I can think of is something happened when I ran Forest/Domain prep on SBS, but would 2008 DCPromo bark if it found anything missing/wrong? I reran Forest/Domain prep using R2 SP1 media on the SBS server, but it says they've already been run.