We help IT Professionals succeed at work.

GPO will not apply policy to local workstation

I am having some issues applying a GPO to my workstations.   I am currently in the process trying to setup a GPO to push a security group with 2 domain logins associated with that group to apply local administrator access to any machine on this current domain.   Below is the link I am using.

https://richardstk.com/2013/11/26/adding-domain-users-to-the-local-administrators-group-using-group-policy/

I am attempting to use option 2 to ensure any local admins that are current on the workstation machine are not removed.  

I created the policy and applied the policy to the workstations group in GPM and enforced the policy.   (GPO Setup.jpg) Attached.  

However after running a gpupdate /force I am experiencing the following error on the workstation.


C:\Users\testgpo>gpupdate /force
Updating policy...

Computer policy could not be updated successfully. The following errors were encountered:

The processing of Group Policy failed. Windows attempted to read the file \\ecva2.local\SysVol\ecva2.local\Policies\{56134950-09B3-4597-950F-26CF3ED660BA}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
a) Name Resolution/Network Connectivity to the current domain controller.
b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller).
c) The Distributed File System (DFS) client has been disabled.
User Policy could not be updated successfully. The following errors were encountered:

The processing of Group Policy failed. Windows attempted to read the file \\ecva2.local\SysVol\ecva2.local\Policies\{341E2438-DF51-484F-B045-A8BED0538FD7}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
a) Name Resolution/Network Connectivity to the current domain controller.
b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller).
c) The Distributed File System (DFS) client has been disabled.

To diagnose the failure, review the event log or run GPRESULT /H GPReport.html from the command line to access information about Group Policy results.

C:\Users\testgpo>

I created a GPO Policy results log and was unable to see my Policy I setup in applied or Denied GPO

Applied GPOshide
Name Link Location Revision
Local Group Policy Local AD (1), Sysvol (1)
TREND MICRO SA INSTALLER ecva2.local AD (2), Sysvol (2)
Disable Server Manager at Start ecva2.local AD (1), Sysvol (1)
Paychex trusted sites ecva2.local AD (10), Sysvol (10)
My Virtual Merchant IE settings ecva2.local AD (22), Sysvol (22)
Homepage ecva2.local AD (1), Sysvol (1)
DP Workstation Policy ecva2.local AD (147), Sysvol (147)
Default Domain Policy ecva2.local AD (427), Sysvol (427)
Passwords ecva2.local AD (14), Sysvol (14)

Denied GPOshide
Name Link Location Reason Denied
{35DC6AA3-1646-46D2-A55E-726654C76F08} ecva2.local Inaccessible
{3C6EBF5B-0547-48AA-90CD-CF40B1705DD0} ecva2.local Inaccessible
{F8E984D3-4761-41F2-BD63-1140181D55B0} ecva2.local Inaccessible
{82D58C3B-C670-484D-9681-F90ACC99274E} ecva2.local Inaccessible
{322E4805-1398-4405-A1A0-2C4838ADE889} ecva2.local Inaccessible
{5AE0ABD2-207D-4199-8168-098856D859BA} ecva2.local Inaccessible
{2C22853C-9139-449F-923A-77AEAEADAEAB} ecva2.local Inaccessible

I have the policy enforced.

My boss seems to think there is a replication issue somewhere.   I have no clue from here where to look.   Can someone assist?  The workstation is running Windows 10 Pro and getting policies from Windows server 2008.   This is a request from the CEO so this is high priority.
GPO-Setup.JPG
Comment
Watch Question

You may want to try the methods here to troubleshoot your issue. Also note the comment in the end of tutorial.
https://theitbros.com/the-processing-of-group-policy-failed-windows-attempted-to-read-the-file/
Andrew N. KowtaloSupport Center Engineer

Author

Commented:

Got to the part after I stopped and restarted the NTFR and got this error.



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.

- System

  - Provider

   [ Name]  NtFrs
 
  - EventID 13568

   [ Qualifiers]  49152
 
   Level 2
 
   Task 0
 
   Keywords 0x80000000000000
 
  - TimeCreated

   [ SystemTime]  2020-01-29T21:51:11.000Z
 
   EventRecordID 1925
 
   Channel File Replication Service
 
   Computer VISIONDC2.ecva2.local
 
   Security
 

- EventData

   DOMAIN SYSTEM VOLUME (SYSVOL SHARE)
   c:\windows\sysvol\domain
   \\.\C:
   5

I would start with chkdsk then. Try again after it's done.
David Johnson, CDSimple Geek from the '70s
Distinguished Expert 2019

Commented:

You have to determine which has the good copy and which has the bad copy.

  1. TL;DR

  2. For an Authoritative Restore you must stop the NTFRS services on all of your DCs
  3. In the registry location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process
    1. Set the BurFlags setting to HEX “D4” on a known DC that has a good SYSVOL (or at this time restore SYSVOL data from backup then set the Burflag to D4)
    2. Then start NTFRS on this  server.
    3. You may want to rename the old folders with .old extensions prior to restoring good data.
  4. Clean up the folders on all the remaining servers (Policies, Scripts, etc) – renamed them with .old extensions.
  5. Set the BurFlags to D2 on all remaining servers and then start NTFRS.
  6. Wait for FRS to replicate.
  7. Clean up the .old stuff if things look good.
  8. If the “D4” won’t solve the problem try the “D2” value.

Read the full article 

https://blogs.msmvps.com/acefekay/2013/08/28/how-to-recover-a-journal-wrap-error-jrnl_wrap_error-and-a-corrupted-sysvol-from-a-good-dc-what-option-do-i-use-d4-or-d2-whats-the-difference-between-d4-and-d2/

Distinguished Expert 2019

Commented:
HDavid provided the fix, but the error also includes directions for the fix.

What is your environment has, you should look at transitioning the sysvol from FRS to dfs-r
D2/D4 deals whether it is the authoritative or not reference.
Make sure backups.
Not e if you use the wrong, it will merely move the existing data into the preexisting folder within sysvol.
Andrew N. KowtaloSupport Center Engineer

Author

Commented:

PDC is running Server 2008 so is the BDC.


How do I determine which sysvol is bad?  


Arnold please forgive me I could not understand what you were saying.

Distinguished Expert 2019

Commented:
I was reinforcing the reference David provide which is how to resolve  the issue you have.

The next step is to convert which replication technology is used.

Note the guidance in David's writeup.
You have two DCs the fix needs to be applied on the one with the error.
Andrew N. KowtaloSupport Center Engineer

Author

Commented:

I am reading this article and I am having trouble understanding what its saying.   I am still unable to determine which of the 2 DC's in place has the corrupt SYSVOL, I am assuming its the Primary.   

Andrew N. KowtaloSupport Center Engineer

Author

Commented:

Also this is in the middle of the workday.  Do you suggest this be done after hours?  And will the server require a reboot?

Distinguished Expert 2019

Commented:
The issue is as follows one system has the event reflecting frs issue
The registry edit directe the system when frs is restarted to reinitialize the db.
When there are more than one DC you have to designate the server with the accurate data. D4, the other are D2 meaning the data from sysvol on the system classified as the reference using D4 will be replicated to the others.

On the others will have any files there moved to thr pre existing folder

A backup if the files should be made
Look at the sysvol to see which was updated most recently as a guide.

Do both systems have corrupted jrnl or just one preventing replication.
Andrew N. KowtaloSupport Center Engineer

Author

Commented:

Arnold right now I am honestly unsure.   Could I ask if you can give me a step by step process on what to do in order.  I am very nervous because this is their main DC/ File Server and want to make sure I do the steps right.   Starting from 1. then 2. then 3. I would appreciate it greatly.   This client is really troublesome so 1 slight mistake can be costly. 

Andrew N. KowtaloSupport Center Engineer

Author

Commented:

Alright.  Should I run this from the PDC Or BDC? 

Distinguished Expert 2019

Commented:
that is the question of which server has the current information. that server will have the d4  if memory serves is the authoritative/reference while the other is the D2.

Open a session to each all the fix does is reinitialize the replication database and then starts the sync with the node that is D4 as  the reference with the nodes that are D2 as replicas.

any data present on the D2 nodes will be reloaceted into the PREExisting folder, the backup should be taken just in case on each node. ...

if the wrong one is chosen as the reference, the data can be copied out of the preexisting folder back into the main path and then ......
the replication will resume....
Distinguished Expert 2019

Commented:
The burflags deals with all dcs in the environment.
You then make the registry adjustment  on all systems
Starts the frs service on all which will reinitoalize the frs database and the system with the D4 flag will be the base reference for files while the D2 nodes will move what they have into preexisting folder before synchronizing the data from the authoritative
Andrew N. KowtaloSupport Center Engineer

Author

Commented:

Arnold let me work on this and will get back to you keep this thread open.

Andrew N. KowtaloSupport Center Engineer

Author

Commented:

Also should I do this after hours so business isnt interrupted? 

Distinguished Expert 2019

Commented:
It can be done during as you are addressing file replication which is server to server
Andrew N. KowtaloSupport Center Engineer

Author

Commented:

I know the age of these servers are OLD and I am starting to wonder whether or not I should bother attempting to try and fix replication.   Perhaps once we build their new environment in a couple months we can properly set permissions and adjustments for file folders and policies.   Right now I can assure you all the environment is a total cluster.   I am just not sure if something is going to break before that happens.   Because of how old things are my fear is running any of this and everything goes boom.   

Distinguished Expert 2019

Commented:
Unfortunately, in your situation you can not wait. You have to resolve the issue at hand to get the option to transition away from FRS to dfs replication to allow joining a newer od based DC which do not support FRS for sysvol, ad replication.

Backup the files on each DC,, the risk, if you choose the wrong DC as the reference, is minimal with the data moved to a preexisting subfolders.

Addressing issues with FRS does not impact normal operations. The only incremental impact is to a system booting or a user loging in using the DC whose data is moved to a prexisting .. By way the gpos will not be there and thus will not be applied.

Disable FRS service on all DCs. Pick one, and reset it as a D4. Start the FRS service on this DC on,y while confirming no jrnl event.
Then go to the second, cobfigured it to reinitialize the DB, start the FRS service. Let the data replication complete.
Check gpmc for policies. If you chose incorrectly, look at the preexisting folder for the guid of the GPO that is missing, move or copy it from the prexisting folder and back into the policies subfolder, it should replicate to the other..

Then begin looking at the guidelines to transition from FRS to dfs-replication.

Takes three steps....

Once transitioned to dfs-replication for AD future addition of newer DCs will be straight forward.
Distinguished Expert 2019

Commented:
Andrew N. KowtaloSupport Center Engineer

Author

Commented:

I think because this may be a little over my head I will have to get some help.   But keep this open for now. 

Andrew N. KowtaloSupport Center Engineer

Author

Commented:

Going to run a dcdiag to and see what I can find.   I will show results.

Andrew N. KowtaloSupport Center Engineer

Author

Commented:

WOW! Here are the results.


            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   07:56:56
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   07:57:01
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   07:57:06
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   07:57:11
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   07:57:16
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   07:57:21
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   07:57:26
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   07:57:31
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   07:57:36
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   07:57:41
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   07:57:46
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   07:57:51
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   07:57:56
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   07:58:01
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   07:58:06
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   07:58:11
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   07:58:16
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   07:58:21
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   07:58:26
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   07:58:31
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   07:58:36
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   07:58:41
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   07:58:46
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   07:58:51
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   07:58:56
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   07:59:01
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   07:59:06
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   07:59:11
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   07:59:16
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   07:59:21
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   07:59:26
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   07:59:31
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   07:59:36
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   07:59:41
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   07:59:46
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   07:59:51
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   07:59:56
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:00:01
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:00:06
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:00:11
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:00:16
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:00:21
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:00:26
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:00:31
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:00:36
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:00:41
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:00:46
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:00:51
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:00:56
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:01:01
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:01:06
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:01:11
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:01:16
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:01:21
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:01:26
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:01:31
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:01:36
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:01:41
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:01:46
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:01:51
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:01:56
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:02:01
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:02:06
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:02:11
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:02:16
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:02:21
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:02:26
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:02:31
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:02:36
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:02:41
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:02:46
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:02:51
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:02:56
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:03:01
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:03:06
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:03:11
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:03:16
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:03:21
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:03:26
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:03:31
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:03:36
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:03:41
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:03:46
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:03:51
            Event String: GetDeviceID failed: 0x0
         An Warning Event occurred.  EventID: 0x81020039
            Time Generated: 02/04/2020   08:03:56
            Event String: GetDeviceID failed: 0x0
         ......................... VISIONDC2 passed test SystemLog
      Starting test: VerifyReferences
         ......................... VISIONDC2 passed test VerifyReferences


   Running partition tests on : ForestDnsZones
      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... ForestDnsZones passed test
         CrossRefValidation

   Running partition tests on : DomainDnsZones
      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test
         CrossRefValidation

   Running partition tests on : Schema
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation

   Running partition tests on : Configuration
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation

   Running partition tests on : ecva2
      Starting test: CheckSDRefDom
         ......................... ecva2 passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... ecva2 passed test CrossRefValidation

   Running enterprise tests on : ecva2.local
      Starting test: LocatorCheck
         ......................... ecva2.local passed test LocatorCheck
      Starting test: Intersite
         ......................... ecva2.local passed test Intersite

C:\Users\administrator.ECVA2>

Andrew N. KowtaloSupport Center Engineer

Author

Commented:

More


C:\Users\administrator.ECVA2>dcdiag

Directory Server Diagnosis

Performing initial setup:
   Trying to find home server...
   Home Server = VISIONDC2
   * Identified AD Forest.
   Done gathering initial info.

Doing initial required tests

   Testing server: Default-First-Site-Name\VISIONDC2
      Starting test: Connectivity
         ......................... VISIONDC2 passed test Connectivity

Doing primary tests

   Testing server: Default-First-Site-Name\VISIONDC2
      Starting test: Advertising
         ......................... VISIONDC2 passed test Advertising
      Starting test: FrsEvent
         ......................... VISIONDC2 passed test FrsEvent
      Starting test: DFSREvent
         ......................... VISIONDC2 passed test DFSREvent
      Starting test: SysVolCheck
         ......................... VISIONDC2 passed test SysVolCheck
      Starting test: KccEvent
         ......................... VISIONDC2 passed test KccEvent
      Starting test: KnowsOfRoleHolders
         ......................... VISIONDC2 passed test KnowsOfRoleHolders
      Starting test: MachineAccount
         ......................... VISIONDC2 passed test MachineAccount
      Starting test: NCSecDesc
         ......................... VISIONDC2 passed test NCSecDesc
      Starting test: NetLogons
         ......................... VISIONDC2 passed test NetLogons
      Starting test: ObjectsReplicated
         ......................... VISIONDC2 passed test ObjectsReplicated
      Starting test: Replications
         ......................... VISIONDC2 passed test Replications
      Starting test: RidManager
         ......................... VISIONDC2 passed test RidManager
      Starting test: Services
         ......................... VISIONDC2 passed test Services

Andrew N. KowtaloSupport Center Engineer

Author

Commented:

I piped the output just in case I missed anything heres the full attachmendcdiag.txtt

Andrew N. KowtaloSupport Center Engineer

Author

Commented:

I found out the BDC is actually the PDC and that is where the problem is see attached. BDC DCDIAG.txt

Distinguished Expert 2019
Commented:
With the modern AD the PDC/BDC have less meaning as the old.

The important issue here is not whether it is a PDC or a BDC, the issue is which system has the most current files.

The issue here is a corrupt replication database which prevents file replication between the servers.

The point is, stop FRS service on both servers. On the system with the issue, set the registry entry in the message to reinitialize the DB. Set the D4 flag and start the service.
Then start the service on the other while monitoring the contents of the c:\windows\system32\sysvol

It should not change.
Then you can create a test file in the PDC to see if it replicates to the BDC, then do the same on the other to confirm replication reestablished.

Note: backup sysvol files on each system.

Once replication is reestablished, look at transitioning to dfsr.
Andrew N. KowtaloSupport Center Engineer

Author

Commented:

Now that i know where the good sysvol is I will do this.  This will be considered per contract a project based fix prior to us updating their infrastructure so once this is in place we will perform the actions.  Thanks again for all the help.