RE: repadmin /showutdvec indicates orphaned DC?

Hi ,

I think this behavior is normal and does not relate to errors in active
directory .

From your description, it relates to previous decommissions and will
continue to remain as we cannot remove these entries because they at some
point in time have originated changes. It is safe to ignore them though as
they are a result of Invocation ID changes or DC's being demoted or rebuilt
and do not affect the health of the topology.

Thanks.

Best regards,

Vincent Xu
Microsoft Online Partner Support

======================================================
Get Secure! - www.microsoft.com/security
======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties,and confers no rights.
======================================================



--------------------
Thread-Topic: repadmin /showutdvec indicates orphaned DC?
thread-index: AcbvAH2xlHilP4mlTz+7YEz5nXGf7g==
X-WBNR-Posting-Host: 24.151.67.6
From: =?Utf-8?B?Qm9i?= <86c6c2e6-2146512712@xxxxxxxxxxxxxx>
Subject: repadmin /showutdvec indicates orphaned DC?
Date: Fri, 13 Oct 2006 12:48:01 -0700
Lines: 103
Message-ID: <A7A4C6AC-914C-47E2-820A-26426ACF457F@xxxxxxxxxxxxx>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
Newsgroups: microsoft.public.windows.server.active_directory
Path: TK2MSFTNGXA01.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.active_directory:88976
NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
X-Tomcat-NG: microsoft.public.windows.server.active_directory

Hi,

I'm using my DC1 (the first built DC and also the FSMO), to run "repadmin
/showutdvec". It finds three DC's with GUID's in hex and my two working
DC's
in strings. I have a single forest with a single domain and everything
is
Windows Server 2K3.

What are these GUID's in hex all about and is this an indication of a
problem?

I'm guessing the DC's with GUID's in hex are orphaned DC's and am using
the
procedure found at: http://support.microsoft.com/?id=216498 (metadata
cleanup)
to try and resolve it. But when I "list servers in site", all I see are
my
two working DC's so I apparently can't use metadata cleanup to resolve
this.

Are there any other techniques? Is there a way to use adsiedit.msc to
search/query AD for these GUID's in hex?

Below are my screen outputs. Thanks!

My two working DC's are:
DC1= "RC-SERVER-1"
DC2= "RC-SERVER-2"

----------------------------------------------------------------------------
------------------
D:\>repadmin /showutdvec * cn=configuration,dc=ComputerCreations,dc=local

repadmin running command /showutdvec against server
rc-server-1.ComputerCreations.local

Caching GUIDs.
..
1ae9b171-7fc6-43cc-ab6b-93c2fd4f139f @ USN 74415 @ Time 2006-10-10
11:52:02
3e04644c-30f3-48f4-8d27-80b094b33fd0 @ USN 74143 @ Time 2006-10-10
09:18:15
41d10ea1-1fe9-4eb2-8ca0-5b26c771008b @ USN 606310 @ Time 2006-06-17
16:09:13
Default-First-Site-Name\RC-SERVER-1 @ USN 1278273 @ Time 2006-10-12
09:51:12
Default-First-Site-Name\RC-SERVER-2 @ USN 1155290 @ Time 2006-10-12
09:46:11

repadmin running command /showutdvec against server
RC-SERVER-2.ComputerCreations.local

Caching GUIDs.
..
1ae9b171-7fc6-43cc-ab6b-93c2fd4f139f @ USN 74415 @ Time 2006-10-10
11:52:02
3e04644c-30f3-48f4-8d27-80b094b33fd0 @ USN 74143 @ Time 2006-10-10
09:18:15
41d10ea1-1fe9-4eb2-8ca0-5b26c771008b @ USN 606310 @ Time 2006-06-17
16:09:13
Default-First-Site-Name\RC-SERVER-1 @ USN 1278253 @ Time 2006-10-12
09:36:41
Default-First-Site-Name\RC-SERVER-2 @ USN 1155290 @ Time 2006-10-12
09:51:12

----------------------------------------------------------------------------
------------------

D:\>ntdsutil
ntdsutil: metadata cleanup
metadata cleanup: connections
server connections: connect to server rc-server-1
Binding to rc-server-1 ...
Connected to rc-server-1 using credentials of locally logged on user.
server connections: q
metadata cleanup: select operation target
select operation target: list domains
Found 1 domain(s)
0 - DC=ComputerCreations,DC=local
select operation target: select domain 0
No current site
Domain - DC=ComputerCreations,DC=local
No current server
No current Naming Context
select operation target: list sites
Found 1 site(s)
0 -
CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=ComputerCreations,
DC
=local
select operation target: select site 0
Site -
CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=ComputerCreations
,DC=local
Domain - DC=ComputerCreations,DC=local
No current server
No current Naming Context
select operation target: list servers in site
Found 2 server(s)
0 -
CN=RC-SERVER-1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configura
ti
on,DC=ComputerCreations,DC=local
1 -
CN=RC-SERVER-2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configura
ti
on,DC=ComputerCreations,DC=local
select operation target: q
metadata cleanup: q
ntdsutil: q
Disconnecting from rc-server-1...

--
Bob


.

Relevant Pages

  • Removing orphan DC / Domains
    ... metadata cleanup: connections ... server connections: connect to server \\jupiter ... metadata cleanup: select operation target ...
    (microsoft.public.windows.server.active_directory)
  • Re: Removing a child domain from the parent
    ... I successfully removed the server with the ... I am trying to run the metadata cleanup. ... server connections: connect to server app1 ... metadata cleanup: select operation target ...
    (microsoft.public.windows.server.setup)
  • Re: Removing a child domain from the parent
    ... I successfully removed the server with the ... I am trying to run the metadata cleanup. ... server connections: connect to server app1 ... metadata cleanup: select operation target ...
    (microsoft.public.windows.server.setup)
  • Re: Removing orphan DC / Domains
    ... Wizard to force demotion in Windows Server 2003 and in Windows 2000 Server ... metadata cleanup: connections ... metadata cleanup: select operation target ...
    (microsoft.public.windows.server.active_directory)
  • RE: using ntdsutil to remove a DC from AD
    ... Also, we you remove the server, If you got "Element not found error" this ... metadata cleanup: select target operation ... select operation target: list domains ... Not connected to a server - use "Connections" ...
    (microsoft.public.windows.server.dns)
Loading