![]() ![]() ![]() Applications that create records about the host should ensure that the cloned computer does not overwrite records about the original host during the cloning process.Ĭloning is a specific deployment capability for only virtualized domain controllers, not a general purpose extension to clone other server roles. ![]() Unlike a rename where the DNS records of the original computer are removed, the original records for the source domain controller remain.ĭuring the cloning process, the new computer is initially running for a brief period of time under the identity of the old computer until the cloning process is initiated and makes the necessary changes. It remains on the network, interacting with clients. From an application vendor's perspective, these are some considerations to take into account when assessing the impact of cloning to your application: The virtualized domain controller cloning process is described in detail in Introduction to Active Directory Domain Services (AD DS) Virtualization (Level 100) and Virtualized Domain Controller Technical Reference (Level 300). Application vendors who have validated that their application works on virtualized domain controllers that have been cloned are encouraged to list the name of the application in the Community Content at the bottom of this topic, along with a link to your organization's web site where users can learn more about the validation. It covers those aspects of the cloning process that interest application vendors and scenarios that may warrant additional testing. This topic explains what application vendors should consider to help ensure their application continues to work as expected after the virtualized domain controller (DC) cloning process completes. Applies to: Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012 ![]()
0 Comments
Leave a Reply. |