SP2010 Timer Jobs Overview


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:
  1. Application Addresses Refresh Job
  2. Audit Log Trimming
  3. Delete Job History
  4. Document ID enable/disable job
  5. Document ID assignment job
  6. Enterprise Server Search Master Job
  7. Health Analysis Job
  8. InfoPath Forms Services Maintenance
  9. Password Management
  10. Prepare query suggestions
  11. Product Version Job
  12. Query Logging
  13. Secure Store Service Timer
  14. Solution Daily Resource Usage Update
  15. State Service Delete Expired Sessions
  16. Timer Service Recycle
  17. Web Analytics Trigger Workflows Timer Job
  18. Windows SharePoint Services Usage Data Import
  19. Windows SharePoint Services Usage Data Processing
  20. Word Conversion Timer Job
  21. Workflow

sharepoint2010CAmonitorTimer Jobs management belongs to the “Monitoring” group of SharePoint 2010 Central Administration, that provide two options “Review job definition” (was “Timer job definition”) and “Check job status” (was “Timer job status”)





The new features of all these screens is “Timer Links” menu, that allows you to manage all jobs from the single screen, so you don’t need to navigate back to the Central Administration to switch on another screen.
sharepoint2010timerjobslinks
Check Job Status changes
Changes of job status screen are minimal:
  1. You can see the jobs grouped by status – Scheduled, Running and History, instead of just a list of all jobs.
  2. Ability to edit the job property from the status screen – all jobs are hyperlinks. Previously you can’t do this.
sharepoint2010timerjobsgroupped
Review Job Status changes
same screen with the list of all jobs.

Set or edit Timer Job
The change of edit time jobs are in the ability to change the time when the job starts via UI (previously you should do this via STSADM) and run job immediately
sharepoint2010timerjobsproperty

PowerShell Commands for TimerJob
STSADM console command is still supported in SharePoint 2010 but the main accent id made on PowerShell (there are about 500 new commands). Thus, you can use the following PowerShell cmdlets to manage your Timer Jobs:
  • Disable-SPTimerJob
  • Enable-SPTimerJob
  • Get-SPTimerJob
  • Set-SPTimerJob
  • Start-SPTimerJob

Comments

Post a Comment

Popular posts from this blog

IRM and the Object Model

A couple of weeks earlier, I saw an interesting issue. It was a normal day as far as days go in support and in comes this issue, where the person in question wants to investigate or rather should I say automate the process of creating IRM settings on document libraries. I wasn't working on this issue and a colleague took this over. But then somewhere it was lurking, how the hell do you do that? The natural starting point is getting a site/web context and going down to the list and then getting dirty with the properties exposed by the particular SPList object. So after finishing what I had on my plate, I dug into figuring out how exactly to set the IRM settings for a list using the object model. So here goes: Step 1 Enable IRM on the farm SPWebService svc = SPFarm.Local.Services.GetValue<SPWebService>(); SPIrmSettings irmSettings    = svc.IrmSettings;irmSettings.IrmRMSEnabled    = true;//set true or false based on the situation irmSettings.IrmRMSUseAD      = true; irmSett
Read more

This content database has a schema version which is not supported in this farm

Image
 Today i have faced one issue while mount content database to server. the issue is " This content database has a schema version which is not supported in this farm." I was getting this error when i ran Mount-SPContentDatabase using powershell.  I tried checking SP versions and other things finally got solution in below way Reason: Once you have taken the backup from SharePoint 2013 content database, usually you will restore the database in the target SQL server. After restoring the database, you will try to restore content database in any one of Webapplication most probably new one. In this stage, you will get the above error message. Solution: Your source SQL server schema and the destination SQL server schema might not be matched. So you need to update the "Versions" table values in the "Restored Database". 1. Open " Versions " table from any of the existing "Content database"  from the Target SQL Server machine in "
Read more

Activate and Deactivate Feature through PowerShell

Image
I was looking at the analytics of the site the other day and I noticed that my post,  Adding and Deploying Solutions with PowerShell , currently has the most traffic on the site.  I had always intended to write a follow up post on this, so here it is.  Today I’m going to talk about how to enable and disable features using PowerShell.  It’s great that you know how to deploy solutions now with PowerShell, but now you want to activate your features. In SharePoint 2007 to activate a feature from the command line you might have used a statement like the one below.  I’ll use the  Reporting  feature on my server named  sp2010  as an example.  The value specified in the  name  parameter refers to the actual folder name of the feature that is in your SharePoint Root folder (14 hive). stsadm.exe –o activatefeature –name Reporting  – url http://sp2010 To get started with PowerShell, run the SharePoint 2010 Management Console located in your Microsoft SharePoint 2010 Products folder on your s
Read more