Thanks James, but I had multiple links set up for this with three different
DC's.  The odd thing is that it really wasn't an issue until recently.


On 6/29/05 12:09 PM, "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]> wrote:

> Hi Mark
> 
> Are the other DCs replicating with anybody else?  Has the updated
> configuration reached them yet?  If their only replication partners were
> that one DC they may not know it has been demoted.  In that case you should
> be able to create a manual connection to a DC that knows the dead DC is
> gone, let it replicate and update itself, then let the KCC find another
> path.  We had the same problem when a hub site DC with multiple spokes got
> changed.  The hubsite replicated the changes to a single DC during demotion
> but because the other DCs were configured to only replicate with the
> hubsite they did not know the hub DC was gone until the hub DC told them it
> was gone.
> 
> Regards;
> 
> James R. Day
> Active Directory Core Team
> Office of the Chief Information Officer
> National Park Service
> (202) 354-1464 (direct)
> (202) 371-1549 (fax)
> [EMAIL PROTECTED]
> 
> 
> |---------+---------------------------------->
> |         |           Mark Orlando           |
> |         |           <[EMAIL PROTECTED]>  |
> |         |           Sent by:               |
> |         |           [EMAIL PROTECTED]|
> |         |           tivedir.org            |
> |         |                                  |
> |         |                                  |
> |         |           06/29/2005 11:57 AM AST|
> |         |           Please respond to      |
> |         |           ActiveDir              |
> |---------+---------------------------------->
>> -----------------------------------------------------------------------------
>> -------------------------------------------------|
>   |              
> |
>   |       To:       Active Directory Mailing List
> <[email protected]>
> |
>   |       cc:       (bcc: James Day/Contractor/NPS)
> |
>   |       Subject:  [ActiveDir] Can't get rid of old DC in Sites and Services
> |
>> -----------------------------------------------------------------------------
>> -------------------------------------------------|
> 
> 
> 
> 
> I have a DC, which used to have all FISMO roles, that is causing me grief.
> The server had issues so I put the roles on another DC and demoted it to a
> member server.  I then deleted all of the static site links that I had set
> up and let AD configure them automatically.  It has been working fine for a
> while, but now, for some reason, this server is still being seen as a DC
> because some of the other DC=B9s are still trying to replicate with it.  I
> went into Sites and Services and deleted the links, but it won=B9t actually
> let me deleted the server container for that DC that isn=B9t a DC anymore.
> I=
> t
> says it can=B9t delete the DSA object.  How the heck do I get rid of this
> DC
> in AD once and for all.
> 
> Thanks,
> Mark Orlando
> IT Dept.
> Linden Public Schools
> 
> List info   : http://www.activedir.org/List.aspx
> List FAQ    : http://www.activedir.org/ListFAQ.aspx
> List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/


List info   : http://www.activedir.org/List.aspx
List FAQ    : http://www.activedir.org/ListFAQ.aspx
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/

Reply via email to