steve1673

Changing the schedule to daily did work, up until this week. It's now 15 minutes past the expected start time of the scripts and nothing has happened. (verified in the execution history). At this point I'm not sure if this is going to kick off sometime unexpected, so I'm going to need to disable scheduling again. Is this an issue with the DST change? Perhaps we should move everything to UTC?

thanks, I'll try that out.

I've been trying to automate as many of my maintenance tasks as possible with Pulseway, but I've noticed that the scheduled start time does not correspond with the actual start time. It's not consistent though, so it doesn't appear to be a time zone issue. Here's some examples: Sample: Cleanup Temporary Files Weekly on Thursday starting on 29 December 2016 at 20:00 16 February 2017 21:39 Took 8 seconds Result: Successful 15 February 2017 20:00 Took 15 seconds Result: Successful 8 February 2017 20:00 Took 15 seconds Result: Successful 1 February 2017 20:00 Took 22 seconds Result: Successful 25 January 2017 20:00 Took 1 minute and 42 seconds Result: Successful 18 January 2017 20:00 Took 18 seconds Result: Successful 12 January 2017 22:06 Took 1 minute and 3 seconds Result: Successful 11 January 2017 20:00 Took 20 seconds Result: Successful 4 January 2017 23:56 Took 10 seconds Result: Successful Other tasks have the same issue with scheduling. While basic maintenance scripts like time syncs, temp file cleanup are not time sensitive, Other tasks are. I have my complete weekly patch and update sequence saved as scheduled tasks, and I can't use it because the scripts are not guaranteed to run during my maintenance window. Any ideas?

done, thanks.

Any ideas what's going on with the main PW website? I've been getting 403's since last week. (tested from multiple systems, sites) If i keep trying, I'll sporadically get good pages, but not often. Finally got my account renewed after 3 days of trying.

I've got a similar issue.... when running the "check, update and restart" command against individual computers or groups, pulseway handles the critical updates just fine. It doesn't install the optional updates however. (Each computer has been configured to download the optional updates within the windows update settings dialog) So when patching a large group of systems every week, I end up having to go to each one individually, selecting each optional update manually (can be lots), and installing and rebooting them manually. To be honest, if I'm having to do all this manual work on every system, then pulseway isn't going to scale well for us. (side note) - all our systems pull updates from WSUS, so the optional updates have already been vetted and approved there. Is there a way I can get pulseway to handle the optional updates when I run the update command? It may be the insanity talking, but I thought pulseway USED to do this. Thanks, Steve1673