ok so I recently installed Business protection on a few servers and everything works just fine, except for the scheduling of tasks… what is going on is I have the full system scan task set at the console for 23:55 on a thursday, and when I open the avast client “on either workstation or the same server that runs the console” it states that this task is scheduled for 05:55 on friday. If I alter the time on the console the client will translate the time forward 6 hours. I can see that this is quite possibly a timezone issue between client and console buuuttt like I said the client on the server that runs the console as well has this 6 hour delay… so is there a time zone setting in the console or does it run off the timezone from which avast originates??
whats the time in the BIOS of your the server?
what is the time on windows?
Timezone in windows is set correct?
Yes, I am in CST and they are all set correctly, I guess I didn’t state this, but this is happening in multiple environments that I implemented Avast Business Protection in.
As stated before, the same server that runs the console also has the 6 hour delay on scheduled tasks. almost like theres a setting in console that I have missed that maybe states the time zone?? is there such a setting in console?
I think I have noticed this on occasion.
its quite puzzling really… was your delay 6 hours?? and if so are you in CST or what time zone are you in? if you have a different delay time and are in a different time zone this will help us clue into what time zone the default is. if this is even the problem.
Things weren’t running at the right time after the clocks went back at the end of daylight savings. What I think I ended up having to do was set my jobs ahead a few hours and save, then set them to the time I wanted.
You could try setting up new jobs with the time you want and see if that works.
BTW I am EST.
Ohh ok thanks, and yeah ive already implemented the time difference but I just feel thats a little “rigged” and would like to figure out what is going on.
Did this problem occur after daylight savings happened?
if so did redefining the time window for the job solve the problem?
NO it did not happen after daylight savings time. I just set it up within the past month and it has done it since I set it up.
What version are you using?