ThirdEyeTech
asked on
Sysvol & netlogon not sharing on new Windows 2008 r2 DC
Recently we installed a new Windows 2008 r2 DC into our existing 2003 domain. Everything appeared fine and working, until we tried to access the sysvol and saw the share was missing. At this point the FSMO roles have been transferred to the new server, but we are having problems with GPOs. We need to get this corrected before the old w2k3 server is removed from the environment.
Any help is greatly appreciated.
We performed the following steps:
1. Ran 2008R2 adprep /forestprep, adprep /domainprep, and adprep /domainprep /gpprep
2. Added the Active Directory Services to the new Windows 2008 r2 server
3. Ran DCPROMO and rebooted
4. Changed the IP scheme of both servers keeping everything connected during the process
5. Allowed the servers to communicate for 72 hours to get replication working
6. Transferred the FSMO roles to the new Windows 2008 R2 server
Now we have no netlogon or sysvol shares on the new w2k8dc.
Additional background:
- Flat domain with only 10 devices will only have 1 server to perform basic file services.
- Windows 2008 r2 has the following roles installed: DNS, DHCP, File services, Print services, Network Policy and Access Services.
I have attached dcdiag, netdiag and ntfrsutl sets from both servers
W2K3_DC
DCDIAG
w2k3dc-dcdiag-verbose.txt
NETDIAG
w2k3dc-netdiag.txt
NTFRSUTL SETS
w2k3dc-ntfrsutl.txt
Repadmin
w2k3dc-repl.txt
W2K8DC
DCDIAG
w2k8dc-dcdiag-verbose.txt
NTFRSUTL SETS
w2k8dc-ntfrsutl.txt
Repadmin
w2k8dc-repl.txt
Any help is greatly appreciated.
We performed the following steps:
1. Ran 2008R2 adprep /forestprep, adprep /domainprep, and adprep /domainprep /gpprep
2. Added the Active Directory Services to the new Windows 2008 r2 server
3. Ran DCPROMO and rebooted
4. Changed the IP scheme of both servers keeping everything connected during the process
5. Allowed the servers to communicate for 72 hours to get replication working
6. Transferred the FSMO roles to the new Windows 2008 R2 server
Now we have no netlogon or sysvol shares on the new w2k8dc.
Additional background:
- Flat domain with only 10 devices will only have 1 server to perform basic file services.
- Windows 2008 r2 has the following roles installed: DNS, DHCP, File services, Print services, Network Policy and Access Services.
I have attached dcdiag, netdiag and ntfrsutl sets from both servers
W2K3_DC
DCDIAG
w2k3dc-dcdiag-verbose.txt
NETDIAG
w2k3dc-netdiag.txt
NTFRSUTL SETS
w2k3dc-ntfrsutl.txt
Repadmin
w2k3dc-repl.txt
W2K8DC
DCDIAG
w2k8dc-dcdiag-verbose.txt
NTFRSUTL SETS
w2k8dc-ntfrsutl.txt
Repadmin
w2k8dc-repl.txt
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Vinchenzo,
I did what you suggested and these are the errors I received:
W2K3DC
Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13568
Date: 6/28/2011
Time: 3:59:11 PM
User: N/A
Computer: FTSERVER-2423
Description:
The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.
Replica set name is : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
Replica root path is : "c:\windows\sysvol\domain"
Replica root volume is : "\\.\C:"
A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found. This can occur because of one of the following reasons.
[1] Volume "\\.\C:" has been formatted.
[2] The NTFS USN journal on volume "\\.\C:" has been deleted.
[3] The NTFS USN journal on volume "\\.\C:" has been truncated. Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal.
[4] File Replication Service was not running on this computer for a long time.
[5] File Replication Service could not keep up with the rate of Disk IO activity on "\\.\C:".
Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1 will cause the following recovery steps to be taken to automatically recover from this error state.
[1] At the first poll, which will occur in 5 minutes, this computer will be deleted from the replica set. If you do not want to wait 5 minutes, then run "net stop ntfrs" followed by "net start ntfrs" to restart the File Replication Service.
[2] At the poll following the deletion this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set.
WARNING: During the recovery process data in the replica tree may be unavailable. You should reset the registry parameter described above to 0 to prevent automatic recovery from making the data unexpectedly unavailable if this error condition occurs again.
To change this registry parameter, run regedit.
Click on Start, Run and type regedit.
Expand HKEY_LOCAL_MACHINE.
Click down the key path:
"System\CurrentControlSet\
Double click on the value name
"Enable Journal Wrap Automatic Restore"
and update the value.
If the value name is not present you may add it with the New->DWORD Value function under the Edit Menu item. Type the value name exactly as shown above.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
**************************
W2K8DC
Log Name: File Replication Service
Source: NtFrs
Date: 6/28/2011 4:00:57 PM
Event ID: 13566
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: FT-SRV-21798.FT.local
Description:
File Replication Service is scanning the data in the system volume. Computer FT-SRV-21798 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 scanning 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.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="NtFrs" />
<EventID Qualifiers="32768">13566</
<Level>3</Level>
<Task>0</Task>
<Keywords>0x80000000000000
<TimeCreated SystemTime="2011-06-28T20:
<EventRecordID>22</EventRe
<Channel>File Replication Service</Channel>
<Computer>FT-SRV-21798.FT.
<Security />
</System>
<EventData>
<Data>FT-SRV-21798</Data>
</EventData>
</Event>
I did what you suggested and these are the errors I received:
W2K3DC
Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13568
Date: 6/28/2011
Time: 3:59:11 PM
User: N/A
Computer: FTSERVER-2423
Description:
The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.
Replica set name is : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
Replica root path is : "c:\windows\sysvol\domain"
Replica root volume is : "\\.\C:"
A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found. This can occur because of one of the following reasons.
[1] Volume "\\.\C:" has been formatted.
[2] The NTFS USN journal on volume "\\.\C:" has been deleted.
[3] The NTFS USN journal on volume "\\.\C:" has been truncated. Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal.
[4] File Replication Service was not running on this computer for a long time.
[5] File Replication Service could not keep up with the rate of Disk IO activity on "\\.\C:".
Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1 will cause the following recovery steps to be taken to automatically recover from this error state.
[1] At the first poll, which will occur in 5 minutes, this computer will be deleted from the replica set. If you do not want to wait 5 minutes, then run "net stop ntfrs" followed by "net start ntfrs" to restart the File Replication Service.
[2] At the poll following the deletion this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set.
WARNING: During the recovery process data in the replica tree may be unavailable. You should reset the registry parameter described above to 0 to prevent automatic recovery from making the data unexpectedly unavailable if this error condition occurs again.
To change this registry parameter, run regedit.
Click on Start, Run and type regedit.
Expand HKEY_LOCAL_MACHINE.
Click down the key path:
"System\CurrentControlSet\
Double click on the value name
"Enable Journal Wrap Automatic Restore"
and update the value.
If the value name is not present you may add it with the New->DWORD Value function under the Edit Menu item. Type the value name exactly as shown above.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
**************************
W2K8DC
Log Name: File Replication Service
Source: NtFrs
Date: 6/28/2011 4:00:57 PM
Event ID: 13566
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: FT-SRV-21798.FT.local
Description:
File Replication Service is scanning the data in the system volume. Computer FT-SRV-21798 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 scanning 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.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="NtFrs" />
<EventID Qualifiers="32768">13566</
<Level>3</Level>
<Task>0</Task>
<Keywords>0x80000000000000
<TimeCreated SystemTime="2011-06-28T20:
<EventRecordID>22</EventRe
<Channel>File Replication Service</Channel>
<Computer>FT-SRV-21798.FT.
<Security />
</System>
<EventData>
<Data>FT-SRV-21798</Data>
</EventData>
</Event>
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Pbrane,
Yes NtFRS is enabled on both boxes. As for copying the sysvol do you mean just literally copy and paste or is there a specific command I need to execute?
Thanks
Yes NtFRS is enabled on both boxes. As for copying the sysvol do you mean just literally copy and paste or is there a specific command I need to execute?
Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
pbrane,
Followed steps and they worked. How should I proceed with the w2k8 box? D2?
Thanks
Followed steps and they worked. How should I proceed with the w2k8 box? D2?
Thanks
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Before you change anything make a copy from the sysvol folder.
After that you may try the options available in this blog: http://blog.ronnypot.nl/?p=738
After that you may try the options available in this blog: http://blog.ronnypot.nl/?p=738
ASKER
pbrane,
Thank you for all your help. Your steps worked perfectly. I award you all the points. Thanks!
Thank you for all your help. Your steps worked perfectly. I award you all the points. Thanks!
Good news,
You're welcome!
Thanks,
You're welcome!
Thanks,
Stop the frs service
Stop netlogon service
Restart both services
Check to see if its sharing? If not what errors are you getting in the event logs.