site links

  • Thread starter Thread starter Jason
  • Start date Start date
J

Jason

We have a full mesh network with 13 sites. Most of the sites are in the
defaultipsitelink. The sites that are not,have
servers that do not exsit any more and have to be removed manually.
My question is, I still see errors in the eventviewer on domain controllers
that still try to replicate to sites that are not in the defaultipsitelink?
 
I suggest to keep all sites within the defaultipsitelink, modify the cost of
the defaultipsitelink to 30150 that will ensure it never use it
defaultsitelink expect if nothing other is available. What are the errors?
can you please provide them here? Domain Controllers may have to talk to
each other cross sites that's not within a site link if there is no other
replication path. Review your replication topology so this can't be a case.

--
Regards
Christoffer Andersson
Microsoft MVP - Directory Services

No email replies please - reply in the newsgroup
 
Hi, 1550 (Labtest) is a site with a server called labtest_nt that does not
exsit anymore. It was removed with out doing a dcpromo.

Event Type: Error
Event Source: NTDS KCC
Event Category: (1)
Event ID: 1550
Date: 3/4/2005
Time: 2:42:27 PM
User: N/A
Computer: EPC_NT
Description:
The site CN=Labtest,CN=Sites,CN=Configuration,DC=quantum,DC=org has no child
NTDS Site Settings object. Please use the Active Directory Sites and
Services snap-in to create an NTDS Site Settings object for this site.


Is this related to 1550 ?

Event Type: Error
Event Source: NTDS KCC
Event Category: (1)
Event ID: 1311
Date: 3/4/2005
Time: 2:42:27 PM
User: N/A
Computer: EPC_NT
Description:
The Directory Service consistency checker has determined that either (a)
there is not enough physical connectivity published via the Active Directory
Sites and Services Manager to create a spanning tree connecting all the
sites containing the Partition DC=quantum,DC=org, or (b) replication cannot
be performed with one or more critical servers in order for changes to
propagate across all sites (most often due to the servers being
unreachable).

For (a), please use the Active Directory Sites and Services Manager to do
one of the following:
1. Publish sufficient site connectivity information such that the system can
infer a route by which this Partition can reach this site. This option is
preferred.
2. Add an ntdsConnection object to a Domain Controller that contains the
Partition DC=quantum,DC=org in this site from a Domain Controller that
contains the same Partition in another site.

For (b), please see previous events logged by the NTDS KCC source that
identify the servers that could not be contacted.




thx jason
 
Here are the basics for removing dead DCs,
and sometimes you have to also perform an
ADSIEdit (usually if you tried some other
methods to delete the DC unsucessfully.)

NTDS metadata cleanup

Search Google for:

[ NTDS "metadata cleanup" remove DC Domain ]

No need to add either site:microsoft.com OR microsoft:
since the NTDS and other terms make it Microsoft specific
by itself.

Unless you WISH to restrict answers to the site:microsoft.com
for some reason.

[ NTDS "metadata cleanup" remove DC Domain site:microsoft.com ]

Key points to NOTE when doing the metadata cleanup:

You CONNECT to a WORKING DC.
You SELECT the missing/dead DC or DOMAIN

'Connect' and 'Select' are technical terms in this context.
 
Start with have a look at this KB below:

How to remove data in Active Directory after an unsuccessful domain
controller demotion
http://support.microsoft.com/kb/216498

--
Regards
Christoffer Andersson
Microsoft MVP - Directory Services

No email replies please - reply in the newsgroup
 
Back
Top