Ramblings from another nerd on the grid
Upgrading your network operating system requires minimal network configuration and typically has a low impact on user operations. The upgrade process is straightforward, efficient, and allows your organization to take advantage of the improved security that is offered by the Windows Server® 2008 and Windows Server 2008 R2 operating systems.
This guide is intended for use by system administrators and system engineers. It provides detailed guidance for upgrading Windows 2000 or Windows Server 2003 Active Directory domains to Active Directory Domain Services (AD DS) domains that have domain controllers running Windows Server 2008 or Windows Server 2008 R2. For a seamless deployment experience, use the checklists that are provided in this guide and complete the tasks in the order in which they are presented.
Go get the guide @ http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=fa629de2-f4dd-47ac-8d80-3db46b2877a2.
Running in a DC in Hyper-V
If you plan to run a Windows Server 2008 Domain Controller as a Hyper-V virtual machine, you should also download and review the latest guide on that as well. This guide discusses many of the important considerations that are specific to the deployment of a Windows Server 2003 and Windows Server 2008 virtual domain controller. It provides recommendations and tips to help you deploy and manage domain controllers in Hyper-V.
Some of the Hyper-V issues, such as storage and backup, that are not specific to domain controllers are not covered in this guide. This guide also does not address the potential cost savings of migration to virtual servers. Furthermore, because the process of making a virtual server a domain controller does not differ from the process of making a physical server a domain controller, this process (domain controller promotion) is not described in this guide.
Go get it @ http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=7425e34b-3990-43d8-b93b-cb6442858c21.
We run a few DC's in Hyper-V.
I couldn't get Time Synch to turn off in the integration services, since thats a no-no with DCs in hyper-v.
Finally I realized that the VM has to be shutdown to disable the feature. Doh!