marqueslc
asked on
Sysvol not replicating from 2003 DC to 2008 DC - FRS issue.
Hi all.
I am adding my first server 2003 STD edt. to an existing domain. I am hoping to allow AD replicate to the new 2008 server and then decommission the server 2003 DC.
The server 2003 is not a R2 server, therefore does not even know about DFS but I have noticed that server 2008 no longer uses FRS to replicate the sysvol folder between servers. My new 2008 server does not have any of the logon scripts etc in it as my 2003 server does.
I have looked around on the net but can not seem to find out whether or not there is a way around this issue.
Anyones assistance would be greatly appreciated!
I am adding my first server 2003 STD edt. to an existing domain. I am hoping to allow AD replicate to the new 2008 server and then decommission the server 2003 DC.
The server 2003 is not a R2 server, therefore does not even know about DFS but I have noticed that server 2008 no longer uses FRS to replicate the sysvol folder between servers. My new 2008 server does not have any of the logon scripts etc in it as my 2003 server does.
I have looked around on the net but can not seem to find out whether or not there is a way around this issue.
Anyones assistance would be greatly appreciated!
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
Rajith Enchiparambil
If your domain is in the Server 2008 domain functional level (meaning all domain controllersDCsare running Server 2008), the system uses DFSR for SYSVOL replication. If the domain isnt in Server 2008 domain mode, there might be non-Server 2008 DCs, which means a server could replicate with a server that doesnt support DFSR. Therefore, the system uses FRS on all DCs.
ASKER
Hi there.
Thanks for your assistance thus far.
I double checked the firewall, but this was already disabled since i dcpromo-ed the 2008 server.
I did notice the ntFRS errors on the 2008 dc saying that it couldn't replicate with the 2003 DC and then found the option to enable FRS on the 2008 dc. after enabling FRS and then manually forcing a replication between the servers, there were no errors reported from the forced replication, but I am still not receiving the Netlogon share / logon bat files on my 2008 server. Perhaps server 2008 no longer uses the "netlogn" share, Im not entirely sure, but then what other alternative would server 2008 be using?
The error received regarding the failed ntfrs replications are as follows:
Log Name: File Replication Service
Source: NtFrs
Date: 22/07/2008 10:25:29
Event ID: 13508
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: BCS2K801.bcs.local
Description:
The File Replication Service is having trouble enabling replication from BCS-PDC to BCS2K801 for c:\windows\sysvol\domain using the DNS name BCS-PDC.bcs.local. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name BCS-PDC.bcs.local from this computer.
[2] FRS is not running on BCS-PDC.bcs.local.
[3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
Event Xml:
13508
3
0
0x80000000000000
16
File Replication Service
BCS2K801.bcs.local
BCS-PDC
BCS2K801
c:\windows\sysvol\domain
BCS-PDC.bcs.local
D5040000
Thanks for your assistance thus far.
I double checked the firewall, but this was already disabled since i dcpromo-ed the 2008 server.
I did notice the ntFRS errors on the 2008 dc saying that it couldn't replicate with the 2003 DC and then found the option to enable FRS on the 2008 dc. after enabling FRS and then manually forcing a replication between the servers, there were no errors reported from the forced replication, but I am still not receiving the Netlogon share / logon bat files on my 2008 server. Perhaps server 2008 no longer uses the "netlogn" share, Im not entirely sure, but then what other alternative would server 2008 be using?
The error received regarding the failed ntfrs replications are as follows:
Log Name: File Replication Service
Source: NtFrs
Date: 22/07/2008 10:25:29
Event ID: 13508
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: BCS2K801.bcs.local
Description:
The File Replication Service is having trouble enabling replication from BCS-PDC to BCS2K801 for c:\windows\sysvol\domain using the DNS name BCS-PDC.bcs.local. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name BCS-PDC.bcs.local from this computer.
[2] FRS is not running on BCS-PDC.bcs.local.
[3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
Event Xml:
13508
3
0
0x80000000000000
16
File Replication Service
BCS2K801.bcs.local
BCS-PDC
BCS2K801
c:\windows\sysvol\domain
BCS-PDC.bcs.local
D5040000
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
Hi lads.
Thanks for your input. You both have contributed to me finding the solution so have split the points according to how each one contributed to the solution.
It was a couple of things;
1. the frs service on 2008 dc had to be enabled. Had also noticed that the firewall had randomly at times activated itself again but has n't happened since...
2. Discovered that ntfrs serive on 2003 service was causing replication failure. resolved this with registry fix and then HAPPY DAYS!!
Again, thanks for pointing me in the right direction.
Thanks for your input. You both have contributed to me finding the solution so have split the points according to how each one contributed to the solution.
It was a couple of things;
1. the frs service on 2008 dc had to be enabled. Had also noticed that the firewall had randomly at times activated itself again but has n't happened since...
2. Discovered that ntfrs serive on 2003 service was causing replication failure. resolved this with registry fix and then HAPPY DAYS!!
Again, thanks for pointing me in the right direction.