OU value not populated on AD to FIM sync
-
Friday, January 25, 2013 1:35 PM
When synchronizing from AD to FIM, it seems as if the 'ou' attribute is not populated - at least it is not populated when looking at the at the user's metaverse object after an import and sync on AD. The flow status states 'NOT APPLIED' and while the ou is listed as a Data Source Attribute the Initial and Final values are null. Why wouldn't the OU value be populated with the user's OU?
All Replies
-
Sunday, January 27, 2013 8:43 AM
Hi Osho
As it may seem the OU attribute should be auto populated in AD, depending on the user's immidiate OU, However, that is not the case.
the OU attribute is just another string attribute with no connection to the user's OU in the AD. This attribute just happens to have the name 'ou'.
Most probably it is empty in the Active Directory itself. You can check that in the 'attribute editor' in the Users properties from 'AD Users and Computers Console'
If you want to get the OU for the user you will have to parse the "dn".
- Marked As Answer by Osho27 Wednesday, February 13, 2013 5:00 PM
.png)
