Results 1 to 5 of 5

Thread: Windows 2008 and SYSVOL

  1. #1
    Join Date
    Apr 2004
    Posts
    57

    Windows 2008 and SYSVOL

    I was earlier running a Windows 2003 Server DC and I remember SYSVOL use to show up as a share. Now I have installed a new Server Windows 2008 but the sysvol is not showing up as a Share.

    Any idea what is wrong and how can I fix it?

  2. #2
    Join Date
    Jan 2006
    Posts
    154

    Re: Windows 2008 and SYSVOL

    There is nothing changed regarding this in Windows 2008. So SYSVOL should still show up as share. But as you said it is not showing up, just try doing a "net share" via command line .

    Apart from this you should also try out dcdiag.exe and see what the results are for the "frssysvol" test. See if sysvol share showing up now.

  3. #3
    Join Date
    Apr 2004
    Posts
    57

    Re: Windows 2008 and SYSVOL

    Thank you very much for the help Tanvir. I followed your suggestions and ran all your test but it is still not showing up. Here are the test results.

    ----------------------------------------------------------------
    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

  4. #4
    Join Date
    Jan 2006
    Posts
    154

    Re: Windows 2008 and SYSVOL

    I checked the results carefully. It indicates that there was something wrong within your environment. It shows that Dcdiag is complaining about mising roles (PDC). So I’ll suggest you to try running "netdom query fsmo".

    Post the results here.

  5. #5
    Join Date
    Sep 2004
    Posts
    63

    Re: Windows 2008 and SYSVOL

    Yeah, I too agree with Tanvir. Your results are showing up few failures such as Ntelogon, advertising etc.. I have some questions which will help me fix your problem if you can let me know if your DNS is configured and is this your first ever DC. When you reply, just try to post your IPconfig /all results as well.

Similar Threads

  1. Unable to access \\domain\SYSVOL but able to access \\server\SYSVOL
    By Ashish Goenkar in forum Active Directory
    Replies: 3
    Last Post: 03-01-2014, 04:03 PM
  2. SYSVOL sharing problem on Windows 2003
    By AMIEL in forum Networking & Security
    Replies: 5
    Last Post: 09-01-2010, 11:22 AM
  3. Replies: 1
    Last Post: 06-05-2009, 09:09 PM
  4. Sysvol issues.....
    By Rising in forum Active Directory
    Replies: 10
    Last Post: 04-12-2007, 07:22 PM
  5. Replies: 1
    Last Post: 13-02-2007, 03:00 AM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,713,858,288.03732 seconds with 17 queries