unexpected UUIDs showing up in repadmin /showvector output

[Guest]

I have a single mixed-mode domain spanning two sites. There are two DCs in
Default-First-Site-Name, named DC01 and DC02 and one DC in OTHER-SITE named
OTHERDC01.

I'm executing this command on a Windows 2000 SP4 domain controller:
C:\Documents and Settings\administrator>repadmin /showvector
dc=mydomain,dc=local dc01.mydomain.local

The documentation I've read leads me to believe I should expect to see
information that looks like this:
Default-First-Site-Name\DC01 @ USN 1840772
OTHER-SITE\OTHERDC01 @ USN 309257
Default-First-Site-Name\DC02 @ USN 1847067

but, I'm seeing this instead (xxxx used for readability):

C:\Documents and Settings\administrator>repadmin /showvector
dc=mydomain,dc=local dc01.mydomain.local
Default-First-Site-Name\DC01 @ USN 1840772
3df422dd-xxxx-xxxx-xxxx-xxxxxxxxxxxxxxxx @ USN 16238
71f39933-xxxx-xxxx-xxxx-xxxxxxxxxxxxxxxx @ USN 5012
OTHER-SITE\OTHERDC01 @ USN 309257
Default-First-Site-Name\DC02 @ USN 1847067
ad432463-xxxx-xxxx-xxxx-xxxxxxxxxxxxxxxx @ USN 37438
b1d627e5-xxxx-xxxx-xxxx-xxxxxxxxxxxxxxxx @ USN 215491

We're preparing to upgrade to Windows2003 on all three domain controllers in
the next couple of weeks, and the presence of these additional UUIDs has me
concerned. Is this just old/stale/retired information? (the USNs don't
increment for these entries). Do I need to remove these entries before our
upgrade? If so, how?

Also worth noting, when I do repadmin /showsig for each DC, it shows only
the (single) current signature and no retired signatures.

 

[Joe Richards [MVP]]

That is fine, you don't want to and can't clean it up. The UTDV maintains an
entry for every DC that ever existed in the forest. It is used for replication
dampening. In Dec/Jan Active Directory 3rd Edition from O'Reilly will be
available and chapter 5 walks through what the UTDV is all about and how it is
used. It is also in the previous editions but I significantly updated that
chapter when I refreshed the book for the 3rd edition.

joe

 

[Guest]

Great - thanks for the quick and to-the-point answer. Looking forward to
seeing your new book

 

[Jorge_de_Almeida_Pinto]

I have a single mixed-mode domain spanning two sites. There
are two DCs in
Default-First-Site-Name, named DC01 and DC02 and one DC in
OTHER-SITE named
OTHERDC01.

I'm executing this command on a Windows 2000 SP4 domain
controller:
Cocuments and Settingsadministrator>repadmin /showvector
dc=mydomain,dc=local dc01.mydomain.local

The documentation I've read leads me to believe I should
expect to see
information that looks like this:
Default-First-Site-NameDC01 @ USN 1840772
OTHER-SITEOTHERDC01 @ USN 309257
Default-First-Site-NameDC02 @ USN 1847067

but, I'm seeing this instead (xxxx used for readability):

Cocuments and Settingsadministrator>repadmin /showvector
dc=mydomain,dc=local dc01.mydomain.local
Default-First-Site-NameDC01 @ USN 1840772
3df422dd-xxxx-xxxx-xxxx-xxxxxxxxxxxxxxxx @ USN 16238
71f39933-xxxx-xxxx-xxxx-xxxxxxxxxxxxxxxx @ USN 5012
OTHER-SITEOTHERDC01 @
USN 309257
Default-First-Site-NameDC02 @ USN 1847067
ad432463-xxxx-xxxx-xxxx-xxxxxxxxxxxxxxxx @ USN 37438
b1d627e5-xxxx-xxxx-xxxx-xxxxxxxxxxxxxxxx @ USN 215491

We're preparing to upgrade to Windows2003 on all three domain
controllers in
the next couple of weeks, and the presence of these additional
UUIDs has me
concerned. Is this just old/stale/retired information? (the
USNs don't
increment for these entries). Do I need to remove these
entries before our
upgrade? If so, how?

Also worth noting, when I do repadmin /showsig for each DC, it
shows only
the (single) current signature and no retired signatures.

use the w2k3 version (on a w2k3 server) as that one might show you if
they are retired

repadmin /showutdvec <DC> <NC>

follow the steps in the following articles to upgrade to w2k3/e2k3:
MS-KBQ314649_W2K3 ADPREP Command Causes Mangled Attributes in W2K
Forests That Contain E2K Servers
MS-KBQ325379_How to Upgrade Windows 2000 Domain Controllers to Windows
Server 2003
MS-KBQ555040_Common Mistakes When Upgrade Windows 2000 Domain To
Windows 2003
MS-KBQ324392_Enhancements to Adprep.exe in Windows Server 2003 Service
Pack 1 and in hotfix 324392
Also see:
http://www.microsoft.com/technet/pr...elp/bc5ebbdb-a8d7-4761-b38a-e207baa73419.mspx)
http://www.petri.co.il/windows_2003_adprep.htm
MS-KBQ555038_How to enable Windows 98-ME-NT clients to logon to
Windows 2003 based Domains
MS-KBQ887426_Incorrect Schema extension for OS X prevents ForestPrep
from completing in Windows 2000
MS-KBQ555262_Common Mistakes When Upgrading Exchange 5.5-2000 To a
Exchange 2003
MS-KBQ822942_Considerations When You Upgrade to Exchange Server 2003