Re: ADAMsync Object Class Violation
- From: "Aaron.Smith@xxxxxxxx" <Aaron.Smith@xxxxxxxx>
- Date: 17 Jul 2006 08:48:06 -0700
I answered B myself. LDAP queries are fine, but I have to use XML
syntax for things like &....:)
Aaron.Smith@xxxxxxxx wrote:
So I installed ADAM on a test domain controller and am trying to import
user data from AD to ADAM. It imports a few users (guest, krbgt, etc)
and then bombs out with an Object Class Violation error when it tries
to import the Administrator account. I have a couple of questions:
A.) I'm assuming that it's complaining because there is some attribute
on the AD account that doesn't exist in ADAM. I've run
ADSchemaAnalyzer and extended the ADAM schema to include every single
attribute that exists in the AD domain. All items are checked as
present when comparing them and creating the LDIF file yields 0 items.
Is there a way to have ADAMSync report WHICH attribute is producing the
error?
B.) In the ADAMSync config file, I set <object-filter> to
(ObjectClass=user) so that it would only pull over user accounts. Can
this be set to a more specific LDAP query? Something along the lines
of ObjectClass=user, but not cn=Administrator or cn=guest, etc.? I
tried putting in a slightly more complicated LDAP query and it
complained about syntax. Maybe I just misstyped something, but I
thought I'd ask if it's even possible before starting the head beating
on wall process.
.
- References:
- ADAMsync Object Class Violation
- From: Aaron.Smith@xxxxxxxx
- ADAMsync Object Class Violation
- Prev by Date: ADAMsync Object Class Violation
- Next by Date: An error has occurred: 0x800706fc The trust relationship between the primary domain ......
- Previous by thread: ADAMsync Object Class Violation
- Next by thread: An error has occurred: 0x800706fc The trust relationship between the primary domain ......
- Index(es):
Relevant Pages
|
