| Author |
 Topic  |
|
|
Yogishbv
Welcome Newcomer
India
4 Posts
Status: offline |
 Posted - 06/07/2012 : 02:23:56 AM
|
I have a problem with inconsistency with the Group policy on the DC's running Windows 2008 R2. Have 2 DC's, the problem was few users were getting removed from local admin group on the local servers.We have a restricted groups for providng admin access.When I checked the restricted groups on One DC the users were part of that but on the other DC the users were not part of restricted groups.And the logon server for the machine were the problem was there was the DC were the users were not part of restricted groups.
I Simply added the users on the problamatic DC to the restricted groups, after refreshing GP the problem resolved.
But was not sure what was the eacat problem. Dint find errors in replication either, IS there any thing, I Can check with?
|
Regards
Yogish |
|
|
wkasdo
Administrator
Netherlands
7405 Posts
Status: offline |
Posted - 06/07/2012 : 07:11:03 AM
|
Welcome to the forum!
> When I checked the restricted groups on One DC the users were part of that but on the other DC the users were not part of restricted groups.
If there is an inconsistency between DC's, you have a replication problem, or latency at the very least. OTOH, verifying policies is not as trivial as some people think. Which DC is your PDCe, and how did you verify the policy on the other one? |
Make it as simple as you can, but not simpler -- Albert Einstein |
 |
|
|
Yogishbv
Welcome Newcomer
India
4 Posts
Status: offline |
Posted - 06/11/2012 : 02:01:18 AM
|
Hi
Runned DCdiag on the server were I observed inconsistency and found error with FRS event.Working on this, have any info?
Getting error with event ID 13568
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\Services\NtFrs\Parameters"
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. |
Regards
Yogish |
|
|
|
wkasdo
Administrator
Netherlands
7405 Posts
Status: offline |
Posted - 06/11/2012 : 02:48:21 AM
|
This error means that there were too many changes on the filesystem for FRS to keep up. One of the most common reasons for this is a bad antivirus program.
Do not set the regkey mentioned in that event. It's no longer a best practice. Instead, do the D2 procedure as explained here: http://support.microsoft.com/kb/290762 (non-auth restore). And take a backup first :-) |
Make it as simple as you can, but not simpler -- Albert Einstein |
|
|
|
Yogishbv
Welcome Newcomer
India
4 Posts
Status: offline |
Posted - 06/18/2012 : 07:48:53 AM
|
Hi
Thank you. Sorry for the delay in reply.I will update you.
Regards
Yogish |
Regards
Yogish |
|
|
| |
Topic |
|
Inconsistency with Group policy in DC's -W2K8 R2
