Scenario:
Users in Set 123 need AD accounts only
Users in Set B need Ex mbxs (& AD accounts obviously)
Users can move from Set 123 to Set B, or go directly into Set B
We cannot simply create a 'base' AD sync rule, and then a dependent Ex sync rule with homemdb,mail,msexchhomeserver &mailnickname - we cannot use 'initial flow only' in a dependent sync rule. We don't want FIM to continue to set the msexchhomeserver and other attributes - we want to transfer authority to Exchange to manage those attributes.
If we create two separate sync rules, not dependent, we can't control which tries to execute first. If we have the ex sync rule withjust homemdb,mail,msexchhomeserver &mailnickname attributes set for initialflowonly, it will fail if it tries to run before the sync rule that creates the AD account.
Separately, does initial flow only run when the user is added to the scope of the sync rule for the first time, or when the object is actually provisioned in AD? In other words, if a user object exists in AD and FIM is aware of this, will FIM flow out attributes in a sync rule set for initial flow only?
Ben Pahl