Timezeone, sync and windows scheduled tasks

[ski.z.goggles]

I have 2 VDS, both in NY. I just noticed that they were both running on Pacific time, but the clock showed the correct Eastern Time.

1. Noticed that Windows is unable to sync with time.windows.com (which would explain why its on PT, but the clock shows ET)
2. I have a number of scheduled jobs for Db backups. 12:15am/6:15am/12:15pm/6:15pm - run on time. 3:15am/9:15am/3:15pm/9:15pm run an hour early. I'm guessing that it has todo with daylight savings time - maybe I created them before or after. Not sure. I'll recreate them and see.

#1 is really the one I'd like to get resolved.

[Edge100x]

The Microsoft time servers are pretty flaky in general, and it's also possible that upstream filters are affecting traffic from them.

Have you tested with time-a.nist.gov, time-b.nist.gov, or time-c.nist.gov? They are reliable and should always work.

The machines running our VDSes are also synced to the correct time and have the correct local timezone set, so after each reboot, your VDS will be using that time (unless you've changed one of the time-related settings in your control panel).

[ski.z.goggles]

all of the windows sync addresses get errors. Both servers are in NY and I never touched them, so they were set to Pacific from the start. None of this really affects using them, but I think there is some setup/network/etc issue.