Steve08

Yeah, that's what I figured - though as I say, it seems a pretty obvious "feature" to have an option to have the server do this automatically, and I am quite surprised there hasn't been enough "demand" for it to make it happen. I want the server's system clock to show the correct local time, but have a number (8, to be precise) schedules that need to run at a fixed time (GMT), and it's a bit of a pain to have to manually reset these twice a year.... ah well, so be it. Cheers....

It seems somewhat extraordinary to me that TS doens't have an option to automatically deal with DST, and move schedules back or forward an hour as appropriate when the system clock changes due to this. Or have I missed it? cheers Steve

Are you trying to run Visual Studio on Windows Server 2008? I have to wonder why - as the name implies, Windows Server 2008 is an OS optimised and developed for a server - it's not really a development OS... but I can't be of any specfic help I'm afraid, unless you've installed a beta version of the SP. Google it - there are known issues. Installer 4.5 is available from Download details: Windows Installer 4.5 - first result found by putting "microsoft installer 4.5" into Google....

Hi - sorry if this is a bit late, but I've been using Ability Mail Server on a couple of client's servers (it comes with a webmail interface, inter alia) and have had no problems with it. Good support too. Happy to recommend it.

OK, So Microsoft recognise the problem too... The value in the Next Run Time field in Task Scheduler is incorrect in Windows Vista and in Windows Server 2008 Glad to know ot wasn't just me being daft!

Final update: OK, I get it now - that about filling in the "Start in.." box is needed in order for the task to run, but the repeating ad infinitum thing is different - figured it now: Consider this task trigger: Start at 10:00 and repeat every 2 minutes for 10 minutes. If you refresh Task Scheduler at, say, 10:05 you will see the "Next run time" as 10:06, as expected. If you refresh again at 10:11 you will see it is blank. The task has finished. Now set it to repeat on a daily basis, and refresh as 10:11. Instead of seeing the "Next run time" set to 10:00 the following day, in fact it is set to 10:12, and continues to re-set itself every 2 minutes BUT the task does not actually run until 10:00 the next day!! Daft, or what?

Re: Scheduled task repeats ad infinitum.... [update sorted] Turns out the solution is that when setting the schedule and entering the application to run, it is also *essential* (NB not optional as it says) to fill in the "Start In (oprional)" box. Nice one, Microsoft...

Re: And another Task Scheduler problem.... [update - sorted] OK, so the task DOES run - but in Win2008 it runs without a GUI - the only way to knwo it;s running is to open Task Manager and watch the process start (and stop) there. Now I know...

Hi, it's a Perl script file, which doesn't run for long. The thing is, I have the same set of scheduled tasks running on another server (Windows 2003) without a problem, it's just on the 2008 server that this is happening. It's all very odd...

I want to schedule a task that opens a webpage on the local server. I know the path is correct, adn that the site is functioning. I can type: "C:\program files\Internet Explorer\iexplore.exe" (path to local webpage) in to the "Start/Run..." dialog and this launches the webpage in IE. Fine. But when I set my task, nothing happens at the allotted time - even if I try the "Run on demand" option, nada. I get an 0x41306 (or 1) "Last run result" show. Makes me wonder if there a setting somewhere wihtin IE perhaps that prevents it from being launched via a schedule? If so, or if anyone has a better idea, I'd be most grateful to know what it is... Many thanks... (no more problems, promise! :o )

HI, I have a task that is required to repeat every 7 minutes for 100 minutes. I have set the obvious things, but when it runs it just carries on past the 100 minutes, forever (or until I disable the task.) It seems odd to me that there are two places within the Task Scheduler settings dialogs where this limit can be set: a) Within the "Advanced settings" of "Edit trigger" within the "Triggers" tab there is: "Stop task if it runs longer than..." option, and, b) Within the "Settings" tab itself there is another "Stop task if it runs longer than..." option... I wonder what happens if one sets conflicting values? Anyway, I haven't - I have set 100 minutes in each case. adn the summary it displays for me indeed says: "After trigered, repeat every 00:07:00 for a duration of 01:40:00" - which is correct. The task runs under admin priveleges. So where do I begin to look for what's goiung wrong? Any ideas? Thanks...