We recently got a new Windows Server 2008 R2 64bit server set up and moved the WFE over to it. (I was on Windows Server 2003 32bit). I joined the new WFE to the farm, stopped services on old, started them on the new and then removed the old server from the farm. But now in my timer job status, I see double of all the jobs: one of each referencing the old server and one of each referencing the new server? How can I clear out the statuses of jobs referencing the old server?

You could try flushing the file system cache on each of your servers to resynch your timer job definitions. Good instructions here: http://blog.camantrix.com/sharepoint/ Regards John Timney

I did findthose same instructions on a different site. The only difference was that it said to reset the cache.ini to 1 instead of 0. It didn't do anything for my timer job status issue. I will try changing to 0 and see if that makes a difference.

Any luck with this? Regards John Timney

Sorry for the delay. I followed the instructions at http://blog.camantrix.com/sharepoint/ and I still have duplicate timer jobs, one referencing the old server and one referencing the new server. After the GUID.xml files were recreated, the value in cache.ini was the same as before I deleted all the GUID.xml files. The end of the post states "You have just synched all your servers with the same timer job definitions from the config db." So my file system cache has been flushed but it seems like my config db still has the old definitions. How can I clean out these old definitions from my config db?

Sounds obvious - but have you tried simply deleting the timer job you no longer require? In Central Administration under Operations click Timer Job Definitions link. Move your mouse over the job you need to delete and it wll show its GUID in the sbrowser tatus bar As long as both jobs have different GUIDS, you should be OK to try and force delete it via stsadm. Delteconfigurationobject should remove it. stsadm.exe -o deleteconfigurationobject -id <GUID> Regards John Timney

The Timer Job Definitions list is correct. It only shows one of each per web application. If I look at the TimerRunningJobs table in the config db, I see the duplicates. For example, on Timer Job Definitions page, I have two "Immediate Alerts", one for each web application. Hovering over those names, I get these two GUIDs: 70337bb8-53f7-4ba5-a3e2-0aea48f575ab and be4ce843-e4ca-4a12-b10c-6ed92219a7f0. When I look in the Timer Running Jobs table, I see 6 rows with JobTitle of "Immediate Alerts" (see below). So it looks like I have instances of those GUIDs for both by old and new server, but additionally I have 2 other unique instances of "Immediate Alerts" on the new server. My guess is that I should only have one unique instance for each web application. ServiceId VirtualServerId JobId JobTitle ServerName Status StartTime CurrentTarget TargetCount CurrentTargetPercentDone 30cf87c9-6675-4c36-9b19-7744ae84666c d2b71fa5-8e54-42c2-bad7-6a4c2b7df4dc 7e583068-479f-425e-884b-f936a9267ce6 Immediate Alerts NEW_SERVER 2 2009-11-30 23:00:07.170 1 1 NULL 30cf87c9-6675-4c36-9b19-7744ae84666c a8b942fb-f8d7-4d30-b1c2-6f2ec4806664 be4ce843-e4ca-4a12-b10c-6ed92219a7f0 Immediate Alerts NEW_SERVER 2 2010-02-04 14:30:00.480 1 1 NULL 30cf87c9-6675-4c36-9b19-7744ae84666c a8b942fb-f8d7-4d30-b1c2-6f2ec4806664 be4ce843-e4ca-4a12-b10c-6ed92219a7f0 Immediate Alerts OLD_SERVER 2 2009-11-30 18:05:19.143 1 1 NULL 30cf87c9-6675-4c36-9b19-7744ae84666c 4c342a73-2b40-4bb3-b5d0-c56f95ff0427 c9508d31-dc7c-4940-8ba4-ceec9ffd3b4e Immediate Alerts NEW_SERVER 2 2009-11-30 22:20:45.683 1 1 NULL 30cf87c9-6675-4c36-9b19-7744ae84666c 263732c8-58e0-4c53-8ef3-e502334327f5 70337bb8-53f7-4ba5-a3e2-0aea48f575ab Immediate Alerts NEW_SERVER 2 2010-02-04 14:30:24.480 1 1 NULL 30cf87c9-6675-4c36-9b19-7744ae84666c 263732c8-58e0-4c53-8ef3-e502334327f5 70337bb8-53f7-4ba5-a3e2-0aea48f575ab Immediate Alerts OLD_SERVER 2 2009-11-30 18:05:33.150 1 1 NULL