SharePoint 2010 Timer Jobs undergo changes are in the management and in configuration. Firstly, the most significant change you will see is that the number of Timer Jobs – new 21 jobs been added. If for an ordinary SharePoint 2007 application we had 39 Timer’s Job, then we have 60 Jobs for SharePoint 2010 So, those 21 new timer jobs are: Application Addresses Refresh Job Audit Log Trimming Delete Job History Document ID enable/disable job Document ID assignment job Ente...

SharePoint provides you OOTB features to run something on regular basis using "timer jobs". You can create you own custom job and SharePoint will handle it using OWSTIMER.exe. There are several resources (1, 2, 3) describing how to create and deploy you custom timer jobs. Unfortunately, SharePoint doesn't provide tools to delete custom timer jobs via Central Administration - you can only disable it, or delete via API - SPJobDefinition.Delete() (sample) There is a codeplex project that install ...

Almost all changes that developers and administrators introduce to SharePoint are completed via “jobs” mechanism of SharePoint (Central Administration –> Operations --> Timer Job Definitions). Your changes are queued and SharePoint complete them when “job” time comes.  It might be a bit frustrating, because all jobs have different timing and SharePoint doesn’t provide you UI to change when jobs start. The only way to change when job starts is using STSADM – ether running a...