Re: Replacing old DC

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hello RemyMaza,

If you are only concerned about the "DELETED SERVER" entry in replmon console, you can ignore it.

See this excellent article about:
http://blogs.dirteam.com/blogs/jorge/archive/2006/12/09/DSA_2D00_GUIDs-and-Invocation-IDs.aspx

If you have a removed domain displayed check with this article:
http://support.microsoft.com/kb/230306

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


I'd like an expert opinion on these logs. I'm probably overthinking
it, but I'd rather be safe. I ran replmon and saved a status report:

Active Directory Replication Monitor
Printed on 2/18/2009 8:22:46 PM
This report was generated on data from the server: SERVER
**********************************************************************
*****
SERVER Data
**********************************************************************
*****
This server currently has writable copies of the following directory
partitions:
----------------------------------------------------------------------
-----
DC=domain,DC=internal
CN=Configuration,DC=domain,DC=internal
CN=Schema,CN=Configuration,DC=domain,DC=internal
DC=DomainDnsZones,DC=domain,DC=internal
DC=ForestDnsZones,DC=domain,DC=internal
Because this server is a Global Catalog (GC) server, it also has
copies
of the following directory partitions:
----------------------------------------------------------------------
-----
Current NTDS Connection Objects
-------------------------------
city2\SERVER00
Connection Name : 5b645f9d-3bc0-49aa-83c0-f1516341e012
Administrator Generated?: AUTO
Reasons for this connection:
Directory Partition
(CN=Configuration,DC=domain,DC=internal)
Directory Partition
(DC=ForestDnsZones,DC=domain,DC=internal)
Directory Partition
(DC=DomainDnsZones,DC=domain,DC=internal)
Directory Partition (DC=domain,DC=internal)

Current Direct Replication Partner Status
-----------------------------------------
Directory Partition: DC=domain,DC=internal

Partner Name: city2\SERVER00
Partner GUID: E9C471CD-5369-4DF5-8EAB-7966B47DADE8
Last Attempted Replication: 2/18/2009 7:53:29 PM
(local)
Last Successful Replication: 2/18/2009 7:53:29 PM
(local)
Number of Failures: 0
Failure Reason Error Code: 0
Failure Description: The operation completed
successfully.
Synchronization Flags:
DRS_WRIT_REP,DRS_INIT_SYNC,DRS_PER_SYNC,DRS_USE_COMPRESSION,DRS_NEVER_
NOTIFY
USN of Last Property Updated: 8619560
USN of Last Object Updated: 8619560
Transport: Inter-domain RPC
Directory Partition: CN=Configuration,DC=domain,DC=internal

Partner Name: city2\SERVER00
Partner GUID: E9C471CD-5369-4DF5-8EAB-7966B47DADE8
Last Attempted Replication: 2/18/2009 7:53:29 PM
(local)
Last Successful Replication: 2/18/2009 7:53:29 PM
(local)
Number of Failures: 0
Failure Reason Error Code: 0
Failure Description: The operation completed
successfully.
Synchronization Flags:
DRS_WRIT_REP,DRS_INIT_SYNC,DRS_PER_SYNC,DRS_USE_COMPRESSION,DRS_NEVER_
NOTIFY
USN of Last Property Updated: 8619595
USN of Last Object Updated: 8619595
Transport: Inter-domain RPC
Directory Partition:
CN=Schema,CN=Configuration,DC=domain,DC=internal
Partner Name: city2\SERVER00
Partner GUID: E9C471CD-5369-4DF5-8EAB-7966B47DADE8
Last Attempted Replication: 2/18/2009 7:53:29 PM
(local)
Last Successful Replication: 2/18/2009 7:53:29 PM
(local)
Number of Failures: 0
Failure Reason Error Code: 0
Failure Description: The operation completed
successfully.
Synchronization Flags:
DRS_WRIT_REP,DRS_INIT_SYNC,DRS_PER_SYNC,DRS_USE_COMPRESSION,DRS_NEVER_
NOTIFY
USN of Last Property Updated: 8619494
USN of Last Object Updated: 8619494
Transport: Inter-domain RPC
Change Notifications for this Directory Partition
-------------------------------------------------
Server Name: city2\SERVER00
Object GUID: 9624AEAB-CEAB-410D-9E17-D49460C34443
Time Added: 10/26/2006 6:33:28 AM
Flags: DRS_WRIT_REP
Transport: RPC
Directory Partition: DC=DomainDnsZones,DC=domain,DC=internal

Partner Name: city2\SERVER00
Partner GUID: E9C471CD-5369-4DF5-8EAB-7966B47DADE8
Last Attempted Replication: 2/18/2009 7:53:29 PM
(local)
Last Successful Replication: 2/18/2009 7:53:29 PM
(local)
Number of Failures: 0
Failure Reason Error Code: 0
Failure Description: The operation completed
successfully.
Synchronization Flags:
DRS_WRIT_REP,DRS_PER_SYNC,DRS_USE_COMPRESSION,DRS_NEVER_NOTIFY
USN of Last Property Updated: 8619494
USN of Last Object Updated: 8619494
Transport: Inter-domain RPC
Change Notifications for this Directory Partition
-------------------------------------------------
Server Name: city2\SERVER00
Object GUID: 9624AEAB-CEAB-410D-9E17-D49460C34443
Time Added: 11/29/2005 7:52:40 AM
Flags: DRS_WRIT_REP
Transport: RPC
Directory Partition: DC=ForestDnsZones,DC=domain,DC=internal

Partner Name: city2\SERVER00
Partner GUID: E9C471CD-5369-4DF5-8EAB-7966B47DADE8
Last Attempted Replication: 2/18/2009 7:53:29 PM
(local)
Last Successful Replication: 2/18/2009 7:53:29 PM
(local)
Number of Failures: 0
Failure Reason Error Code: 0
Failure Description: The operation completed
successfully.
Synchronization Flags:
DRS_WRIT_REP,DRS_PER_SYNC,DRS_USE_COMPRESSION,DRS_NEVER_NOTIFY
USN of Last Property Updated: 8619567
USN of Last Object Updated: 8619567
Transport: Inter-domain RPC
Current Transitive Replication Partner Status
---------------------------------------------
Directory Partition: DC=domain,DC=internal

Partner Name: city1\SERVER
Partner GUID: A80727DB-F969-4521-8F97-EE35D9D5AC35
USN: 10289434
Partner Name: **DELETED SERVER #2
Partner GUID: E3170870-BFFC-4E42-A453-C7F0613F4BCB
USN: 18951
Partner Name: city2\SERVER00
Partner GUID: E9C471CD-5369-4DF5-8EAB-7966B47DADE8
USN: 8619597
Directory Partition: CN=Configuration,DC=domain,DC=internal

Partner Name: city1\SERVER
Partner GUID: A80727DB-F969-4521-8F97-EE35D9D5AC35
USN: 10289434
Partner Name: **DELETED SERVER #2
Partner GUID: E3170870-BFFC-4E42-A453-C7F0613F4BCB
USN: 18913
Partner Name: city2\SERVER00
Partner GUID: E9C471CD-5369-4DF5-8EAB-7966B47DADE8
USN: 8619597
Directory Partition:
CN=Schema,CN=Configuration,DC=domain,DC=internal
Partner Name: city1\SERVER
Partner GUID: A80727DB-F969-4521-8F97-EE35D9D5AC35
USN: 10289434
Partner Name: **DELETED SERVER #2
Partner GUID: E3170870-BFFC-4E42-A453-C7F0613F4BCB
USN: 18882
Partner Name: city2\SERVER00
Partner GUID: E9C471CD-5369-4DF5-8EAB-7966B47DADE8
USN: 8619597
Directory Partition: DC=DomainDnsZones,DC=domain,DC=internal

Partner Name: city1\SERVER
Partner GUID: A80727DB-F969-4521-8F97-EE35D9D5AC35
USN: 10289434
Partner Name: **DELETED SERVER #2
Partner GUID: E3170870-BFFC-4E42-A453-C7F0613F4BCB
USN: 18882
Partner Name: city2\SERVER00
Partner GUID: E9C471CD-5369-4DF5-8EAB-7966B47DADE8
USN: 8619597
Directory Partition: DC=ForestDnsZones,DC=domain,DC=internal

Partner Name: city1\SERVER
Partner GUID: A80727DB-F969-4521-8F97-EE35D9D5AC35
USN: 10289434
Partner Name: **DELETED SERVER #2
Partner GUID: E3170870-BFFC-4E42-A453-C7F0613F4BCB
USN: 18882
Partner Name: city2\SERVER00
Partner GUID: E9C471CD-5369-4DF5-8EAB-7966B47DADE8
USN: 8619597
The server SERVER knows about the following FSMO roles:
----------------------------------------------------------------------
----
Schema FSMO: city1\SERVER
Domain Naming FSMO: city1\SERVER
Infrastructure FSMO: city1\SERVER
Primary Domain Controller FSMO: city1\SERVER
RID Pool FSMO: city1\SERVER
Performance Statistics at Time of Report
----------------------------------------
Configuration (Registry)
NOTE: an empty value indicates that Windows 2000 will use the internal
default
NOTE: all empty values may indicate insufficient permission to
retrieve this information from the domain controller
------------------------
DSA
---
Days per Database Phantom Scan:
Initialize MAPI interface:
Enforce LIST_OBJECTS rights:
DSA Heuristics:
Max Threads (ExDS+NSP+DRA):
DSA Database file: C:\WINDOWS\NTDS\ntds.dit
DSA Working Directory: C:\WINDOWS\NTDS
Critical Object Installation:
DS Drive Mappings:
DSA Previous Restore Count:
REPLICATION
-----------
Replicator notify pause after modify (secs):
Replicator notify pause between DSAs (secs):
Replicator intra domain packet size (objects):
Replicator intra domain packet size (bytes):
Replicator inter domain packet size (objects):
Replicator inter domain packet size (bytes):
Replicator maximum concurrent read threads:
Replicator operation backlog limit:
Replicator thread op priority threshold:
Replicator intra domain RPC handle lifetime (secs):
Replicator inter domain RPC handle lifetime (secs):
Replicator RPC handle expiry check interval (secs):
LDAP
----
Max objects in LDAP Search (Admin Limit):
Max concurrent LDAP connections allowed:
Max time allowed for an LDAP Search:
Max concurrent LDAP searches allowed:
Max concurrent threads per LDAP connection allowed:
Minimum idle seconds before potential \ timeout of LDAP
connection (non-authenticated client):
Minimum idle seconds before potential \ timeout of LDAP
connection (authenticated client):
Database
--------
Database backup path: C:\WINDOWS\NTDS\dsadata.bak
Database backup interval (hours):
Database log files path: D:\WINDOWS\NTDS
Database logging/recovery: ON
Hierarchy Table Recalculation interval (minutes): 720
Database restored from backup:
Pending object ownership conversions:
EDB max buffers:
EDB max log buffers:
EDB log buffer flush threshold:
EDB buffer flush start:
EDB buffer flush stop:
EDB max ver pages (increment over the minimum:
Circular Logging:
Server Functionality:
TCP/IP Port:
Restore from disk backup:
Performance Counter Version: 17
KCC
---
Repl topology update delay (secs):
Repl topology update period (secs):
KCC domain generator fail-over (minutes):
KCC domain generator renewal interval (minutes):
KCC domain generator renewal interval (minutes):
CriticalLinkFailuresAllowed:
MaxFailureTimeForCriticalLink (sec):
NonCriticalLinkFailuresAllowed:
MaxFailureTimeForNonCriticalLink (sec):
InterdomainFailuresAllowed:
MaxFailureTimeForInterdomainLink (sec):
KCC connection failures:
InterdomainFailuresAllowed:
InterdomainFailuresAllowed:
**********************************************************************
*****
Enterprise Data
**********************************************************************
*****
Globally Unique Identifiers (GUIDs) for each domain controller in the
enterprise
NOTE: the absence of a GUID means that the server has been demoted.
----------------------------------------------------------------------
----------
domain Name: city1
---------------------------------------
domain Options :
domain Topology Generator: CN=NTDS
Settings,CN=SERVER,CN=Servers,CN=city1,CN=domains,CN=Configuration,DC=
domain,DC=internal
domain Topology Renewal :
domain Topology Failover :
SERVER
Server GUID (used for
DNS) :
545D5B9E-C9B5-4416-927F-
EBFE875BD262
Replication Database GUID (used to identify partner in
replication): A80727DB-F969-4521-8F97-EE35D9D5AC35
DSA Options : NTDSDSA_OPT_IS_GC
DSA Computer Path : CN=SERVER,OU=Domain
Controllers,DC=domain,DC=internal
DSA Schema Location :
CN=Schema,CN=Configuration,DC=domain,DC=internal
DSA Mail Address :
DSA DNS Host Name : SERVER.domain.internal
DSA BridgeHead Transports :
domain Name: city2
---------------------------------------
domain Options :
domain Topology Generator: CN=NTDS
Settings,CN=SERVER00,CN=Servers,CN=city2,CN=domains,CN=Configuration,D
C=domain,DC=internal
domain Topology Renewal :
domain Topology Failover :
SERVER00
Server GUID (used for
DNS) :
9624AEAB-CEAB-410D-9E17-
D49460C34443
Replication Database GUID (used to identify partner in
replication): E9C471CD-5369-4DF5-8EAB-7966B47DADE8
DSA Options : NTDSDSA_OPT_IS_GC
DSA Computer Path : CN=SERVER00,OU=Domain
Controllers,DC=domain,DC=internal
DSA Schema Location :
CN=Schema,CN=Configuration,DC=domain,DC=internal
DSA Mail Address :
DSA DNS Host Name : SERVER00.domain.internal
DSA BridgeHead Transports :
domain Name: city3
---------------------------------------
domain Options :
domain Topology Generator: CN=NTDS
Settings,CN=SERVER00,CN=Servers,CN=city2,CN=domains,CN=Configuration,D
C=domain,DC=internal
domain Topology Renewal :
domain Topology Failover :
Active Directory Replication Monitor determined that there
are no servers in this domain.

domain Links and domain Link Bridges
-----------------------------------------------------
domain Links
----------
DEFAULTIPdomainLINK
Link Type: : IP
Distinguished Name :
CN=DEFAULTIPdomainLINK,CN=IP,CN=Inter-domain
Transports,CN=domains,CN=Configuration,DC=domain,DC=internal
Replication Interval : 180
Cost : 100
Options :
domain List :
city3
city2
city1
domain Link Bridges
------------------
Active Directory Replication Monitor determined that no
domain Link Bridges are present in the Directory.
Inter-domain Transports
---------------------
IP
Options :
DLL Name : ismip.dll
Address Type: dNSHostName
SMTP
Options : NTDSTRANSPORT_OPT_IGNORE_SCHEDULES
DLL Name : ismsmtp.dll
Address Type: mailAddress
Subnets
-------
192.168.1.0/24
Associated domain :
CN=city1,CN=domains,CN=Configuration,DC=domain,DC=internal
192.168.110.0/24
Associated domain :
CN=city2,CN=domains,CN=Configuration,DC=domain,DC=internal
192.168.120.0/24
Associated domain :
CN=city3,CN=domains,CN=Configuration,DC=domain,DC=internal
Active Directory Configuration Data
-----------------------------------
Stay of Execution for Servers: 0
SPN Mappings :
host=alerter,appmgmt,cisvc,clipsrv,browser,dhcp,dnscache,replicator,ev
entlog,eventsystem,policyagent,oakley,dmserver,dns,mcsvc,fax,msiserver
,ias,messenger,netlogon,netman,netdde,netddedsm,nmagent,plugplay,prote
ctedstorage,rasman,rpclocator,rpc,rpcss,remoteaccess,rsvp,samss,scards
vr,scesrv,seclogon,scm,dcom,cifs,spooler,snmp,schedule,tapisrv,trksvr,
trkwks,ups,time,wins,www,http,w3svc,iisadmin,msdtc
Partner Name: **DELETED SERVER #2
Partner GUID: E3170870-BFFC-4E42-A453-C7F0613F4BCB
USN: 18951
This line is what raises my curiosity. I'm not having replication
issues but I'd like to clear this up before I bring in a new dc. Is
this really a problem? DCDiag doesn't have any errors either. Should
I run a different test?

Thanks in advance,
Matt


.

Relevant Pages

  • Re: Replacing old DC
    ... It still has info from this now removed server. ... Current Direct Replication Partner Status ... USN of Last Property Updated: ... Replicator notify pause after modify: ...
    (microsoft.public.windows.server.active_directory)
  • Replacing old DC
    ... This report was generated on data from the server: ... Current Direct Replication Partner Status ... USN of Last Property Updated: ... Replicator notify pause after modify: ...
    (microsoft.public.windows.server.active_directory)
  • Replacing old DC
    ... This report was generated on data from the server: ... Current Direct Replication Partner Status ... USN of Last Property Updated: ... Replicator notify pause after modify: ...
    (microsoft.public.windows.server.active_directory)
  • Re: Replacing old DC
    ... This report was generated on data from the server: ... Current Direct Replication Partner Status ... USN of Last Property Updated: ... Replicator notify pause after modify: ...
    (microsoft.public.windows.server.active_directory)
  • AD Replication Monitor Status Report
    ... Section & 'The server HUNAIN knows about the following FSMO roles:' Section ... Current Direct Replication Partner Status ... USN: 909870 ... Replicator notify pause after modify: ...
    (microsoft.public.win2000.active_directory)