OK I have this scenario that I am trying to implement. I have been able to get the Inbound and Outbound and publishing from 2 data sources up and running. my Scenario consists of users being moved from different OU's depending on the department or employee type. In this case for testing purposes i am using the employeeType attribute. I have an employee that gets created through the website or AD then his employee type changes from an Intern to a Full Time Employee.Currently this is my setup: 3 Sync Rules: AD outbound FTE, AD outbound Intern, and AD inboundI have two workflows: AD outbound WF FTE and AD outbound WF Intern both action type with the activity being one of the above sync rules (Add)2 MPRs: AD outbound FTE and AD outbound Intern I just want to be able to have the user moved from the OU to a different OU based on the employeeType what am I missing in order to do this. Is it a workflow issue or an MPR issue.

Apparently youve managed it to get your provisioning problem solved, which is good.After reading your description again, I think, you might actually get by just having one outbound synchronization rule for AD objects.As far as I can tell, the only difference between FTEs and Interns is the location in AD correct?In this case, you would need to add some logic to your current DN flow that would calculate the actual DN based on employee type.Moving objects between OUs is a rename operation. If I remember this correctly, this scenario doesnt work in RC0. To implement a rename, you would need an additional attribute flow for the DN attribute - to be clear, two separate attribute flow rules for the DN attribute.Right now, you already have an initial flow for DN attribute, which is required. To handle your rename, you would also need another flow for the DN attribute that does not have the initial flow flag set. This flow would be triggered for already provisioned objects, which is what you need to move your object. If memory serves me correctly, the RC0 UI doesnt allow you configure this. Just try to configure another regular attribute flow for the DN attribute and see what the system tells you. If the UI barks at, you will have to wait for RC1. Cheers,MarkusMarkus Vilcinskas, Technical Content Developer, Microsoft Corporation