>>>I think that's possible indeed, need to setup the scheduler so it works also when no one logs into the server. We have had problems in the past because the server would restart during the night because of a Windows update, and there is no log in. But maybe this issue has been solved.
>>
>>There's a checkbox in the setup of the task scheduler to do exactly that. The larger problem is the account under which it runs, which will cause problems later. Usually the admin doesn't remember or even know that it is used for a scheduled task, and sets it to expire the password. The task simply stops running when the password is changed and the new password not entered in the scheduler, and nobody notices that for days (depending on the importance of the task). Or, if you're lucky, its password is set to never expire, but the never expires when the admin leaves and the new one notices a security breach: aaaahhh I have an account whose password never expires, panic, change that asap. About 90% of the problems I had with the 30-60 installations of several scheduled tasks were of this kind.
>
>There would be the advantage of the service, because it does not depend on a user account. The problem for the service would only exist, if the service needs rights on the network, then you would also need to setup an account for that. But an ftp download should not need any log on, can write to the windows events and send status emails.

IIRC. _anything_ under windowses needs an account under which it runs. Services mostly use system accounts, which generally solves the rights. FTP would need to access the port and the folder where it reads/writes the files, which isn't much. You only need some strong account which would have the rights to set up the service.