Hi All 1. Created three new users (contractors) 2. Created Outbound Sync rule 3. Created WF 4. Created MPR When I look at the users properties created in step 1, none of them are part of the ERL. 5. I then created another user (contractor) When I look at this users properties, I can see that user is part of the ERL. My question is, why MPR is not applied on the users created in step 1 and but only on users created in step 5. I have verified that all the users (step 1 & 5) are part of the All Contractors set. TIA Sachin

A MPR fires on a condition - for example a change on the Set membership.I can only make assumptions about your scenario, however, when you've created the last contractor, you have a trigger to fire the MPR by adding the user to All Contractors.This trigger is lost when you've created the other users since the object that fires on the set membership change - your MPR - didn't exist.Does this make sense?In a nutshell, a MPR fires based on a triggering event.Cheers,MarkusMarkus Vilcinskas, Knowledge Engineer, Microsoft Corporation

Thanks Markus. How can this be solved as it could happen in real life scenario also. I deleted the Set Membership condition and recreated it. But still MPR is not fired for the users created in step 1. TIA Sachin

I deleted the Set Membership condition and recreated it. Does this mean, you have deleted the condition on the MPR and re-created it?Cheers,MarkusMarkus Vilcinskas, Knowledge Engineer, Microsoft Corporation

Yes, under Set. Set -> All Contractors -> Criteria-based Members -> 'Employe Type' is 'Contractor' - I deleted this condition and recreated it. Also, trying the 'User and Group Management' walkthrough. Again, MPR is not triggered for the existing users. Is there no way where we can trigger the MPR on existing Set members? Cheers, Sachin

Just make your user a FTE and change it back to contractor.Cheers,MarkusMarkus Vilcinskas, Knowledge Engineer, Microsoft Corporation

That will work only if we have few users...but what if we have thousands of users already in FIM Portal and then later we want to introduce a MPR? Does this limitation mean that we should ALWAYS have MPR defined first before populating any objects into FIM Portal? Cheeers, Sachin

I changed the Employee Type of one user from 'Contractor' to 'Full Time Employee'. Closed the dialog. Again edited the user properties and changed the Employee Type from 'Full Time Employee' to 'Contractor' still MPR is not triggerd. Cheers Sachin

You should post your MPR configuration.Is it possible that your MPR is configured to only fire on adds?Cheers,MarkusMarkus Vilcinskas, Knowledge Engineer, Microsoft Corporation

For MPR, under 'Requestors and Operation' Tab, I selected all the Operations. Create resoure, Delete resource, Read resource, Add a value to multivalued attirbute, Remove a value from a multivalued attribute and Modify a single-valued attribute. Cheers Sachin

You should really post your complete MPR configuration.Cheers,MarkusMarkus Vilcinskas, Knowledge Engineer, Microsoft Corporation

I did something similar (I think) and what I ended up doing was setting the Run on Policy Update flag on the workflow, disabling the MPR, IISRESET, enabling the MPR, IISRESET and then the remaining set members ERL was updated with the synch rule in pending status.