So in support a very common discussion is "How do I automate my run profiles? and How often should I run the run profiles?" In light of this conversation topic, I decided to write a wiki covering these two questions. My goal is to provide centralized information and additional information on automating the run profiles as well as answering the question of how often.
It is important to understand the different run profiles, and what they do. Here are resources that discuss the run profiles. The run profile definitions have not changed from MIIS 2003 to FIM 2010 and/or FIM 2010 R2. ILM Run Profile Definitions Run profiles in MIIS 2003 Understanding Run Profiles in MIIS 2003 How to work with more than one partition in a management agent
It is important to understand the different run profiles, and what they do. Here are resources that discuss the run profiles. The run profile definitions have not changed from MIIS 2003 to FIM 2010 and/or FIM 2010 R2.
The Synchronization Engine itself does not provide a means of automating or scheduling your runs. The reason for this is that each business or organization that uses the Synchronization Service Engine has it's own business rules as to when to schedule the runs, and which runs to execute. The Synchronization Service Engine does provide a means of creating a script file that you can utilize with Task Scheduler. This topic is very broad across the internet, but I have brought some of it together for us. REFERENCE: How to automate run profiles via script button How to schedule agents via a batch file How to automate and schedule Run Profiles for IIFP/MIIS/ILM
The Synchronization Engine itself does not provide a means of automating or scheduling your runs. The reason for this is that each business or organization that uses the Synchronization Service Engine has it's own business rules as to when to schedule the runs, and which runs to execute. The Synchronization Service Engine does provide a means of creating a script file that you can utilize with Task Scheduler. This topic is very broad across the internet, but I have brought some of it together for us.
This is a very tough question for a person in support to answer, as each business has different solutions, different needs, and different business rules. As a recommendation, it would be good to sit down with your team and discuss what your business needs are as far as updating the information. We in support have seen people run it as quick as every 10 minutes, and as much as once a day or once a week. It really depends on your business needs. If you choose to run around the neighborhood of every 10 minutes, the recommendation would be to keep an eye on it, and ensure that you do not have runs overlapping one another. If you do have runs, especially synchronizations, then it would be recommended that you lengthen the time between runs to ensure that you give your runs adequate time to complete successfully. Here is a good resource that goes into a deeper explanation of when to run the run profile. FIM-REFERENCE: Which Run Profile Do I run first?
This could be broken down into several areas. For now, we will break it down at a high level. IMPORT: Network Monitoring Tool, SQL Server Profiler Testing with a drop file SYNCHRONIZATION: SQL Server Profiler EXPORT: Network Monitoring Tool, SQL Server Profiler TROUBLESHOOTING: Troubleshooting Export Issues REFERENCE: How to export to a drop file REFERENCE: How to export using a threshold WMI TROUBLESHOOTING: 0x8004100E - Invalid Namespace
This could be broken down into several areas. For now, we will break it down at a high level.
FIM LANDING PAGE: Resource Wiki Page Index
Tim Macaulay edited Revision 5. Comment: added new link for working with more than one partition
Tim Macaulay edited Revision 4. Comment: added a link for troubleshooting a WMI issue in case the run profile fails when calling from wmi
Tim Macaulay edited Revision 1. Comment: added a new link for which run profile do I run first