Quantcast
Channel: Directory Services forum
Viewing all articles
Browse latest Browse all 31638

Replication isssue - Sysvol not replicationing "after" 2008 Schema upgrade

$
0
0


Hi-

We are having issues with one of our DC's - after a recent Schema upgrade to 2008.


1. Started out by running this:

E:\support\adprep>adprep32.exe /forestprep

--> Adprep successfully updated the forest-wide information.

 

2.

After running "C:\Software\AD\adprep>adprep32.exe /rodcprep"...

Adprep completed with errors. Not all partitions are updated. See the ADPrep.log in the C:\WINDOWS\debug\adprep\logs\20121024191148 directory for more information.

To successfully update all partititions, the current logged on user needs to be
a member of Enterprise Admins group.  If that is not the case, please correct the problem, and then restart Adprep.

--> We thought we were going to add RODC to our environment later - but, then decided to ignore these errors move on...

3.

Lastly - run on domain and GP...

E:\support\adprep>adprep32 /domainprep /gpprep
Running domainprep ...

Adprep successfully updated the domain-wide information.

Adprep successfully updated the Group Policy Object (GPO) information.

 

4.

Our problem DC:

C:\>dcdiag /q
         Unable to connect to the NETLOGON share! (\\server\netlogon)
         [DC] An net use or LsaPolicy operation failed with error 1203, No ne
twork provider accepted the given network path..
         ......................... DC failed test NetLogons
         Warning: DsGetDcName returned information for \\server.Auxiant.local,
when we were trying to reach DC.
         Server is not responding or is not considered suitable.
         ......................... DC failed test Advertising
         There are warning or error events within the last 24 hours after the
         SYSVOL has been shared.  Failing SYSVOL replication problems may cause
         Group Policy problems.
         ......................... DC failed test frsevent

 

5.

We tried using these steps - maybe we did not wait long enough?

-Stop the File Replication Service on the failing DC
-Set the "BurFlags" Value in the following registry key to "D2"(DWORD):
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup

-Start the File Replication Service.

After that the Sysvol Folder should be reinitialized with the contents of the other DC's.

Then we set the value back to 0 and restarted again since we did nto see results.

 

6.

And we have run this command but are not sure if we can interpret all the info:

repadmin /showrepl /all /verbose

7.

Our Event logs show this last mesg for NTFRS...

Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13565
Date:  10/24/2012
Time:  7:51:46 PM
User:  N/A
Computer: DC
Description:
File Replication Service is initializing the system volume with data from another domain controller. Computer DC cannot become a domain controller until this process is complete. The system volume will then be shared as SYSVOL.
 
To check for the SYSVOL share, at the command prompt, type:
net share
 
When File Replication Service completes the initialization process, the SYSVOL share will appear.
 
The initialization of the system volume can take some time. The time is dependent on the amount of data in the system volume, the availability of other domain controllers, and the replication interval between domain controllers.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

 

Can anyone help or should we just wait?

Thanks much.

 

-P

 


Viewing all articles
Browse latest Browse all 31638

Latest Images

Trending Articles





Latest Images