We had a 2003 Server as our DC, and I joined a 2012 R2 server to our domain, promoted it, transferred roles, etc... I believe, however, that I didn't let settings propagate long enough prior to demoting the 2003 DC, and was left without SYSVOL and NETLOGON
shares on my DC's now. Below is a dcdiag. Does someone know what to do from here? Thanks.
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
H:\>dcdiag
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
Home Server = LSS-PHX-DC
* Identified AD Forest.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\LSS-PHX-DC
Starting test: Connectivity
......................... LSS-PHX-DC passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\LSS-PHX-DC
Starting test: Advertising
......................... LSS-PHX-DC passed test Advertising
Starting test: FrsEvent
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.
......................... LSS-PHX-DC passed test FrsEvent
Starting test: DFSREvent
......................... LSS-PHX-DC passed test DFSREvent
Starting test: SysVolCheck
......................... LSS-PHX-DC passed test SysVolCheck
Starting test: KccEvent
......................... LSS-PHX-DC passed test KccEvent
Starting test: KnowsOfRoleHolders
......................... LSS-PHX-DC passed test KnowsOfRoleHolders
Starting test: MachineAccount
......................... LSS-PHX-DC passed test MachineAccount
Starting test: NCSecDesc
......................... LSS-PHX-DC passed test NCSecDesc
Starting test: NetLogons
Unable to connect to the NETLOGON share! (\\LSS-PHX-DC\netlogon)
[LSS-PHX-DC] An net use or LsaPolicy operation failed with error 67,
The network name cannot be found..
......................... LSS-PHX-DC failed test NetLogons
Starting test: ObjectsReplicated
......................... LSS-PHX-DC passed test ObjectsReplicated
Starting test: Replications
......................... LSS-PHX-DC passed test Replications
Starting test: RidManager
......................... LSS-PHX-DC passed test RidManager
Starting test: Services
......................... LSS-PHX-DC passed test Services
Starting test: SystemLog
An error event occurred. EventID: 0x00000422
Time Generated: 04/11/2017 08:11:23
Event String:
The processing of Group Policy failed. Windows attempted to read the
file \\LSMAZ.local\SysVol\LSMAZ.local\Policies\{F1A46D2D-797A-4BAE-907E-8E6007B
E8BBA}\gpt.ini from a domain controller and was not successful. Group Policy set
tings may not be applied until this event is resolved. This issue may be transie
nt and could be caused by one or more of the following:
An error event occurred. EventID: 0x00000422
Time Generated: 04/11/2017 08:16:24
Event String:
The processing of Group Policy failed. Windows attempted to read the
file \\LSMAZ.local\SysVol\LSMAZ.local\Policies\{F1A46D2D-797A-4BAE-907E-8E6007B
E8BBA}\gpt.ini from a domain controller and was not successful. Group Policy set
tings may not be applied until this event is resolved. This issue may be transie
nt and could be caused by one or more of the following:
An error event occurred. EventID: 0x00000422
Time Generated: 04/11/2017 08:21:24
Event String:
The processing of Group Policy failed. Windows attempted to read the
file \\LSMAZ.local\SysVol\LSMAZ.local\Policies\{F1A46D2D-797A-4BAE-907E-8E6007B
E8BBA}\gpt.ini from a domain controller and was not successful. Group Policy set
tings may not be applied until this event is resolved. This issue may be transie
nt and could be caused by one or more of the following:
An error event occurred. EventID: 0x00000422
Time Generated: 04/11/2017 08:26:24
Event String:
The processing of Group Policy failed. Windows attempted to read the
file \\LSMAZ.local\SysVol\LSMAZ.local\Policies\{F1A46D2D-797A-4BAE-907E-8E6007B
E8BBA}\gpt.ini from a domain controller and was not successful. Group Policy set
tings may not be applied until this event is resolved. This issue may be transie
nt and could be caused by one or more of the following:
An error event occurred. EventID: 0x00000422
Time Generated: 04/11/2017 08:31:24
Event String:
The processing of Group Policy failed. Windows attempted to read the
file \\LSMAZ.local\SysVol\LSMAZ.local\Policies\{F1A46D2D-797A-4BAE-907E-8E6007B
E8BBA}\gpt.ini from a domain controller and was not successful. Group Policy set
tings may not be applied until this event is resolved. This issue may be transie
nt and could be caused by one or more of the following:
An error event occurred. EventID: 0x00000422
Time Generated: 04/11/2017 08:36:24
Event String:
The processing of Group Policy failed. Windows attempted to read the
file \\LSMAZ.local\SysVol\LSMAZ.local\Policies\{F1A46D2D-797A-4BAE-907E-8E6007B
E8BBA}\gpt.ini from a domain controller and was not successful. Group Policy set
tings may not be applied until this event is resolved. This issue may be transie
nt and could be caused by one or more of the following:
An error event occurred. EventID: 0x00000422
Time Generated: 04/11/2017 08:41:24
Event String:
The processing of Group Policy failed. Windows attempted to read the
file \\LSMAZ.local\SysVol\LSMAZ.local\Policies\{F1A46D2D-797A-4BAE-907E-8E6007B
E8BBA}\gpt.ini from a domain controller and was not successful. Group Policy set
tings may not be applied until this event is resolved. This issue may be transie
nt and could be caused by one or more of the following:
An error event occurred. EventID: 0x00000422
Time Generated: 04/11/2017 08:46:25
Event String:
The processing of Group Policy failed. Windows attempted to read the
file \\LSMAZ.local\SysVol\LSMAZ.local\Policies\{F1A46D2D-797A-4BAE-907E-8E6007B
E8BBA}\gpt.ini from a domain controller and was not successful. Group Policy set
tings may not be applied until this event is resolved. This issue may be transie
nt and could be caused by one or more of the following:
An error event occurred. EventID: 0x00000422
Time Generated: 04/11/2017 08:51:25
Event String:
The processing of Group Policy failed. Windows attempted to read the
file \\LSMAZ.local\SysVol\LSMAZ.local\Policies\{F1A46D2D-797A-4BAE-907E-8E6007B
E8BBA}\gpt.ini from a domain controller and was not successful. Group Policy set
tings may not be applied until this event is resolved. This issue may be transie
nt and could be caused by one or more of the following:
An error event occurred. EventID: 0x00000422
Time Generated: 04/11/2017 08:56:25
Event String:
The processing of Group Policy failed. Windows attempted to read the
file \\LSMAZ.local\SysVol\LSMAZ.local\Policies\{F1A46D2D-797A-4BAE-907E-8E6007B
E8BBA}\gpt.ini from a domain controller and was not successful. Group Policy set
tings may not be applied until this event is resolved. This issue may be transie
nt and could be caused by one or more of the following:
An error event occurred. EventID: 0x00000422
Time Generated: 04/11/2017 09:01:25
Event String:
The processing of Group Policy failed. Windows attempted to read the
file \\LSMAZ.local\SysVol\LSMAZ.local\Policies\{F1A46D2D-797A-4BAE-907E-8E6007B
E8BBA}\gpt.ini from a domain controller and was not successful. Group Policy set
tings may not be applied until this event is resolved. This issue may be transie
nt and could be caused by one or more of the following:
An error event occurred. EventID: 0x00000422
Time Generated: 04/11/2017 09:06:25
Event String:
The processing of Group Policy failed. Windows attempted to read the
file \\LSMAZ.local\SysVol\LSMAZ.local\Policies\{F1A46D2D-797A-4BAE-907E-8E6007B
E8BBA}\gpt.ini from a domain controller and was not successful. Group Policy set
tings may not be applied until this event is resolved. This issue may be transie
nt and could be caused by one or more of the following:
An error event occurred. EventID: 0x00000422
Time Generated: 04/11/2017 09:07:37
Event String:
The processing of Group Policy failed. Windows attempted to read the
file \\LSMAZ.local\sysvol\LSMAZ.local\Policies\{31B2F340-016D-11D2-945F-00C04FB
984F9}\gpt.ini from a domain controller and was not successful. Group Policy set
tings may not be applied until this event is resolved. This issue may be transie
nt and could be caused by one or more of the following:
......................... LSS-PHX-DC failed test SystemLog
Starting test: VerifyReferences
......................... LSS-PHX-DC 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 : LSMAZ
Starting test: CheckSDRefDom
......................... LSMAZ passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... LSMAZ passed test CrossRefValidation
Running enterprise tests on : LSMAZ.local
Starting test: LocatorCheck
......................... LSMAZ.local passed test LocatorCheck
Starting test: Intersite
......................... LSMAZ.local passed test Intersite
