Ah I see. In that case, you should be able to continue deleting the value for ADGSLastPollTime (that number is the last time the sync ran in UTC Windows File Time) and just forgo the service restart. LFDS polls this hourly so a sync should be initiated within one hour of deleting the value from the table.

Interesting ok. Yeah I am aware we can just keep deleting the record. I was really hoping someone could shed light on how I could force a specific time as the value in that db_setting record.

Thanks,

Julie

That value is the last time the sync was run; with the old interval scheduler LFDS checks hourly to see if (CurrentTime) - (ADGSLastPollTime) > (DesiredInterval). There is no way to use that value to specify a schedule. What I meant by my prior comment is that you can continue to use your current process but a service restart is unnecessary. You will just have less control over when the sync happens (it may happen up to an hour after the value is deleted).

Right ok - my thinking was that if I could force a value in that ADGSLastPollTime that will make Laserfiche think a sync has taken place at a certain date/time so it won't try again for 24 hours past that (our desired interval is every 24 hours). I was hoping there was a way to decipher the format of that value ADGSLastPollTime; but it sounds like you are saying that is not possible.

The format of ADGSLastPollTime is Windows file time in UTC. For example, run 

get-date 132437573498697196

in Powershell and it will return "Saturday, September 5, 0420 5:29:09 AM" (add 1600 years for the current year). If you wanted, you could set that value to some time in the future to delay the sync, but I'm unsure how that would help your situation. Even if you get a sync to run exactly at your desired time and use a 24 hour interval, the syncs will drift later and later over time due to ADGSLastPollTime being set at sync completion, not start. This would necessitate rolling back the last poll time via DB editing anyway.