Preventing Duplicate Alerts onPostModify and I guess duplicate processing.
I have some ARS script policies which have to use DirSync to capture the change. The script works fine BUT it runs on every ARS administration service in our environment. This is not normally a problem, although I have tried suppressing the duplicate processing by setting virtual attributes in the $request object and this has had limited success.
In this instance I get ARS to email an alert out. All of the ARS servers, and sometimes one will send out two emails, presumably the change replicating in from two DCs.
I could in theory force all ARS services to use the same DirSync server but I doubt that's good practice and probably would not stop the email alerts being generated.
One option I have used before was to suppress multiple updates based on changes happening in a short space of time but looking at log files generated I have a 10 second window before the change replicates into anther DC so that would be a very small time window.
I looked at using the OperationID as I figured this would be unique to the change but this is only on the Request object if the change is made using ARS and I'm using DirSync to capture the change so that's a dead end.
Has anyone come up with a successful strategy to do this. A drop file seems best but there is a small chance that a email won't be generated if two changes were made at the same time, although thinking about this as I write I guess I could reduce / eliminate that if the file has a relationship to the object so the chance of two changes being made to the same object are small. How successful this might be is debatable too as the file will take longer that 10 seconds to produce and all of the ARS server will have seen the change by then :-(.