Duplicate Computer Account Objects CNF???

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I'm not sure if this is the right newsgroup for this but i'm hoping to get an
idea as to a problem i'm seeing in our AD.

I'm beginning to see something like duplicate computer name for example:

seat001
Seat001CNF:0e60630b-2dec-42db-ba54-99f6119a3c06

This has started happening in the last few weeks. i'm not sure whats causing
it or what the CNF is. The computers seem to work properly but I don't know
where to start. Does anyone know what the CNF is?

Any help is greatly appreciated.
 
I'm not sure if this is the right newsgroup for this but i'm hoping to
get an idea as to a problem i'm seeing in our AD.

I'm beginning to see something like duplicate computer name for
example:

seat001
Seat001CNF:0e60630b-2dec-42db-ba54-99f6119a3c06

This has started happening in the last few weeks. i'm not sure whats
causing it or what the CNF is. The computers seem to work properly but
I don't know where to start. Does anyone know what the CNF is?

Any help is greatly appreciated.

This is ADs way of handling duplicate objects via conflict resolution.
Duplicate objects can occur when an object is created on two different
domain controllers in the same replication interval. For example, if a
computer object named COMP1 is created on DC1 and another computer object
named COMP1 is created on DC2 during the same replication interval, there
is a conflict when they try to replicate the objects. To resolve the
conflict, AD adds CNF:[guid] to one of them and writes an error message
to the log on the DC that detected the conflict.

My personal experience is that this usually happens when creating
computer account manually on one DC and then trying to join the domain
using a different DC (which you have no control over). Since the object
doesn't exist on the 2nd DC, it creates a new one, which results in a
conflict when they replicate with each other.

The error message on the DC tells you which one to keep, which is usually
the one with the latest whenChanged attribute for computers (it is
usually the opposite with users, you want to keep the earliest one as
identified by the whenCreated attribute).

HTH,

Wayne Tilton
 
Improper cleaning up after a migration can also be the cause. I don't know
the exact abbreviation but I call it common name flag..

Tn
 
CNF means CoNFlict.

--
Joe Richards Microsoft MVP Windows Server Directory Services
www.joeware.net

Improper cleaning up after a migration can also be the cause. I don't know
the exact abbreviation but I call it common name flag..

Tn
 
Back
Top