Hi Folks,
I have a 2 DC system (2012 r2):
literally DC1 and DC2, both setup as GC's, and both are Virtual on Hyper-v (2 separate Hyper-v hosts)
DC1, was the original controller that has been running fine for a year or more. I recently decided to setup a second DC (dc2). The setup went fine without error and everything seemed to be running along ok.
have them setup for load balancing and replication.
I noticed the other day that DC2 did not have Netlogon shared, and when I dug deeper, no login scripts (Yes I still use login scripts. Smaller organization, so just faster and easier).
I checked events recently and noticed that DC1 is throwing errors about DFS replication: 4012 Error:
----------------------------------------
The DFS Replication service stopped replication on the folder with the following local path: C:\Windows\SYSVOL\domain. This server has been disconnected from other partners for 334 days, which is longer than the time
allowed by the MaxOfflineTimeInDays parameter (60). DFS Replication considers the data in this folder to be stale, and this server will not replicate the folder until this error is corrected.
To resume replication of this folder, use the DFS Management snap-in to remove this server from the replication group, and then add it back to the group. This causes the server to perform an initial synchronization task, which replaces the stale
data with fresh data from other members of the replication group.
Additional Information:
Error: 9061 (The replicated folder has been offline for too long.)
Replicated Folder Name: SYSVOL Share
Replicated Folder ID: B6FCEBF0-DD6A-4BC6-9CFD-F8FA2AA0FEDD
Replication Group Name: Domain System Volume
Replication Group ID: 17A738B6-6EBE-44DF-86BF-ADB0385D47B3
Member ID: F716F9E1-03D4-429A-88DF-86F260C6A2AB
----------------------------------------
As you can see , this error has being going for quite some time (Over 300 days). so, I don't think it is related to the new DC installation. I also can't find the DFS management snap-in as I don't think I actually have DFS namespace or replication installed.(related??)
DCDiag runs show that replication between DC1 and DC2 are working, yet, not netlogon for DC2 and these 4012 errors.
I just started investigating this and I just want to clean it up.
I have also read different solutions about demoting the affected DC and then promoting it again. Is that wise to do that on my first DC1?
One final thought. I have had a couple of my users mention to me (Since setting up the second DC). that they have experienced trouble logging in where it continually says incorrect password when they are sure they entered it correctly. (Not sure if this is all related). when logging in, neither DC throws any kind of error related to a DC not being available or anything like that.
Any help would be appreciated.
Kyrou