Am I wrong to think that Scheduled Windows Tasks running for example a console app can achieve everything that a SharePoint custom timer job can?
This has been my experience so far.
However, a C# Console app running as scheduled task is :
A. Easier to code - no learning curve required for a C# developer
B. Easier to deploy and redeploy, this really speeds up development if you're doing a lot of testing and incrementally updating your job. With a console app you could copy it to a network share, with a SharePoint custom timer job you need to RDC into the server, and it is about 5 steps you need to redeploy. You might say you can use powershell, yes you can but with the console app it is just pure convenience.
C. All the SharePoint purists out there thinking in the SharePoint box want everything housed under one roof - this isn't a good enough reason to add so much complexity to the job development and deployment process.
So what are the good reasons to use SharePoint custom timer jobs over Windows Scheduled tasks?