I have a Windows SBS 2003 Domain which I am attempting to migrate to Windows Server 2008. I am not using the transition pack, as I have already purchased two separate new boxes with Server 2008 licenses and do not wish to use the old SBS hardware (VLS-SERVER) in the new domain. I have dcpromo'd my new domain controller (VLS-DOMCON1) and succesfully joined the domain. AD replication is successful between the two domain controllers. I am aware of the time constraints with having two domain controllers on a SBS domain and need to get this resolved in the next 4 days.
The current problem is that I do not have a Sysvol and netlogon share on my new domain controller (VLS-DOMCON1). I read through several threads on this subject and started by looking the File Replication Service logs on VLS-DOMCON1.
Here's the details of the error that I've been seeing:
Log Name: File Replication Service
Date: 10/20/2008 12:59:46 PM
Event ID: 13508
Task Category: None
The File Replication Service is having trouble enabling replication from VLS-SERVER to VLS-DOMCON1 for c:\windows\sysvol\domain using the DNS name vls-server.Vincentlimousin
es.local. FRS will keep retrying.
Following are some of the reasons you would see this warning.
 FRS can not correctly resolve the DNS name vls-server.Vincentlimousin
es.local from this computer.
 FRS is not running on vls-server.Vincentlimousin
 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.
<Provider Name="NtFrs" />
<Channel>File Replication Service</Channel>
I was able to resolve the name of VLS-SERVER.vincentlimousin
es.local from this machine succesfully. I also checked that FRS was running on VLS-SERVER.
I saw a thread about Journal Wrap Errors, but I didn't see any in the event log for VLS-DOMCON1. When I looked at the file replication service event log for VLS-SERVER, I saw many Journal Wrap Errors.
I resolved the journal wrap error by adding a DWORD for Enable Journal Wrap Automatic Restore in HKEY_LOCAL_MACHINE\SYSTEM\
ers. I then stopped and started the File Replication Service on VLS-SERVER. I didn't get any more journal wrap errors, but I'm still getting the Cannot replicate (check DNS, replication topology, etc) message on VLS-SERVER and am getting the same message on VLS-DOMCON1,
The last item that I will put out is that my windows directory is on the E: drive on VLS-SERVER but it is on the C: directory on VLS-DOMCON1. I don't think this would make a difference, but wanted to make sure that the information is out there.
I appreciate any help that is offered in solving this problem