It would be really helpful to have built in support for running as a service. I'm using it on my Windows Server 2003 box that doesn't usually have a user logged into it. I install it as a service so that I can access it even fresh out of a reboot, and run commands/transfer files.
What prevents you from using Windows Scheduler?
If the server from which it is run is turned off when Scheduler would run the command, then there could be a gap of, say, 24 hours, until the Scheduler ran the command again. If Scheduler were to try to run the command while it was already running in keepuptodate mode, then error messages would be generated.I don't want to run it from Startup since no-one may be logged in.
I would prefer not to run 3rd party tools to force it into Run as a service, so it would be very useful to run as a service, if possible.