I'm a bit confused on why it appears that all of the components to make WMS 2012 into an Active Domain Controller seem to exist, but that the wizard always fails to complete with any clear error messages.
The ability for it to be its own DC would be very handy, especially given that VM-based desktop and Session-based desktop deployment require that the server be connected to an AD before they can be implemented.
Bottom line, is intentionally DC ability is crippled in this OS or whether the wizard is just "buggy"?
Thanks,
Shawn