Comment Added by : Rob Ingenthron

Comment Added at : 2012-07-18 23:06:18

Comment on Tutorial : Change Dirsync synchronization frequency By Emiley J
This is the solution that I also used, however, there may be a problem with this method: the default "every three hour" schedule appears to continue, regardless of the time of the last manual run. In other words, there could be a potential conflict when your manually triggered job is in the middle of running one of the four tasks, and then the scheduled process kicks in.

I am still testing this, and trying to ascertain whether or not there really is an issue. I am trusting that Microsoft programmers were smart enough to check for the status of the process when the Powershell is started.

I am triggering my scheduled process (an event log triggered scheduled task) to run after an Application Event ID 4 (dirsync process completed), waiting for 30 minutes before starting the Powershell.

So far, on my system, I am not seeing a problem with doing this.

View Tutorial