Home

Results 1 to 5 of 5

Thread: AD: Do attributes in the filter HAVE to be in the schema?

Threaded View

  1. #1
    Join Date
    Aug 2013
    Posts
    124

    AD: Do attributes in the filter HAVE to be in the schema?

    My AD driver is set to place users is OUs based on the value of a custom attribute in LDAP. It is not used for anything other than that. Changing that attribute successfully moves users between OUs in AD without an error but when I try to migrate a new user from eDirectory I get a trace message that the attribute "is not in the application schema". It is in the filter though and all I need the attribute for is for driver logic; I don't really need it in AD. Do I really need it in the AD schema or is there a way around it? While extending the schema in AD or mapping it to an unused attribute should work, it is less than ideal. I'm also not sure how manually adding the attribute didn't produce the error but migrating users did.
    Last edited by bobbintb; 01-Jun-2017 at 07:10 PM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •