NTDS Replication warnings

I am currently running a Windows 2003 native AD domain with two DCs; DC #1
has Domain Naming and Schema FSMO roles, DC #2 has PDC, Infrastructure and
RID Master FSMO roles. The below event log entry appears on both my DCs
once a day at about the same time each day. The referenced server in the
event log entry (W2K3SERVER) is no longer in my network and is not listed
anywhere in DNS or in FSMO roles. However the error shows it as having the
infrastructure role, which is not the case.

The advice in the event log entry is not helpful because the FSMO roles are
correct and do not list W2K3SERVER anywhere in my AD domain. "netdom query
fsmo" command yields the correct roles for each DC.

Before I go fishing around (and probably break something ), is there a
proper way to rid my Active Directory of this entry?


Thanks in advance!

Edward W. Ray

Event Type: Warning

Event Source: NTDS Replication

Event Category: Replication

Event ID: 2091

Date: 5/30/2004

Time: 10:23:39 AM

User: NT AUTHORITY\ANONYMOUS LOGON

Computer: BLOWJOB

Description:



Ownership of the following FSMO role is set to a server which is deleted or
does not exist.



Operations which require contacting a FSMO operation master will fail until
this condition is corrected.



FSMO Role: CN=Infrastructure,DC=ForestDnsZones,DC=mmicmanhome net,DC=local

FSMO Server DN: CN=NTDS
Settings\0ADEL:71802418-3aa6-41d4-be34-05ae893e06f7,CN=W2K3SERVER\0ADEL:05c61c7f-2820-492c-bd9a-e9af8914fcea,CN=Servers,



User Action:



1. Determine which server should hold the role in question.

2. Configuration view may be out of date. If the server in question has been
promoted recently, verify that the Configuration partition has replicated
from the new server recently. If the server in question has been demoted
recently and the role transferred, verify that this server has replicated
the partition (containing the latest role ownership) lately.

3. Determine whether the role is set properly on the FSMO role holder
server. If the role is not set, utilize NTDSUTIL.EXE to transfer or seize
the role. This may be done using the steps provided in KB articles 255504
and 324801 on http://support.microsoft.com.

4. Verify that replication of the FSMO partition between the FSMO role
holder server and this server is occurring successfully.



The following operations may be impacted:

Schema: You will no longer be able to modify the schema for this forest.

Domain Naming: You will no longer be able to add or remove domains from this
forest.

PDC: You will no longer be able to perform primary domain controller
operations, such as Group Policy updates and password resets for non-Active
Directory accounts.

RID: You will not be able to allocation new security identifiers for new
user accounts, computer accounts or security groups.

Infrastructure: Cross-domain name references, such as universal group
memberships, will not be updated properly if their target object is moved or
renamed.



For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.