As I understand it there are two timer jobs related to the Document ID service: the Document ID assignment job, and the Document ID enable/disable job. But is there something else in the mix? I ask because we are in the process of removing a custom document ID provider and it seems that changes to the Document ID settings (at the site collection level) don't come into effect shortly after both those timer jobs have completed. It takes much longer - overnight - which suggests to me there is another job that must run to implement the changes.

Has anyone else run into this?

Thanks,

Hi Tom,

Only the two job are there.

http://www.mavention.com/blog/demystifying-document-id

http://blogs.msdn.com/b/chunliu/archive/2011/07/27/details-about-how-document-id-service-is-activated.aspx

If that is the case, then why does it take so long for changes to be reflected?