I am as a Premier Field Engineering supporting Windows Server and Active Directory with an emphasis on OS performance.
Follow Me and Learn 2012 Index or Windows 2012 Core Survival Guide Index
Hello, Bruce here again. With the release Windows Server 2012 we all have to start learning the new features of the product. So I thought I would share with you what I’m studying tonight and some resource to bring you to speed at the same time. Below is the second topic I’m starting to look at.
Rapid deployment with cloning
AD DS in Windows Server 2012 allows you to deploy replica virtual domain controllers by “cloning” existing virtual domain controllers. You can promote a single virtual domain controller by using the domain controller promotion interface in Server Manager, and then rapidly deploy additional virtual domain controllers within the same domain, through cloning.
The process of cloning involves creating a copy of an existing virtual domain controller, authorizing the source domain controller to be cloned in AD DS, and running Windows PowerShell cmdlets to create a configuration file that contains detailed promotion instructions (name, IP address, Domain Name System [DNS] servers, and so on). Or you can leave the configuration file empty, which allows the system to automatically fill in the information. Cloning reduces the number of steps and time involved by eliminating repetitive deployment tasks, and it enables you to fully deploy additional domain controllers that are authorized and configured for cloning by the Active Directory domain administrator. http://technet.microsoft.com/en-us/library/hh831477.aspx#BKMK_VirtualizationJustWorks
Introduction to Active Directory Domain Services (AD DS) Virtualization
Steps for deploying a clone virtualized domain controller
Active Directory Virtualization Safeguards and Domain Controller Cloning with Windows Server 2012
New features in Active Directory Domain Services in Windows Server 2012, Part 13: Domain Controller Cloning
How does Windows Server 2012 Cloning of a DC handle windows patches?
Can you "slipstream" or "update" the base template with the Windows Updates?
Or do you have to deploy the DC, then patch it?
The clone will be at what ever patch level the ordinal box was at. Are you asking how to keep your copy of the patched?
Yes, it would be helpful to know how to keep the image up to date without creating a new.