Ошибка репликации SYSVOL при присоединении к домену

Question

Ошибка репликации SYSVOL при присоединении к домену

Кажется, я не могу получить папку SYSVOL для репликации. После вступления в мой журнал событий выплевывает следующее.

The DFS Replication service initialized SYSVOL at local path C:\Windows\SYSVOL\domain and is waiting to perform initial replication. The replicated folder will remain in the initial synchronization state until it has replicated with its partner NTE-AUTHSRV.NASUTEK-CORE.nisn.nasutek.com. If the server was in the process of being promoted to a domain controller, the domain controller will not advertize and function as a domain controller until this issue is resolved. This can occur if the specified partner is also in the initial synchronization state, or if sharing violations are encountered on this server or the synchronization partner. If this event occurred during the migration of SYSVOL from File Replication service (FRS) to DFS Replication, changes will not replicate out until this issue is resolved. This can cause the SYSVOL folder on this server to become out of sync with other domain controllers. 

Additional Information: 
Replicated Folder Name: SYSVOL Share 
Replicated Folder ID: 9149BE82-BD4D-42D9-8E6C-C900D799E3E4 
Replication Group Name: Domain System Volume 
Replication Group ID: A9B325AD-85F2-4B0B-BF83-404FF8172FB8 
Member ID: B61BF26F-A357-431F-8AF2-90DB0A844851 
Read-Only: 0

The DFS Replication service failed to update configuration in Active Directory Domain Services. The service will retry this operation periodically. 

Additional Information: 
Object Category: msDFSR-LocalSettings 
Object DN: CN=DFSR-LocalSettings,CN=administrator2,OU=Domain Controllers,DC=NASUTEK-CORE,DC=nisn,DC=nasutek,DC=com 
Error: 2 (The system cannot find the file specified.) 
Domain Controller: NTE-AUTHSRV.NASUTEK-CORE.nisn.nasutek.com 
Polling Cycle: 60

The DFS Replication service has detected that no connections are configured for replication group Domain System Volume. No data is being replicated for this replication group. 

Additional Information: 
Replication Group ID: A9B325AD-85F2-4B0B-BF83-404FF8172FB8 
Member ID: B61BF26F-A357-431F-8AF2-90DB0A844851

Я перепробовал все, что только мог придумать, но этот просто ошеломляет меня.

РЕДАКТИРОВАТЬ: я добавил дополнительную информацию на https://gist.github.com/michael-manley/5343111 для любых других команд, которые я выполнил.

1

active-directory windows-server-2012 dfs-r

Источник

DrHouse 09 апр '13 в 03:13

1 ответ

Решение

Другие вопросы по тегам active-directory windows-server-2012 dfs-r

DrHouse 09 апр '13 в 06:40 2013-04-09 06:40 · Accepted Answer · 2013-04-09 06:40

Я наконец выяснил, проблема была на PDC. Я нашел эту запись в журналах DFSR

The DFS Replication service stopped replication on volume C:. This occurs when a DFSR JET database is not shut down cleanly and Auto Recovery is disabled. To resolve this issue, back up the files in the affected replicated folders, and then use the ResumeReplication WMI method to resume replication. 

Additional Information: 
Volume: C: 
GUID: 89131A39-4A90-11E2-93EB-806E6F6E6963 

Recovery Steps 
1. Back up the files in all replicated folders on the volume. Failure to do so may result in data loss due to unexpected conflict resolution during the recovery of the replicated folders. 
2. To resume the replication for this volume, use the WMI method ResumeReplication of the DfsrVolumeConfig class. For example, from an elevated command prompt, type the following command: 
wmic /namespace:\\root\microsoftdfs path dfsrVolumeConfig where volumeGuid="89131A39-4A90-11E2-93EB-806E6F6E6963" call ResumeReplication 

For more information, see http://support.microsoft.com/kb/2663685.

Я запустил команду, перезапустил DFSR, и репликация наконец началась.