Page 1 of 1

Scheduling with .\cmd\custom\RunAll.cmd

PostPosted: 13.03.2015, 21:10
by Dennis
I have ran the software & selected 'Create collection script' which I have then setup as a Scheduled Task. I am able to run the batch file manually and it works correctly, however when I create a scheduled task, it does not work. I have looked through the log files and see no appended logs from the time it is set to run (Every Thursday)

I have tried running it as SYSTEM and as my user, with no luck...

http://gyazo.com/367f411b3adee36b34aa1c5447ac2bc8
http://gyazo.com/b7661162de711faba41b4aea7d5818c5
http://gyazo.com/401817a4e117a31fba1fd1cd768f5620

Re: Scheduling with .\cmd\custom\RunAll.cmd

PostPosted: 14.03.2015, 07:02
by aker
Please try "cmd.exe /c <path to your RunAll.cmd>".

Re: Scheduling with .\cmd\custom\RunAll.cmd

PostPosted: 25.03.2015, 15:07
by Dennis
Thanks for your reply... I believe I have understood your instructions correctly, and did the following. I have triggered a manual run of the scheduled task, I will check to see if the logs show any activity after a bit... Thanks again

http://gyazo.com/19d3636d15ef517395b47daa727de65a

Re: Scheduling with .\cmd\custom\RunAll.cmd

PostPosted: 25.03.2015, 19:19
by aker
Just check, if the file C:\Windows\wsusofflineupdate.log exists and if it contains an entry for your run.

Re: Scheduling with .\cmd\custom\RunAll.cmd

PostPosted: 31.03.2015, 14:43
by Dennis
I have checked the log file per your recommendation, and its a negative, the package still isn't running, that or it's trying to run and erroring not sure which. Jan14 was the last log entry... Now, with that in mind, I know I have manually ran the updater since then... Perhaps it is running correctly, and the logging isn't working properly?

Wed 01/14/2015 17:32:21.2

Re: Scheduling with .\cmd\custom\RunAll.cmd

PostPosted: 31.03.2015, 18:12
by aker
And C:\wsusoffline\log\download.log?
Could you post the content of your RunAll.cmd in [code]-tags?