Provisioning hierarchy errors following update 2
Hi All,
Updated my FIM 2010 from update 1 to update 2 and now when I go to edit the properties of my management agents that had provisioning hierarchy configured I get the following error:
"The mapping for dn component of 'xx' to object type 'xx' is not in the list of allowed component mappings"
If I try and enable provisioning hierarchy in a management agent that did not already have it enabled I get the same error.
Deleting the configured rules and trying to re-create them results in the same error.
Does anyone else get this error? or is it just me?
Thanks in advance
Heath
March 7th, 2012 8:38pm
I have exactly the same error. Looks likes update 2 broke it :-(
Free Windows Admin Tool Kit Click here and download it now
March 8th, 2012 3:46am
I will not have this problem as the picture below shows I don't have o mapped to organization. Why do you?
March 8th, 2012 9:47am
Update 2 applied and you have saved that change?
Free Windows Admin Tool Kit Click here and download it now
March 8th, 2012 10:22am
The same error is displayed whether it is 'o' or 'ou' mapped, as Mark says, it looks like it is an issue introduced with update 2
March 8th, 2012 5:41pm
Ok, so there is a nasty workaround. As a test I manually modified the mms_management_agent table in SQL to add the component mapping. The UI complained and won't let you make any changes until you fix the 'error', but the MA worked as it should creating
the OU as expected.
Free Windows Admin Tool Kit Click here and download it now
March 13th, 2012 4:55am
Better than nothing :) I can just remove the mapping, modify MA, modify db..if I need to make any changes :)
March 15th, 2012 10:43pm
I'd just like to re-raise this thread - Rollup 2 has, in my experience, definitely broken the "Provisioning Hierarchy" UI. It's impossible to modify any properties of the MA as long as there are any provisioning hierarchy rules in effect.
As you note, re-adding the rules via mms_management_agent does the trick, but Microsoft has always been clear that the SQL database is not user-serviceable. ;)
I was hoping this rollup would cure hard crashes of the Sync Service during export when trying to provision more than one level of new OU hierarchy.
Free Windows Admin Tool Kit Click here and download it now
April 5th, 2012 6:38pm
Hello,
Same thing, after Update 2 Rollup.
Removed hierarchy provisioning, modified MA, and updated DB. But in UI of MA no mapping are showed...
BR
April 16th, 2012 1:00am
This problem will be fixed in an upcoming hotfix:
https://connect.microsoft.com/site433/feedback/details/735234/update2-provisioning-hierarchy-error
//HenrikHenrik Nilsson, Forefront Identity Manager MVP
Blog Twitter
My employer - Cortego
Free Windows Admin Tool Kit Click here and download it now
April 16th, 2012 2:04am
Hi Mark,
I am getting the same error. what is the xml supposed to look like? can you provide an example?
April 21st, 2012 3:09am
This is the SQL statement I used to add OU mapping. You'll have to change the MA GUID.
use [FIMSynchronizationService]
update mms_management_agent
set [component_mappings_xml]
= '<component_mappings><mapping><dn_component>ou</dn_component><object_class>organizationalUnit</object_class></mapping></component_mappings>'
where [ma_id] =
'4EFBC8E7-D751-40E2-8349-7F356BC23ED1'
Free Windows Admin Tool Kit Click here and download it now
April 23rd, 2012 3:56am