hi all
i went to a company that has 2 domain controllers dc01 and DC02 ,dc02 is the additional domain controller was considered as tombstone because a replication doesn't take place since april 2017, so I demoted it today
running dcdiag on dc01 : i have the following errors regarding dfs although there is no dfs installed
I also check dfs log and found that it instructs me to opem dfs snapin to remove this server from replication group
I don't know how to do this
bellow the logs
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
Home Server = DC01
* Identified AD Forest.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\DC01
Starting test: Connectivity
......................... DC01 passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\DC01
Starting test: Advertising
......................... DC01 passed test Advertising
Starting test: FrsEvent
......................... DC01 passed test FrsEvent
Starting test: DFSREvent
There are warning or error events within the last 24 hours after the
SYSVOL has been shared. Failing SYSVOL replication problems may cause
Group Policy problems.
......................... DC01 failed test DFSREvent
Starting test: SysVolCheck
......................... DC01 passed test SysVolCheck
Starting test: KccEvent
A warning event occurred. EventID: 0x8000082C
Time Generated: 09/16/2018 09:10:12
Event String:
......................... DC01 passed test KccEvent
Starting test: KnowsOfRoleHolders
......................... DC01 passed test KnowsOfRoleHolders
Starting test: MachineAccount
......................... DC01 passed test MachineAccount
Starting test: NCSecDesc
......................... DC01 passed test NCSecDesc
Starting test: NetLogons
......................... DC01 passed test NetLogons
Starting test: ObjectsReplicated
......................... DC01 passed test ObjectsReplicated
Starting test: Replications
[Replications Check,DC01] A recent replication attempt failed:
From DC02 to DC01
Naming Context: DC=ForestDnsZones,DC=mydomain,DC=local
The replication generated an error (8614):
The directory service cannot replicate with this server because the time since the last replication with this server has exceeded the tombstone lifetime.
The failure occurred at 2018-09-16 08:55:13.
The last success occurred at 2017-04-05 11:49:17.
11307 failures have occurred since the last success.
[Replications Check,DC01] A recent replication attempt failed:
From DC02 to DC01
Naming Context: DC=DomainDnsZones,DC=mydomain,DC=local
The replication generated an error (8614):
The directory service cannot replicate with this server because the time since the last replication with this server has exceeded the tombstone lifetime.
The failure occurred at 2018-09-16 08:55:13.
The last success occurred at 2017-04-05 11:49:17.
11313 failures have occurred since the last success.
[Replications Check,DC01] A recent replication attempt failed:
From DC02 to DC01
Naming Context: CN=Schema,CN=Configuration,DC=mydomain,DC=local
The replication generated an error (8614):
The directory service cannot replicate with this server because the time since the last replication with this server has exceeded the tombstone lifetime.
The failure occurred at 2018-09-16 08:55:13.
The last success occurred at 2017-04-05 11:49:17.
11307 failures have occurred since the last success.
[Replications Check,DC01] A recent replication attempt failed:
From DC02 to DC01
Naming Context: CN=Configuration,DC=mydomain,DC=local
The replication generated an error (8614):
The directory service cannot replicate with this server because the time since the last replication with this server has exceeded the tombstone lifetime.
The failure occurred at 2018-09-16 08:55:13.
The last success occurred at 2017-04-05 11:49:17.
11307 failures have occurred since the last success.
[Replications Check,DC01] A recent replication attempt failed:
From DC02 to DC01
Naming Context: DC=mydomain,DC=local
The replication generated an error (8614):
The directory service cannot replicate with this server because the time since the last replication with this server has exceeded the tombstone lifetime.
The failure occurred at 2018-09-16 08:55:13.
The last success occurred at 2017-04-05 12:02:13.
11470 failures have occurred since the last success.
......................... DC01 failed test Replications
Starting test: RidManager
......................... DC01 passed test RidManager
Starting test: Services
......................... DC01 passed test Services
Starting test: SystemLog
An error event occurred. EventID: 0xC0001B63
Time Generated: 09/16/2018 08:40:09
Event String:
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the UmRdpService service.
An error event occurred. EventID: 0xC0001B63
Time Generated: 09/16/2018 08:40:39
Event String:
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the ScDeviceEnum service.
An error event occurred. EventID: 0xC0001B58
Time Generated: 09/16/2018 08:40:39
Event String:
The Smart Card Device Enumeration Service service failed to start due to the following error:
An error event occurred. EventID: 0xC0001B63
Time Generated: 09/16/2018 08:50:55
Event String:
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the UmRdpService service.
An error event occurred. EventID: 0xC0001B63
Time Generated: 09/16/2018 09:07:14
Event String:
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the UmRdpService service.
An error event occurred. EventID: 0xC0001B63
Time Generated: 09/16/2018 09:07:44
Event String:
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the ScDeviceEnum service.
An error event occurred. EventID: 0xC0001B58
Time Generated: 09/16/2018 09:07:44
Event String:
The Smart Card Device Enumeration Service service failed to start due to the following error:
......................... DC01 failed test SystemLog
Starting test: VerifyReferences
......................... DC01 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 : mydomain
Starting test: CheckSDRefDom
......................... mydomain passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... mydomain passed test CrossRefValidation
Running enterprise tests on : mydomain.local
Starting test: LocatorCheck
......................... mydomain.local passed test LocatorCheck
Starting test: Intersite
......................... mydomain.local passed test Intersite
*********************************************************************************************
DFS logs
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 541 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: 3BFC547C-224C-40F1-8757-386C221B3E8B
Replication Group Name: Domain System Volume
Replication Group ID: E460C25B-61A3-4BBB-829F-5FC9462252AB
**************************************************************************
Installed programs
Name : AD-Domain-ServicesInstallState : Installed
Name : DNS
InstallState : Installed
Name : FileAndStorage-Services
InstallState : Installed
Name : File-Services
InstallState : Installed
Name : FS-FileServer
InstallState : Installed
Name : Storage-Services
InstallState : Installed
Name : NET-Framework-45-Features
InstallState : Installed
Name : NET-Framework-45-Core
InstallState : Installed
Name : NET-WCF-Services45
InstallState : Installed
Name : NET-WCF-TCP-PortSharing45
InstallState : Installed
Name : GPMC
InstallState : Installed