Exchange 2010 provision MBXes and link to existing MBXes with FIM
Hello, I have simple ADs deployment in my orgniazation: AD(#1) -> FIM -> AD(#2). Mailbox creation (or rather I should say migration) is triggered by changing a given attribute in AD(#1). As the result FIM kicks in picking up the change and starts the Exchange 2010 mailbox creation process (pretty much standard MS code-less way to provision Exchange 2010 mailboxes) to AD(#2) forest. This works all fine for me! Problem is that within my organization a few users were already created in Exchange 2010 manually (early adopters). Now, from time to time it happens that people trigger mailbox migration in AD(#1) and as the result a new mailbox gets created (existing one is then disconnected). Is there a way to help FIM resolve this issue with the code-less provisioning? Or I should rather go to custom workflows or FIM extension directly to implement mailbox ecistance check? I have a few ideas (if code-less) does not prove helpful, but would greatly appreciate advices for the most effective and common approach. Regards.
April 15th, 2011 10:45am

I think this scenario calls for a custom activity to help you. You will probably be able to integrate this activity into your codeless design via WF parameters.
Free Windows Admin Tool Kit Click here and download it now
April 19th, 2011 9:41am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics