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

Migration from 2003 SBS to 2008 R2 STD, dcdiag errors

I am migrating from a SBS 2003 to a 2008 R2 Std server, have done all adpreps, dns, and global catalog. When runnig dcdiag I continually get these errors after fixiing all Schannel errors.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Administrator.ssh>dcdiag

Directory Server Diagnosis

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

Doing initial required tests

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

Doing primary tests

   Testing server: Default-First-Site-Name\SERVER2
      Starting test: Advertising
         Warning: DsGetDcName returned information for \\SERVER.ssh.local, when
         we were trying to reach SERVER2.
         SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.
         ......................... SERVER2 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.
         ......................... SERVER2 passed test FrsEvent
      Starting test: DFSREvent
         ......................... SERVER2 passed test DFSREvent
      Starting test: SysVolCheck
         ......................... SERVER2 passed test SysVolCheck
      Starting test: KccEvent
         ......................... SERVER2 passed test KccEvent
      Starting test: KnowsOfRoleHolders
         ......................... SERVER2 passed test KnowsOfRoleHolders
      Starting test: MachineAccount
         ......................... SERVER2 passed test MachineAccount
      Starting test: NCSecDesc
         ......................... SERVER2 passed test NCSecDesc
      Starting test: NetLogons
         Unable to connect to the NETLOGON share! (\\SERVER2\netlogon)
         [SERVER2] An net use or LsaPolicy operation failed with error 67,
         The network name cannot be found..
         ......................... SERVER2 failed test NetLogons
      Starting test: ObjectsReplicated
         ......................... SERVER2 passed test ObjectsReplicated
      Starting test: Replications
         ......................... SERVER2 passed test Replications
      Starting test: RidManager
         ......................... SERVER2 passed test RidManager
      Starting test: Services
         ......................... SERVER2 passed test Services
      Starting test: SystemLog
         An error event occurred.  EventID: 0x00000449
            Time Generated: 03/26/2011   20:16:58
            Event String:
            The processing of Group Policy failed. Windows could not determine t
he computer account to enforce Group Policy settings. This may be transient. Gro
up Policy settings, including computer configuration, will not be enforced for t
his computer.
         An error event occurred.  EventID: 0x00009018
            Time Generated: 03/26/2011   20:17:13
            Event String:
            The following fatal alert was generated: 10. The internal error stat
e is 10.
         An error event occurred.  EventID: 0x00009018
            Time Generated: 03/26/2011   20:17:14
            Event String:
            The following fatal alert was generated: 10. The internal error stat
e is 10.
         An error event occurred.  EventID: 0x00000449
            Time Generated: 03/26/2011   20:18:10
            Event String:
            The processing of Group Policy failed. Windows could not determine t
he computer account to enforce Group Policy settings. This may be transient. Gro
up Policy settings, including computer configuration, will not be enforced for t
his computer.
         An error event occurred.  EventID: 0x00000449
            Time Generated: 03/26/2011   20:23:11
            Event String:
            The processing of Group Policy failed. Windows could not determine t
he computer account to enforce Group Policy settings. This may be transient. Gro
up Policy settings, including computer configuration, will not be enforced for t
his computer.
         An error event occurred.  EventID: 0x00000449
            Time Generated: 03/26/2011   20:28:11
            Event String:
            The processing of Group Policy failed. Windows could not determine t
he computer account to enforce Group Policy settings. This may be transient. Gro
up Policy settings, including computer configuration, will not be enforced for t
his computer.
         An error event occurred.  EventID: 0x00000449
            Time Generated: 03/26/2011   20:33:12
            Event String:
            The processing of Group Policy failed. Windows could not determine t
he computer account to enforce Group Policy settings. This may be transient. Gro
up Policy settings, including computer configuration, will not be enforced for t
his computer.
         An error event occurred.  EventID: 0x00000449
            Time Generated: 03/26/2011   20:38:12
            Event String:
            The processing of Group Policy failed. Windows could not determine t
he computer account to enforce Group Policy settings. This may be transient. Gro
up Policy settings, including computer configuration, will not be enforced for t
his computer.
         An error event occurred.  EventID: 0x00000449
            Time Generated: 03/26/2011   20:43:13
            Event String:
            The processing of Group Policy failed. Windows could not determine t
he computer account to enforce Group Policy settings. This may be transient. Gro
up Policy settings, including computer configuration, will not be enforced for t
his computer.
         An error event occurred.  EventID: 0x00000449
            Time Generated: 03/26/2011   20:48:14
            Event String:
            The processing of Group Policy failed. Windows could not determine t
he computer account to enforce Group Policy settings. This may be transient. Gro
up Policy settings, including computer configuration, will not be enforced for t
his computer.
         An error event occurred.  EventID: 0x00000449
            Time Generated: 03/26/2011   20:53:14
            Event String:
            The processing of Group Policy failed. Windows could not determine t
he computer account to enforce Group Policy settings. This may be transient. Gro
up Policy settings, including computer configuration, will not be enforced for t
his computer.
         An error event occurred.  EventID: 0x00000449
            Time Generated: 03/26/2011   20:58:15
            Event String:
            The processing of Group Policy failed. Windows could not determine t
he computer account to enforce Group Policy settings. This may be transient. Gro
up Policy settings, including computer configuration, will not be enforced for t
his computer.
         An error event occurred.  EventID: 0x00000449
            Time Generated: 03/26/2011   21:03:15
            Event String:
            The processing of Group Policy failed. Windows could not determine t
he computer account to enforce Group Policy settings. This may be transient. Gro
up Policy settings, including computer configuration, will not be enforced for t
his computer.
         An error event occurred.  EventID: 0x00000449
            Time Generated: 03/26/2011   21:08:16
            Event String:
            The processing of Group Policy failed. Windows could not determine t
he computer account to enforce Group Policy settings. This may be transient. Gro
up Policy settings, including computer configuration, will not be enforced for t
his computer.
         An error event occurred.  EventID: 0x00000449
            Time Generated: 03/26/2011   21:13:16
            Event String:
            The processing of Group Policy failed. Windows could not determine t
he computer account to enforce Group Policy settings. This may be transient. Gro
up Policy settings, including computer configuration, will not be enforced for t
his computer.
         ......................... SERVER2 failed test SystemLog
      Starting test: VerifyReferences
         ......................... SERVER2 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 : ssh
      Starting test: CheckSDRefDom
         ......................... ssh passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... ssh passed test CrossRefValidation

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

C:\Users\Administrator.ssh>

            Feel like I've been running in circles and could use some help, thanks
0
AdminTSU
Asked:
AdminTSU
  • 2
  • 2
1 Solution
 
AdminTSUAuthor Commented:
Also I haven't yet moved FSMOs or done Operations Management moves yet
0
 
arnoldCommented:
It seems that the replication has not completed yet.
You should run dcdiag from the first DC rather than from the one you just promoted.
Check the event logs on the current server to see what is going on.
0
 
AdminTSUAuthor Commented:
Ran the dcdiag from original SBS 2003 server still running as a DC, passed the diag except for SYSVOL share and frsevent test;

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator>dcdiag

Domain Controller Diagnosis

Performing initial setup:
   Done gathering initial info.

Doing initial required tests

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

Doing primary tests

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

   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 : ssh
      Starting test: CrossRefValidation
         ......................... ssh passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... ssh passed test CheckSDRefDom

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

C:\Documents and Settings\Administrator>
0
 
arnoldCommented:
Check the FRS events on server2 and server to see whether you have an errors that prevents the replication.  Check within the sites and trusts interface the configuration for the interactions.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

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