File shares and AD/DNS were moved onto a single physical Dell Poweredge, and we also happened to spin up a production Hyper-V server running Server 2012 for the purposes of Remote Desktop Services.
By the way, if you are curious, Hyper-V 2012 is working great for us. So it was a Mission Accomplished on the server consolidation and virtualization front.
As it happens, I recently needed just such a configuration myself so thought I'd share how I did it...
Talk about a hellhole of issues we were running into.The basic crux of the issue is that MS DNS uses Kerberos for authentication to update DNS records, while ISC DHCP, out of the box, supports TSIG [for BIND].The scripts above are rather lengthy, so I won't post them here, but the basic steps are: Generate a keytab using ktutil.The fix is easy: you just need to create a DHCP Service Account add it to the DNS Update Proxy group.Then enter the credentials in the property tab of the DHCP server.