Quantcast
Channel: Directory Services forum
Viewing all articles
Browse latest Browse all 31638

Clean up AD of old server & clean metadata

$
0
0

Hi,

I've inherited quite a server mess and I'm hoping that the AD experts in this group might help.  Currently I have 2 servers and one of them has AD on it and the other does not.  The issue I'm seeing is that when I do a dcdiag I find references to an old server that doesn't exist.  Does anyone know how I go about cleaning this stuff out before I got and add AD to this new server?   

I've got 2 servers configured as follows

mailserv - W2k8 R2 Standard - Windows AD Domain Controller
dataserv2 - W2k8 Standard - Non AD DC (I'd like to add it here)
server2 - I'm assuming this is a server that my predecessor created years ago and long since retired.  But it could also be this newer server (dataserv2) before a rename. 

I've attached a copy of the dcdiag output here for you below:

Directory Server Diagnosis


Performing initial setup:

   Trying to find home server...

   Home Server = mailserv

   * Identified AD Forest.
   Done gathering initial info.


Doing initial required tests


   Testing server: Default-First-Site-Name\MAILSERV

      Starting test: Connectivity

         ......................... MAILSERV passed test Connectivity


   Testing server: Default-First-Site-Name\SERVER2

      Starting test: Connectivity

         Ldap search capabality attribute search failed on server SERVER2,

         return value = 81
         ......................... SERVER2 failed test Connectivity



Doing primary tests


   Testing server: Default-First-Site-Name\MAILSERV

      Starting test: Advertising

         ......................... MAILSERV 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.
         ......................... MAILSERV passed test FrsEvent

      Starting test: DFSREvent

         ......................... MAILSERV passed test DFSREvent

      Starting test: SysVolCheck

         ......................... MAILSERV passed test SysVolCheck

      Starting test: KccEvent

         ......................... MAILSERV passed test KccEvent

      Starting test: KnowsOfRoleHolders

         ......................... MAILSERV passed test KnowsOfRoleHolders

      Starting test: MachineAccount

         ......................... MAILSERV passed test MachineAccount

      Starting test: NCSecDesc

         ......................... MAILSERV passed test NCSecDesc

      Starting test: NetLogons

         ......................... MAILSERV passed test NetLogons

      Starting test: ObjectsReplicated

         ......................... MAILSERV passed test ObjectsReplicated

      Starting test: Replications

         [Replications Check,MAILSERV] A recent replication attempt failed:

            From SERVER2 to MAILSERV

            Naming Context: CN=Schema,CN=Configuration,DC=example,DC=com

            The replication generated an error (1753):

            There are no more endpoints available from the endpoint mapper.

            The failure occurred at 2014-10-17 14:48:40.

            The last success occurred at 2011-06-23 17:56:45.

            29095 failures have occurred since the last success.

            The directory on SERVER2 is in the process.

            of starting up or shutting down, and is not available.

            Verify machine is not hung during boot.

         [Replications Check,MAILSERV] A recent replication attempt failed:

            From SERVER2 to MAILSERV

            Naming Context: CN=Configuration,DC=example,DC=com

            The replication generated an error (1753):

            There are no more endpoints available from the endpoint mapper.

            The failure occurred at 2014-10-17 14:48:40.

            The last success occurred at 2012-03-07 20:58:21.

            22896 failures have occurred since the last success.

            The directory on SERVER2 is in the process.

            of starting up or shutting down, and is not available.

            Verify machine is not hung during boot.

         [Replications Check,MAILSERV] A recent replication attempt failed:

            From SERVER2 to MAILSERV

            Naming Context: DC=example,DC=com

            The replication generated an error (1753):

            There are no more endpoints available from the endpoint mapper.

            The failure occurred at 2014-10-17 14:48:40.

            The last success occurred at 2011-06-23 18:15:25.

            29095 failures have occurred since the last success.

            The directory on SERVER2 is in the process.

            of starting up or shutting down, and is not available.

            Verify machine is not hung during boot.

         ......................... MAILSERV failed test Replications

      Starting test: RidManager

         ......................... MAILSERV passed test RidManager

      Starting test: Services

         ......................... MAILSERV passed test Services

      Starting test: SystemLog

         An Error Event occurred.  EventID: 0x00000422

            Time Generated: 10/17/2014   14:21:25

            Event String:

            The processing of Group Policy failed. Windows attempted to read the file \\example\sysvol\example\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: 0x00000422

            Time Generated: 10/17/2014   14:26:28

            Event String:

            The processing of Group Policy failed. Windows attempted to read the file \\example\sysvol\example\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: 0x00000422

            Time Generated: 10/17/2014   14:31:30

            Event String:

            The processing of Group Policy failed. Windows attempted to read the file \\example\sysvol\example\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: 0x00000422

            Time Generated: 10/17/2014   14:36:32

            Event String:

            The processing of Group Policy failed. Windows attempted to read the file \\example\sysvol\example\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: 0x00000422

            Time Generated: 10/17/2014   14:41:34

            Event String:

            The processing of Group Policy failed. Windows attempted to read the file \\example\sysvol\example\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: 0x00000422

            Time Generated: 10/17/2014   14:46:36

            Event String:

            The processing of Group Policy failed. Windows attempted to read the file \\example\sysvol\example\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: 0x40000004

            Time Generated: 10/17/2014   14:51:38

            Event String:

            The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server dataserv2$. The target name used was cifs/server2.example. This indicates that the target server failed to decrypt the ticket provided by the client. This can occur when the target server principal name (SPN) is registered on an account other than the account the target service is using. Please ensure that the target SPN is registered on, and only registered on, the account used by the server. This error can also happen when the target service is using a different password for the target service account than what the Kerberos Key Distribution Center (KDC) has for the target service account. Please ensure that the service on the server and the KDC are both updated to use the current password. If the server name is not fully qualified, and the target domain (BELMONTDENTAL.COM) is different from the client domain (BELMONTDENTAL.COM), check if there are identically named server accounts in these two domains, or use the fully-qualified name to identify the server.

         An Error Event occurred.  EventID: 0x00000422

            Time Generated: 10/17/2014   14:51:38

            Event String:

            The processing of Group Policy failed. Windows attempted to read the file \\example\sysvol\example\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: 0x00000422

            Time Generated: 10/17/2014   14:56:40

            Event String:

            The processing of Group Policy failed. Windows attempted to read the file \\example\sysvol\example\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: 0x00000422

            Time Generated: 10/17/2014   15:01:43

            Event String:

            The processing of Group Policy failed. Windows attempted to read the file \\example\sysvol\example\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: 0x00000422

            Time Generated: 10/17/2014   15:03:59

            Event String:

            The processing of Group Policy failed. Windows attempted to read the file \\example\sysvol\example\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: 0x00000422

            Time Generated: 10/17/2014   15:06:45

            Event String:

            The processing of Group Policy failed. Windows attempted to read the file \\example\sysvol\example\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: 0x00000422

            Time Generated: 10/17/2014   15:11:47

            Event String:

            The processing of Group Policy failed. Windows attempted to read the file \\example\sysvol\example\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: 0x00000422

            Time Generated: 10/17/2014   15:16:49

            Event String:

            The processing of Group Policy failed. Windows attempted to read the file \\example\sysvol\example\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:


         ......................... MAILSERV failed test SystemLog

      Starting test: VerifyReferences

         ......................... MAILSERV passed test VerifyReferences


   Testing server: Default-First-Site-Name\SERVER2

      Skipping all tests, because server SERVER2 is not responding to directory

      service requests.




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

      Starting test: CheckSDRefDom

         ......................... example passed test CheckSDRefDom

      Starting test: CrossRefValidation

         ......................... example passed test CrossRefValidation


   Running enterprise tests on : example

      Starting test: LocatorCheck

         ......................... example passed test LocatorCheck

      Starting test: Intersite

         ......................... example passed test Intersite

Any help is appreciated...

TIA,
J



Viewing all articles
Browse latest Browse all 31638

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>