User locked out - Events 1955 and 1083

Just yesterday a user starting having issues logging into a server.  I had them reboot and found they couldn't log in at all.  But it seems sporadic.

After much searching I am seeing the messages below on one of my domain controllers that point to the users object.  These appeared, I suspect around when I attempted change their password because of these issues.  

The DC in question was recently added (with in a month or so).  They are 3 domain controllers running Server 2012R2 domain functional level 2003

    Log Name:      Directory Service
Source:        Microsoft-Windows-ActiveDirectory_DomainService
Date:          7/5/2018 3:28:07 PM
Event ID:      1083
Task Category: Replication
Level:         Warning
Keywords:      Classic
User:          ANONYMOUS LOGON
Computer:      DC04
Description:
Active Directory Domain Services could not update the following object with changes received from the directory service at the following network address because Active Directory Domain Services was busy processing information. 
 
Object:
CN=
Network address:
e3457cb7-5a59-4383-b661-a5266614d890._msdcs.
 
This operation will be tried again later.

Log Name:      Directory Service
Source:        Microsoft-Windows-ActiveDirectory_DomainService
Date:          7/5/2018 3:28:07 PM
Event ID:      1955
Task Category: Replication
Level:         Information
Keywords:      Classic
User:          ANONYMOUS LOGON
Computer:      Description:
Active Directory Domain Services encountered a write conflict when applying replicated changes to the following object. 

Object: 
CN=,OU=,DC=,DC=com 
Time in seconds: 
0 

Event log entries preceding this entry will indicate whether or not the update was accepted. 

A write conflict can be caused by simultaneous changes to the same object or simultaneous changes to other objects that have attributes referencing this object. This commonly occurs when the object represents a large group with many members, and the functional level of the forest is set to Windows 2000. This conflict triggered additional retries of the update. If the system appears slow, it could be because replication of these changes is occurring. 

User Action 
Use smaller groups for this operation or raise the forest functional level to Windows Server 2003.