asked on
How long does SYSVOL take to rebuild?
Situation; two servers DC1 and DC2 Both wiped out by Ransomeware. I have a good bare metal copy of Server DC2 and I decide to junk DC1. The restore goes fine. I take over the FSMO roles on the new server and use a metadata cleanup to remove DC1. I added the Server 192.168.254.10 to the NIC as DNS.
When the server starts up I have no access to any AD windows and very little is available in Adminastrative tools. Using DCdiag I find the SYSVOL and NETLOGON arent shared.
Checking the Event viewer I see that DC2 cant become the DC until it has rebuilt SYSVOL and has it as a share. Its been running foor 48 hours on a disk which has 500Gb of data on it and its a SATA3.
1. How long can I expect it to take? The hard disk light is flashing and the drives are flashing.
I have been through the logs this is the entry for FRS;
File Replication Service is scanning the data in the system volume. Computer SERVER01 cannot become a domain controller until this process is complete. The system volume will then be shared as SYSVOL.
To check for the SYSVOL share, at the command prompt, type:
net share
When File Replication Service completes the scanning process, the SYSVOL share will appear.
The initialization of the system volume can take some time. The time is dependent on the amount of data in the system volume.
This is the entry in DFS;
The DFS replication service succesfully contacted doman controller <DC1.local> to access configuration information
This is the result of DCDIAG anfter doing a fix:
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
Home Server = SERVER01
* Identified AD Forest.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\SE
Starting test: Connectivity
......................... SERVER01 passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\SE
Starting test: Advertising
Fatal Error:DsGetDcName (SERVER01) call failed, error 1355
The Locator could not find the server.
......................... SERVER01 failed test Advertising
Starting test: FrsEvent
......................... SERVER01 passed test FrsEvent
Starting test: DFSREvent
......................... SERVER01 passed test DFSREvent
Starting test: SysVolCheck
......................... SERVER01 passed test SysVolCheck
Starting test: KccEvent
......................... SERVER01 passed test KccEvent
Starting test: KnowsOfRoleHolders
......................... SERVER01 passed test KnowsOfRoleHolders
Starting test: MachineAccount
......................... SERVER01 passed test MachineAccount
Starting test: NCSecDesc
......................... SERVER01 passed test NCSecDesc
Starting test: NetLogons
Unable to connect to the NETLOGON share! (\\SERVER01\netlogon)
[SERVER01] An net use or LsaPolicy operation failed with error 67,
The network name cannot be found..
......................... SERVER01 failed test NetLogons
Starting test: ObjectsReplicated
......................... SERVER01 passed test ObjectsReplicated
Starting test: Replications
......................... SERVER01 passed test Replications
Starting test: RidManager
......................... SERVER01 passed test RidManager
Starting test: Services
......................... SERVER01 passed test Services
Starting test: SystemLog
An error event occurred. EventID: 0x0000271A
Time Generated: 09/03/2018 09:21:19
Event String:
The server {9BA05972-F6A8-11CF-A442-0
An error event occurred. EventID: 0x0000271A
Time Generated: 09/03/2018 09:21:19
Event String:
The server {9BA05972-F6A8-11CF-A442-0
An error event occurred. EventID: 0x00000469
Time Generated: 09/03/2018 09:21:33
Event String:
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
An error event occurred. EventID: 0x00000469
Time Generated: 09/03/2018 09:22:58
Event String:
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
An error event occurred. EventID: 0xC00038D6
Time Generated: 09/03/2018 09:37:45
Event String:
The DFS Namespace service could not initialize cross forest trust information on this domain controller, but it will periodically retry the operation. The return code is in the record data.
......................... SERVER01 failed test SystemLog
Starting test: VerifyReferences
......................... SERVER01 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 : <domain>
Starting test: CheckSDRefDom
......................... <domain> passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... jodal2 passed test CrossRefValidation
Running enterprise tests on : <domain>.local
Starting test: LocatorCheck
Warning: DcGetDcName(GC_SERVER_REQU
A Global Catalog Server could not be located - All GC's are down.
Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
A Time Server could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(GOOD_TIME_SERV
1355
A Good Time Server could not be located.
Warning: DcGetDcName(KDC_REQUIRED) call failed, error 1355
A KDC could not be located - All the KDCs are down.
......................... <domain>.local failed test LocatorCheck
Starting test: Intersite
......................... <domain>.local passed test Intersite
2. Help, is it stuck?
When the server starts up I have no access to any AD windows and very little is available in Adminastrative tools. Using DCdiag I find the SYSVOL and NETLOGON arent shared.
Checking the Event viewer I see that DC2 cant become the DC until it has rebuilt SYSVOL and has it as a share. Its been running foor 48 hours on a disk which has 500Gb of data on it and its a SATA3.
1. How long can I expect it to take? The hard disk light is flashing and the drives are flashing.
I have been through the logs this is the entry for FRS;
File Replication Service is scanning the data in the system volume. Computer SERVER01 cannot become a domain controller until this process is complete. The system volume will then be shared as SYSVOL.
To check for the SYSVOL share, at the command prompt, type:
net share
When File Replication Service completes the scanning process, the SYSVOL share will appear.
The initialization of the system volume can take some time. The time is dependent on the amount of data in the system volume.
This is the entry in DFS;
The DFS replication service succesfully contacted doman controller <DC1.local> to access configuration information
This is the result of DCDIAG anfter doing a fix:
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
Home Server = SERVER01
* Identified AD Forest.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\SE
Starting test: Connectivity
......................... SERVER01 passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\SE
Starting test: Advertising
Fatal Error:DsGetDcName (SERVER01) call failed, error 1355
The Locator could not find the server.
......................... SERVER01 failed test Advertising
Starting test: FrsEvent
......................... SERVER01 passed test FrsEvent
Starting test: DFSREvent
......................... SERVER01 passed test DFSREvent
Starting test: SysVolCheck
......................... SERVER01 passed test SysVolCheck
Starting test: KccEvent
......................... SERVER01 passed test KccEvent
Starting test: KnowsOfRoleHolders
......................... SERVER01 passed test KnowsOfRoleHolders
Starting test: MachineAccount
......................... SERVER01 passed test MachineAccount
Starting test: NCSecDesc
......................... SERVER01 passed test NCSecDesc
Starting test: NetLogons
Unable to connect to the NETLOGON share! (\\SERVER01\netlogon)
[SERVER01] An net use or LsaPolicy operation failed with error 67,
The network name cannot be found..
......................... SERVER01 failed test NetLogons
Starting test: ObjectsReplicated
......................... SERVER01 passed test ObjectsReplicated
Starting test: Replications
......................... SERVER01 passed test Replications
Starting test: RidManager
......................... SERVER01 passed test RidManager
Starting test: Services
......................... SERVER01 passed test Services
Starting test: SystemLog
An error event occurred. EventID: 0x0000271A
Time Generated: 09/03/2018 09:21:19
Event String:
The server {9BA05972-F6A8-11CF-A442-0
An error event occurred. EventID: 0x0000271A
Time Generated: 09/03/2018 09:21:19
Event String:
The server {9BA05972-F6A8-11CF-A442-0
An error event occurred. EventID: 0x00000469
Time Generated: 09/03/2018 09:21:33
Event String:
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
An error event occurred. EventID: 0x00000469
Time Generated: 09/03/2018 09:22:58
Event String:
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
An error event occurred. EventID: 0xC00038D6
Time Generated: 09/03/2018 09:37:45
Event String:
The DFS Namespace service could not initialize cross forest trust information on this domain controller, but it will periodically retry the operation. The return code is in the record data.
......................... SERVER01 failed test SystemLog
Starting test: VerifyReferences
......................... SERVER01 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 : <domain>
Starting test: CheckSDRefDom
......................... <domain> passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... jodal2 passed test CrossRefValidation
Running enterprise tests on : <domain>.local
Starting test: LocatorCheck
Warning: DcGetDcName(GC_SERVER_REQU
A Global Catalog Server could not be located - All GC's are down.
Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
A Time Server could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(GOOD_TIME_SERV
1355
A Good Time Server could not be located.
Warning: DcGetDcName(KDC_REQUIRED) call failed, error 1355
A KDC could not be located - All the KDCs are down.
......................... <domain>.local failed test LocatorCheck
Starting test: Intersite
......................... <domain>.local passed test Intersite
2. Help, is it stuck?
Windows OSWindows Server 2012DNSNetworking
Last Comment
Fiona Cheeseman