测试环境1. 三台物理机
a) 一台AD 2012 | Svr-0
| Svr-1
| Svr-2
| Svr-3
| 角色
| AD
| HYPERV
| HYPERV
| HYPERV
| IP1
| 192.168.35.100
| 192.168.35.101
| 192.168.35.102
| 192.168.35.103
| IP2
| 192.168.35.120
| 192.168.35.121
| 192.168.35.122
| 192.168.35.123
|
b) 两台HYPERV HOST | VDC1
| VDC2
| IP
| 192.168.35.131
| 192.168.35.132
| 角色
| BDC
| BDC
|
×VDC1已部署,VDC2为本次试验所需创建的VDC
Prepare the environment - Step 1: Validate that the hypervisor supports VM-Generation ID and therefore, cloning
- Step 2: Verify the PDC emulator role is hosted by a domain controller that runs Windows Server 2012 and that it is online and reachable by the cloned domain controller during cloning.
Prepare the source domain controller - Step 3: Authorize the source domain controller for cloning
- Step 4: Remove incompatible services or programs or add them to the CustomDCCloneAllowList.xml file.
- Step 5: Create DCCloneConfig.xml
- Step 6: Take the source domain controller offline
Create the cloned domain controller - Step 7: Copy or export the source VM and add the XML if not already copied
- Step 8: Create a new virtual machine from the copy
- Step 9: Start the new virtual machine to commence cloning
操作过程1. 将VDC1加入克隆域控组
2. 检测源域控不能被克隆的应用或服务,比如ADCS,DHCP,ADLDS。命令:Get-ADDCCloningExcludedApplicationList和默认列表(customdccloneallowlist.xml)内容
这个命令搜索的是HKLM\SOFTWARE\MICROSOFT\WINDOWS\CURRENTVERSION\UNINSTALL
如果输入命令后有返回内容,但是不在默认列表内,克隆可能会失败。也就是说要么出现在默认列表内,要么就删除之,命令不应该返回任何内容。
3. 创建AD配置文件:New-ADDCCloneConfigFile –Static -IPv4Address "192.168.35.132" -IPv4DNSResolver "192.168.35.100" -IPv4SubnetMask "255.255.255.0" -IPv4DefaultGateway "192.168.35.1" -CloneComputerName "vdc2" -SiteName "sitea"。
4. VDC1关机,删除快照,导出
5. 在SVR-2导入后,重命名VDC2,启动
6. 完成后,计算机名等信息已变更
×如果启动后进入恢复目录模式表示克隆域控失败。
结论PDC不能作为源VDC,但是测试应该可行。
克隆方式两种:直接克隆,离线克隆
创建VDC过程相对比较简单,但是这样做的目的是为什么了呢?方便在虚拟化中部署DC吗?还是为了分支机构部署方便?实用性未知。
开始学写BLOG记录
最后附上TECHNET参考
2012 ADDS功能介绍:http://technet.microsoft.com/zh-cn/library/hh831477.aspx
部署教程:http://tehnet.microsoft.com/zh-CN/library/hh831734.aspx
|