Remove old failed server from ADSI
in [Microsoft Exchange]
|
Prev: public or shared calendar with automated appointment feed fromusers (Exch 2007)
Next: cannot send from our exchange server to hotmail or windows liv
From: Julien Demarey on 27 Apr 2010 06:16 Hi, I actually work with an 2K3 R2 server SERVER2. This server is the only DC of the domain. But I found with frsdiag and ADSI old records about SERVER1 that no longer exists. This cause DFRS issue and Exchange pb. I found a solution for the DFRS with adsutil clean metadata. But how to remove olds records from ADSI in the following path : CN=Servers,CN=Premier groupe administratif,CN=Administrative Groups,CN=DOMAIN NAME,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=DOMAIN NAME,DC=com Thanks in advance. -- Julien Demarey
From: John Oliver, Jr. [MVP] on 27 Apr 2010 14:47 This is more an AD issue rather than Exchange but you will need to perform a Metadata Cleanup from NTDSUtil if the DC was not removed properly. You will then need to cleanup your DNS Records from DNS Management Console. -- John Oliver, Jr MCSE, MCT, CCNA Exchange MVP 2010 Microsoft Certified Partner "Julien Demarey" <JulienDemarey(a)discussions.microsoft.com> wrote in message news:0DCDC3A7-089A-4230-BD19-3884D4F1A525(a)microsoft.com... > Hi, > I actually work with an 2K3 R2 server SERVER2. > This server is the only DC of the domain. But I found with frsdiag and > ADSI > old records about SERVER1 that no longer exists. > This cause DFRS issue and Exchange pb. > I found a solution for the DFRS with adsutil clean metadata. > But how to remove olds records from ADSI in the following path : > CN=Servers,CN=Premier groupe administratif,CN=Administrative > Groups,CN=DOMAIN NAME,CN=Microsoft > Exchange,CN=Services,CN=Configuration,DC=DOMAIN NAME,DC=com > > Thanks in advance. > > -- > Julien Demarey >
From: Julien Demarey on 29 Apr 2010 16:25
Thanks for the answer. He has been partially removed from the AD. He is not "visible" in ntdsutil. That's why I can't use the metadata cleanup. -- Julien Demarey "John Oliver, Jr. [MVP]" wrote: > This is more an AD issue rather than Exchange but you will need to perform a > Metadata Cleanup from NTDSUtil if the DC was not removed properly. You > will then need to cleanup your DNS Records from DNS Management Console. > > -- > John Oliver, Jr > MCSE, MCT, CCNA > Exchange MVP 2010 > Microsoft Certified Partner > > > "Julien Demarey" <JulienDemarey(a)discussions.microsoft.com> wrote in message > news:0DCDC3A7-089A-4230-BD19-3884D4F1A525(a)microsoft.com... > > Hi, > > I actually work with an 2K3 R2 server SERVER2. > > This server is the only DC of the domain. But I found with frsdiag and > > ADSI > > old records about SERVER1 that no longer exists. > > This cause DFRS issue and Exchange pb. > > I found a solution for the DFRS with adsutil clean metadata. > > But how to remove olds records from ADSI in the following path : > > CN=Servers,CN=Premier groupe administratif,CN=Administrative > > Groups,CN=DOMAIN NAME,CN=Microsoft > > Exchange,CN=Services,CN=Configuration,DC=DOMAIN NAME,DC=com > > > > Thanks in advance. > > > > -- > > Julien Demarey > > |