Re: Windows 2008 and SYSVOL
- From: Ed <Ed@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 22 Apr 2009 07:49:03 -0700
it doesnt show up
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
Home Server = ISNDC1
* Identified AD Forest.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\ISNDC1
Starting test: Connectivity
......................... ISNDC1 passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\ISNDC1
Starting test: Advertising
Fatal Error:DsGetDcName (ISNDC1) call failed, error 1355
The Locator could not find the server.
......................... ISNDC1 failed 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.
......................... ISNDC1 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.
......................... ISNDC1 failed test DFSREvent
Starting test: SysVolCheck
......................... ISNDC1 passed test SysVolCheck
Starting test: KccEvent
......................... ISNDC1 passed test KccEvent
Starting test: KnowsOfRoleHolders
......................... ISNDC1 passed test KnowsOfRoleHolders
Starting test: MachineAccount
......................... ISNDC1 passed test MachineAccount
Starting test: NCSecDesc
......................... ISNDC1 passed test NCSecDesc
Starting test: NetLogons
Unable to connect to the NETLOGON share! (\\ISNDC1\netlogon)
[ISNDC1] An net use or LsaPolicy operation failed with error 67,
The network name cannot be found..
......................... ISNDC1 failed test NetLogons
Starting test: ObjectsReplicated
......................... ISNDC1 passed test ObjectsReplicated
Starting test: Replications
......................... ISNDC1 passed test Replications
Starting test: RidManager
......................... ISNDC1 passed test RidManager
Starting test: Services
......................... ISNDC1 passed test Services
Starting test: SystemLog
An Error Event occurred. EventID: 0x00000422
Time Generated: 04/22/2009 09:37:41
Event String:
The processing of Group Policy failed. Windows attempted to read
the file
\\insightnetworks.local\sysvol\insightnetworks.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini
from a domain controller and was not successful. Group Policy settings may
not be applied until this event is resolved. This issue may be transient and
could be caused by one or more of the following:
An Error Event occurred. EventID: 0x00000406
Time Generated: 04/22/2009 09:42:44
Event String:
The processing of Group Policy failed. Windows attempted to
retrieve new Group Policy settings for this user or computer. Look in the
details tab for error code and description. Windows will automatically retry
this operation at the next refresh cycle. Computers joined to the domain must
have proper name resolution and network connectivity to a domain controller
for discovery of new Group Policy objects and settings. An event will be
logged when Group Policy is successful.
An Error Event occurred. EventID: 0x00000406
Time Generated: 04/22/2009 09:47:47
Event String:
The processing of Group Policy failed. Windows attempted to
retrieve new Group Policy settings for this user or computer. Look in the
details tab for error code and description. Windows will automatically retry
this operation at the next refresh cycle. Computers joined to the domain must
have proper name resolution and network connectivity to a domain controller
for discovery of new Group Policy objects and settings. An event will be
logged when Group Policy is successful.
An Error Event occurred. EventID: 0x00000406
Time Generated: 04/22/2009 09:52:49
Event String:
The processing of Group Policy failed. Windows attempted to
retrieve new Group Policy settings for this user or computer. Look in the
details tab for error code and description. Windows will automatically retry
this operation at the next refresh cycle. Computers joined to the domain must
have proper name resolution and network connectivity to a domain controller
for discovery of new Group Policy objects and settings. An event will be
logged when Group Policy is successful.
An Error Event occurred. EventID: 0x00000406
Time Generated: 04/22/2009 09:57:52
Event String:
The processing of Group Policy failed. Windows attempted to
retrieve new Group Policy settings for this user or computer. Look in the
details tab for error code and description. Windows will automatically retry
this operation at the next refresh cycle. Computers joined to the domain must
have proper name resolution and network connectivity to a domain controller
for discovery of new Group Policy objects and settings. An event will be
logged when Group Policy is successful.
An Error Event occurred. EventID: 0x00000406
Time Generated: 04/22/2009 10:02:55
Event String:
The processing of Group Policy failed. Windows attempted to
retrieve new Group Policy settings for this user or computer. Look in the
details tab for error code and description. Windows will automatically retry
this operation at the next refresh cycle. Computers joined to the domain must
have proper name resolution and network connectivity to a domain controller
for discovery of new Group Policy objects and settings. An event will be
logged when Group Policy is successful.
An Error Event occurred. EventID: 0x00000406
Time Generated: 04/22/2009 10:13:02
Event String:
The processing of Group Policy failed. Windows attempted to
retrieve new Group Policy settings for this user or computer. Look in the
details tab for error code and description. Windows will automatically retry
this operation at the next refresh cycle. Computers joined to the domain must
have proper name resolution and network connectivity to a domain controller
for discovery of new Group Policy objects and settings. An event will be
logged when Group Policy is successful.
An Error Event occurred. EventID: 0x00000406
Time Generated: 04/22/2009 10:18:05
Event String:
The processing of Group Policy failed. Windows attempted to
retrieve new Group Policy settings for this user or computer. Look in the
details tab for error code and description. Windows will automatically retry
this operation at the next refresh cycle. Computers joined to the domain must
have proper name resolution and network connectivity to a domain controller
for discovery of new Group Policy objects and settings. An event will be
logged when Group Policy is successful.
......................... ISNDC1 failed test SystemLog
Starting test: VerifyReferences
......................... ISNDC1 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 : insightnetworks
Starting test: CheckSDRefDom
......................... insightnetworks passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... insightnetworks passed test
CrossRefValidation
Running enterprise tests on : insightnetworks.local
Starting test: LocatorCheck
Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355
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_SERVER_PREFERRED) call failed, error
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.
......................... insightnetworks.local failed test
LocatorCheck
Starting test: Intersite
......................... insightnetworks.local passed test Intersite
"Francis Ouellet" wrote:
Hi Ed,.
Yes, the SYSVOL share should show up! Fire up a command line and do a "net
share". Is your sysvol share showing up?
Also, you could launch dcdiag.exe and see what the results are for the
"frssysvol" test.
Let us know!
--
Francis Ouellet
1998 - 2006 MVP
http://directoryservicesconsulting.ca
On 22/April/2009 9:44 AM, in article
77B99EF9-EE9F-48C5-867D-8CC7AFEE1336@xxxxxxxxxxxxx, "Ed"
<Ed@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
is sysvol suppose to show up as a share like it did in windows 2003 dc? Mine
doesnt . if thats not correct how do I fix it?
- Follow-Ups:
- Re: Windows 2008 and SYSVOL
- From: Meinolf Weber [MVP-DS]
- Re: Windows 2008 and SYSVOL
- From: Isaac Oben [MCITP,MCSE]
- Re: Windows 2008 and SYSVOL
- From: Francis Ouellet
- Re: Windows 2008 and SYSVOL
- References:
- Windows 2008 and SYSVOL
- From: Ed
- Re: Windows 2008 and SYSVOL
- From: Francis Ouellet
- Windows 2008 and SYSVOL
- Prev by Date: Re: Windows 2008 and SYSVOL
- Next by Date: Slow Logins and Slow Boot-up
- Previous by thread: Re: Windows 2008 and SYSVOL
- Next by thread: Re: Windows 2008 and SYSVOL
- Index(es):
Relevant Pages
|
