Problems with removing DC from AD.   

I have upgraded from NT4 domain to Windows 2003 AD domain... this was
done on NT4PDC computer named NT-DC.

Upgrade was a complete success.

After setting other two DC on the same location and one DC on each
remote location, a have transfered all FSMO roles to other DCs from
NT-DC.

Two days after transfering FSMO roles from NT-DC I have started DCPROMO
to demote NT-DC as a domain controller.

DCPROMO stated succsesfully demotion of NT-DC.

Few days later NT-DC was removed from network.

What bothers me is result that dcdiag /v returns the following:
**************************************************************
      Starting test: Replications
         * Replications Check
         * Replication Latency Check
            DC=ForestDnsZones,DC=domain,DC=local
               Latency information for 2 entries in the vector were
ignored.
                  2 were retired Invocations.  0 were either: read-only
replicas
 and are not verifiably latent, or dc's no longer replicating this nc.
0 had no
 latency information (Win2K DC).
            DC=DomainDnsZones,DC=domain,DC=local
               Latency information for 2 entries in the vector were
ignored.
                  2 were retired Invocations.  0 were either: read-only
replicas
 and are not verifiably latent, or dc's no longer replicating this nc.
0 had no
 latency information (Win2K DC).
            CN=Schema,CN=Configuration,DC=domain,DC=local
               Latency information for 2 entries in the vector were
ignored.
                  2 were retired Invocations.  0 were either: read-only
replicas
 and are not verifiably latent, or dc's no longer replicating this nc.
0 had no
 latency information (Win2K DC).
            CN=Configuration,DC=domain,DC=local
               Latency information for 2 entries in the vector were
ignored.
                  2 were retired Invocations.  0 were either: read-only
replicas
 and are not verifiably latent, or dc's no longer replicating this nc.
0 had no
 latency information (Win2K DC).
            DC=domain,DC=local
               Latency information for 2 entries in the vector were
ignored.
                  2 were retired Invocations.  0 were either: read-only
replicas
 and are not verifiably latent, or dc's no longer replicating this nc.
0 had no
 latency information (Win2K DC).
         ......................... AD-DC passed test Replications
**************************************************************

Few days after I have checked Sites&Services and NT-DC was still
listed... so I have removed NT-DC from manually.

Few days later I have checked DNS and NT-DC had still entries in... I
have removed all of them manually.

But this problem still persist.

Does anyone have a clue how to get rid of this.

Thanks in advance
Herbert Knavs

date: 12 May 2005 02:18:51 -0700   author:   Herbert Knavs