Hi, May i start off by saying thank you to the people that have helped me so far - but I still have an issue understanding FIM basics. Run Profiles is one such area, and please do not post links to white papers or technet articles or blogs...please could someone explain the run profiles to me. I am working thru the following lab: "How do I provision users to AD DS" http://technet.microsoft.com/en-us/library/ff686263(WS.10).aspx and I would like to ask a question about Step 9 Run the run profiles: Fabrikam FIMMA - Full Import (in my limited knowledge, an "Import" moves data from external system (FIM Portal) into the Connector Space, correct?) Fabrikam FIMMA - Full Sync (a Sync moves data from the Connector Space to the Metaverse, correct?) Fabrikam FIMMA - Export (why is the 3rd step Export if the data is already in the MV (step 2)?) Fabrikam FIMMA - Delta Import (why is there a Delta Import step, when all data was already imported in Step 1 Full Import?) Fabrikam ADMA - Full Import (moves data from AD to the Connector Space, correct?) Fabrikam ADMA - Full Sync (moves data from Connector Space to Metaverse, correct?) Why is there no Export run profile on the ADMA...should there be one if we want to move data into AD? Thank you

1. Correct, import moves data from external data source to its connector space. 2. Partially correct, a sync applies the flow rules in both directions, not only import, export too. This depends on your configuration in the FIM sync engine and/or FIM portal with it's the sync rules configuration. But in the scenario there is an outbound flow (to the FIM portal), that needs an export run profile to the FIM portal. (Ref next point.) 3. Export to FIM MA is needed to move data from MV to FIM Portal 4. If you run an export, you need an import to confirm that the exported data has been accepted by/save to the target data source. This can be a full import or delta import. By preference delta, in normal operation. 5. Correct. Full Import requests ALL data available (while delta imports only move changed data, since previous import) 6. Partially correct, as explained, sync moves data between connector space and metaverse in both directions depending configuration. 7. If you did not define an export flow (or outbound sync rule to AD in the FIM portal), you don't need an export run profile. If you have an export flow defined, then you should run an export run profile. At least, if one of the synchronisation runs has resulted in outbound synchronization data for the ADMA, you need to run the export. (Check the sync run profile statistics.) HTH, Peter Peter Geelen (Traxion) - Sr. Consultant IDA (http://www.fim2010.be) [If a post helps to resolve your issue, please click the "Mark as Answer" of that post or "Helpful" button of that post. By marking a post as Answered or Helpful, you help others find the answer faster.]

Peter, Thank you SO much, finally a clear cut explanation of the profiles !!! Just have a small issue with point. 4 4. If you run an export, you need an import to confirm that the exported data has been accepted by/save to the target data source. So is that the essence of that final 'Import' operation....confirm that the exported data has been accepted The logic just does not stick...Import is 'from external data source to CS' ....maybe I need to sleep on it....

"... logic just does not stick...Import is 'from external data source to CS' ....maybe I need to sleep on it......." If you remember that the view is always from FIM it will make more sense. FIM will get info FROM the external datasource, so for FIM it's a Import. Does that make more sense? Kind regards, Freek Berson

so essentially this last "import" is a way for FIM to verify that everything that needed to be processed was indeed processed? Could more objects suddenly appear on this final "import"....then what? will that be scheduled for the next profile run?

Right, the sync engine needs to confirm what it exported. It is more granular than the run profile - it actually goes right down to the attribute, as described in the State-Based Processing in MIIS 2003 guide. If you get more changes on your final import, then they will just get processed the next time your agent runs (assuming the management agents are scheduled). CraigMartin Edgile, Inc. http://identitytrench.com

awesome, thanks !