Windows Server 2003/2008 Task Scheduler won't run using a Remote Desktop Connection and FreeFileSync

[sufifus]

Hi folks
Just wanted to share with you that I couldn't test my scheduled backup FFS jobs using Windows Remote Desktop. It took me quite a while till I figured out why my Batch FFS Jobs couldn't be started on the server. The scheduler never opened up a window - although Windows Scheduler told me the job was running - and not ending. So I tried it with the simple Calculator App (scheduled a job that had to open the Calculator). As well this didn't work via Remote. Curious I went directly to the console in the server room - it was a little cold - but everything worked flawless directly via console. Maybe someone from the community knows how to start up a remote connection to the server (Windows 2003) so that the behaviour is the same as with the console.
Hopefully nobody looses time anymore because of this.
Thanks for the great tool - FreeFileSync - is great. As soon as business is improving there will be an according donation.
Keep up the good work.

[goldsun]

Thanks for the information you provided, I have the same problem as you, Windows Server 2003 R2, after a while I will go to the server room to try, and then tell you the results, although Windows Server 2003 R2 is very old, but there are still people in use, and the information to help is getting less and less, I hope to help people in need here.
I come from a non-English speaking country and my English is not good.

[goldsun]

I went to the server room for testing, the software with the scheduled task program has been running normally, but after the test, it is not that the remote and local operation caused by the software can not run, because the Windows Server 2003 scheduled task settings and the current Windows system is very different, now the online setting method is based on Windows Server 2012 or after the new version, The Windows Server 2003 scheduled task settings are not the same, the program runs there do not fill in FreeFileSync .exe, the correct way is to fill in the batch file generated before, the default name is BatchRun.ffs_batch; (the path containing this file) starts with the path to fill in the batch file (excluding the file name). This allows the scheduled task to function properly.
I used this method to remotely set up a scheduled task program for another Windows Server 2003 server, and automatically ran FreeFileSync to backup my files to my NAS at a scheduled time without the administrator logging in.