there are to ways to remove DCs from AD:
(1) demote and cleanup server object manually
(2) just shutdown the DC (never to be connected again!), perform a metadata
cleanup and cleanup the server object manually
to answer your question...
YES, you should cleanup the AD metadata of DCs that still exist in AD but
are not alive anymore.
--
Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)
# Jorge de Almeida Pinto # MVP Windows Server - Directory Services
BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
------------------------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always test before implementing!
------------------------------------------------------------------------------------------
#################################################
#################################################
------------------------------------------------------------------------------------------
Post by BJorge,
I thought these were objectGIODs from the NTDS Settings, but when I found
the DNS Alias (from Property of NTDS Settings on each DC), none of the GUIDs
are matched between DNS Alias and the one showing on repadmin /showvector.
Also, when I found the CNAME in DNS (_msdcs), they are completelly matched
with DNS Alias (Property of NTDS Setting).
We removed bunch of DC before and we did not follow the correct process (we
just ran dcpromo and did not clean up from NTDS Utility nor adsiedit), so I
thought those removed DCs informations are still remained somewhere.
Especially, those time and dates were never updated.
Don't I need to worry about it??
Post by Jorge de Almeida Pinto [MVP]those are not server GUIDs (or better yet: DSA GUIDs or objectGUIDs from the
NTDS Settings object which identify a DC).
those GUIDs are Invocation IDs which identify database instances on DCs.
Those Invocation IDs are changed when a DC is restored or when an app NC is
sourced onto the DC.
DSA GUIDs never change during the lifetime of a DC, only when demoting
in DNS you will find DSA GUIDs, NOT invocation IDs
--
Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)
# Jorge de Almeida Pinto # MVP Windows Server - Directory Services
BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
------------------------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always test before implementing!
------------------------------------------------------------------------------------------
#################################################
#################################################
------------------------------------------------------------------------------------------
Post by Jorge SilvaHi
These numbers identifies the servers GUID, these servers aren't in use
anymore, and did you remove them from AD using Dcpromo?
If yes, then just delete these GUID from DNS.
--
I hope that the information above helps you
Good Luck
Jorge Silva
MCSA
Systems Administrator
Post by BWhen running repadmin /showvector dc=abc,dc=com, it shows strange GUIDs
07:51:00
09:46:11
How can I get rid of it?