• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 890
  • Last Modified:

gpo update, group policy not working, fsmo wont transfer

I have a server 2003 and server 2008r2. installed server 2008r2 about a year ago did the fsmo transfer to 2008r2 and did not give group policy any thought. Today I tried to add a group policy and get the "the network name cannot be found". I ran gpupdate /force and failed syaing that it could not read the sysvol policies. I also noticed that if I shut down the 2003 server I cannot use active directory. I tried changing domain controller to the 2008r2 but it will not hold. also tried moving the schema master and domain naming master to 2008 r2 and failed. I have very little knowledge this far in could anyone please help?

thanks,
Ron
0
ronrod
Asked:
ronrod
  • 6
1 Solution
 
djStraTTosCommented:
Kindly run dcdiag on both servers and revert with the results. Most probably something went wrong at the time you tried to transfer the FSMO roles to the new server.

Have a thorough look at the following article as well: http://support.microsoft.com/kb/324801
0
 
ronrodAuthor Commented:
here is the dcdiag for server2008r2
could not get dcdiag to run on server 2003 standard edition sp2
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\administrator.STFRANCIS>dcdiag

Directory Server Diagnosis

Performing initial setup:
   Trying to find home server...
   Home Server = Mainserver
   * Identified AD Forest.
   Done gathering initial info.

Doing initial required tests

   Testing server: Default-First-Site\MAINSERVER
      Starting test: Connectivity
         ......................... MAINSERVER passed test Connectivity

Doing primary tests

   Testing server: Default-First-Site\MAINSERVER
      Starting test: Advertising
         Warning: DsGetDcName returned information for
         \\sf_dc_01.stfrancis.local, when we were trying to reach MAINSERVER.
         SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.
         ......................... MAINSERVER 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.
         ......................... MAINSERVER passed test FrsEvent
      Starting test: DFSREvent
         ......................... MAINSERVER passed test DFSREvent
      Starting test: SysVolCheck
         ......................... MAINSERVER passed test SysVolCheck
      Starting test: KccEvent
         ......................... MAINSERVER passed test KccEvent
      Starting test: KnowsOfRoleHolders
         ......................... MAINSERVER passed test KnowsOfRoleHolders
      Starting test: MachineAccount
         ......................... MAINSERVER passed test MachineAccount
      Starting test: NCSecDesc
         ......................... MAINSERVER passed test NCSecDesc
      Starting test: NetLogons
         Unable to connect to the NETLOGON share! (\\MAINSERVER\netlogon)
         [MAINSERVER] An net use or LsaPolicy operation failed with error 67,
         The network name cannot be found..
         ......................... MAINSERVER failed test NetLogons
      Starting test: ObjectsReplicated
         ......................... MAINSERVER passed test ObjectsReplicated
      Starting test: Replications
         ......................... MAINSERVER passed test Replications
      Starting test: RidManager
         ......................... MAINSERVER passed test RidManager
      Starting test: Services
         ......................... MAINSERVER passed test Services
      Starting test: SystemLog
         An error event occurred.  EventID: 0x00000422
            Time Generated: 08/22/2012   09:52:45
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\stfrancis.local\SysVol\stfrancis.local\Policies\{74B938CA-0E10-4015-AEBE
-7D98BF8D613F}\gpt.ini from a domain controller and was not successful. Group Po
licy 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: 0x00000422
            Time Generated: 08/22/2012   09:52:45
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
 file \\stfrancis.local\SysVol\stfrancis.local\Policies\{74B938CA-0E10-4015-AEBE
-7D98BF8D613F}\gpt.ini from a domain controller and was not successful. Group Po
licy 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:
         ......................... MAINSERVER failed test SystemLog
      Starting test: VerifyReferences
         ......................... MAINSERVER 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 : stfrancis
      Starting test: CheckSDRefDom
         ......................... stfrancis passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... stfrancis passed test CrossRefValidation

   Running enterprise tests on : stfrancis.local
      Starting test: LocatorCheck
         ......................... stfrancis.local passed test LocatorCheck
      Starting test: Intersite
         ......................... stfrancis.local passed test Intersite

C:\Users\administrator.STFRANCIS>
0
 
ronrodAuthor Commented:
here is the dcdiag for server 2003
03/25/2003  05:00 AM            51,337 WMIAPSRV.EX_
Domain Controller Diagnosis

Performing initial setup:
   Done gathering initial info.

Doing initial required tests

   Testing server: Default-First-Site\SF_DC_01
      Starting test: Connectivity
         ......................... SF_DC_01 passed test Connectivity

Doing primary tests

   Testing server: Default-First-Site\SF_DC_01
      Starting test: Replications
         ......................... SF_DC_01 passed test Replications
      Starting test: NCSecDesc
         ......................... SF_DC_01 passed test NCSecDesc
      Starting test: NetLogons
         ......................... SF_DC_01 passed test NetLogons
      Starting test: Advertising
         ......................... SF_DC_01 passed test Advertising
      Starting test: KnowsOfRoleHolders
         ......................... SF_DC_01 passed test KnowsOfRoleHolders
      Starting test: RidManager
         ......................... SF_DC_01 passed test RidManager
      Starting test: MachineAccount
         ......................... SF_DC_01 passed test MachineAccount
      Starting test: Services
         ......................... SF_DC_01 passed test Services
      Starting test: ObjectsReplicated
         ......................... SF_DC_01 passed test ObjectsReplicated
      Starting test: frssysvol
         ......................... SF_DC_01 passed test frssysvol
      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.
         ......................... SF_DC_01 failed test frsevent
      Starting test: kccevent
         ......................... SF_DC_01 passed test kccevent
      Starting test: systemlog
         ......................... SF_DC_01 passed test systemlog
      Starting test: VerifyReferences
         ......................... SF_DC_01 passed test VerifyReferences

   Running partition tests on : TAPI3Directory
      Starting test: CrossRefValidation
         ......................... TAPI3Directory passed test CrossRefValidation

      Starting test: CheckSDRefDom
         ......................... TAPI3Directory passed test CheckSDRefDom

   Running partition tests on : ForestDnsZones
      Starting test: CrossRefValidation
         ......................... ForestDnsZones passed test CrossRefValidation

      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom

   Running partition tests on : DomainDnsZones
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test CrossRefValidation

      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom

   Running partition tests on : Schema
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom

   Running partition tests on : Configuration
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom

   Running partition tests on : stfrancis
      Starting test: CrossRefValidation
         ......................... stfrancis passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... stfrancis passed test CheckSDRefDom

   Running enterprise tests on : stfrancis.local
      Starting test: Intersite
         ......................... stfrancis.local passed test Intersite
      Starting test: FsmoCheck
         ......................... stfrancis.local passed test FsmoCheck

thanks a bunch
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
ronrodAuthor Commented:
i tried moving the fsmo rolls. the domain naming master and  schema master would not change to server 2008r2 domain controller
0
 
ronrodAuthor Commented:
seizing the roles looks like a plausible answer.
http://support.microsoft.com/kb/255504
would you agree?  
Ron
0
 
ronrodAuthor Commented:
I can only manage group policy through 2003 server. cannot move it to 2008r2.
0
 
ronrodAuthor Commented:
good quick initial feedback but no response afterward. did send me in the right direction though.
thanks,
Ron
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now