在将Windows 2003域控升级到Windows Server 2008 R2域控的过程中,升级SYSVO的复制方式是很容易被忽略的事情,我是在做文件服务器规划的时候,看到了相关信息:升级后的域控之间的复制仍然是使用FRS复制(FRS应该在Windows Server 2000时代,DFS出现在windows Server 2003 R2时代,二者的详细信息建议看看微软的官方文档),虽然FRS可以很好的完成AD数据的同步,但是有好东西为什么不用,何况公司现在的域控数量正在快速增长,拓扑复杂,DFS应该可以很好的减轻网络负载,所以宜早不宜迟。
升级前,请务必了解升级的原理、回滚的机制、异常处理方法,最好在试验环境熟练这些操作,以下文档可以非常好的帮助我们理解和指导升级:
SYSVOL Migration Series:
SYSVOL Replication Migration Guide: FRS to DFS Replication 下载地址:
上面2个链接在technet library中的这个链接都可以找到:
http://technet.microsoft.com/en-us/library/dd640019(WS.10).aspx
FRS升级到DFS大致分为四个状态(其中中间的2个状态DFS和FRS并行存在),以上三个连接都很清楚的说明了,摘抄下:
‘START’ state: In this state, FRS is responsible for replicating the contents of the SYSVOL share between domain controllers. The main replication engine for the SYSVOL share on each of the domain controllers in the domain is FRS.
‘PREPARED’ state: In the ‘PREPARED’ state, the DFS Replication service makes a copy of the contents of the SYSVOL share for itself. It then proceeds to initiate replication of its copy of the SYSVOL folder with the DFS Replication service running on other peer domain controllers which have migrated to the ‘PREPARED’ state. At this stage of the migration process, the main replication engine for the SYSVOL share on each of the domain controllers in the domain is still FRS.
‘REDIRECTED’ state: In the ‘REDIRECTED’ state, the replication responsibility is shifted to the DFS Replication service. The copy of the SYSVOL folder which was being replicated by the DFS Replication service is now the one that is shared out by the Netlogon service and advertized by the domain controller. FRS is, in the meantime, replicating the old SYSVOL folder with the FRS service running on other peer domain controllers. At this stage of the migration process, the main replication engine for each of the domain controllers in the domain is the DFS Replication service.
’ELIMINATED’ state: In the ‘ELIMINATED’ state, once the domain administrator has ensured that replication is working fine, the FRS service is retired and the DFS Replication service assumes sole responsibility for replicating the contents of the SYSVOL share between all domain controllers in that domain.
以下是对几十台域控升级过程的一些经验:
1、域和林架构都升到windows Server 2008 R2;
2、确保所有域控在线(虽然不在线的可以单独升级,但是增加复杂度……),最好在PDC进行所有操作,PDC可以链接到所有域控,使用以下命令检查域控在线和复制情况:
Repadmin.exe /replsummary * /bysrc /bydest /sort:failures
或者
repadmin /ReplSum
3、运行以下命令将域控复制状态从START变更为PREPARED:
dfsrmig /SetGlobalState 1
4、运行以下命令检查所有域控迁移状态是否全部变更:
dfsrmig /getglobalstate
dfsrmig /GetMigrationState
这一步需要耐性等待,个把小时是正常的,可以每隔15分钟重复运行以上命令查看状态,另外看看仍然没有变更过来的域控中的DFS相关日志,有些分站点域控其实已经变更了,但是在PDC运行命令检查的时候,状态信息并没有即时的复制过来,谨慎起见,还是等待,知道没有一个域控返回不正常状态,然后执行下一步;
5、运行以下命令将域控复制状态从PREPARED变更为REDIRECTED:
dfsrmig /SetGlobalState 2
6、运行以下命令检查所有域控迁移状态是否全部变更:
dfsrmig /getglobalstate
dfsrmig /GetMigrationState
耐心,同上。。。。
7、运行以下命令将域控复制状态从REDIRECTED变更为ELIMINATED:
dfsrmig /SetGlobalState 3
谨慎操作,执行该命令后,FRS将成为历史,不像之前的操作,此操作将不可逆!
8、运行以下命令检查所有域控迁移状态是否全部变更:
dfsrmig /getglobalstate
dfsrmig /GetMigrationState
耐心,同上。。。。
完成后,会发现FRS文件复制服务停止了,DFS处于运行状态。
升级很顺利,就是时间比较长,2个小时吧。
Good Luck!