Options? Most people use Windows Task Scheduler with a PowerShell script or VBScript -- which works but can get cumbersome to maintain. With my SQL Server background, I often use SQL Server Agent Jobs because it has much better follow up and executing database commands.
- Task Scheduler -- runs as a windows service
- Can launch a job based on multiple triggers:
- CPU idle
- an event in the event log
- user logon
- Step Types
- Command line
- What it lacks is follow up -- it doesn't write to the event log, it doesn't have email capability, it doesn't do a good job of storing the results.
- SQL Agent -- also runs as a windows service
- Schedule types:
- Recurring -- recur every x hours, x min or x seconds
- One time
- SQL Agent Starts
- CPU idle
- Step Types
- Command Line
- Follow up is pretty good --
- Write to the event log
- It automatically records the results of each step -- I find it much easier to troubleshoot a SQL Agent job as opposed to a Task Scheduler job.
- You can control the level of detail recorded
- Send an email on failure or success
- Can even have a pager schedule
- You can jump from one step to another on success or failure
A search of GitHub reveals a few Open Source options that provide features more specific to MIM.
Open Source options:
- Aseand's RunScript is a PowerShell script. How does that help? It has all kinds of pre-built functions that are commonly needed in your own PowerShell script -- so this isn't really a scheduler as you still need to use Task Scheduler, but not a bad place to start your own PowerShell script.
- AnyInProgress Ma's
- start-agent -- runs an Agent asynchronously
- Runagent -- runs an Agent and waits -- looks to have some great error handling
- WriteXmlToScreen -- for printing out the CSEntry data
- SaveChangeCS -- get the pending CS changes
- Aseand also created a PowerShell script that does some pretty nice Sync engine documentation by querying the Sync engine database
- Fellow MVP Ryan Newington (lithnet)'s miis-autosync -- runs as a windows service
- Recurring schedules
- events such as changes to AD, HR etc
- The other key feature is it can be set up to only run if there is work to be done. It can also run as many profiles in parallel as possible. This is one of the best ways to cut a sync cycle as short as possible.
- Send emails when job fails
- Clear Run History
- Wim Beck's FIM Scheduler -- uses XML config files, can run linear sequences and parallel sequences. It also runs as a Windows Service
- Former MVP Soren Granfeldt's MA Run Scheduler -- was built as a replacement for the MASequencer from the MIIS Toolkit.
- Traxion Solutions also has an MIIS Sequencer to replace the MA Sequencer
A friend have point out that my run script was mentioned in you blog.
Have new version that I have used some time but not update on Github, have done so now.
The new version have some nice more functions, so you may script disconnects and previews.
I also recommend take look on MIM-Powershell-Agent, that is powershell agent and is passible run rules extensions as powershell script in MIM for any other.
Post a Comment