Comments on: Daylight savings – Change in politics

By: nephi1

nephi1 — Tue, 28 Nov 2006 09:22:35 +0000

Well I found out that our DHCP server has the time servers already set in them.

Also found what I have been reading is that Windows 2000 (server and Pro), wont autoupdate as they should. And I would need to manually (by script or something) to update the client.

Well I will be testing on over the next couple of days as daylight saving starts on Sunday

By: paul144hart

paul144hart — Mon, 27 Nov 2006 20:18:58 +0000

I would have the servers support NTP (or the microsoft way), then only have them update the time for daylight savings. All logs should be based on UTC so there is no mysterious missing hour or double hour. (The median does not move, only the human perception in time). If you have overseas systems or ship systems that report back to you this is the only way.

By: ursulus

ursulus — Sun, 26 Nov 2006 03:42:54 +0000

Just a thought regarding setting the TimeServers.. should be fairly easy if you’re using DHCP.. set the DHCP server and change the TimeServer in DHCP as this will sort a fair number of clients..

The kerboros authentication may prevent already powered up machines from logging in, but detach them from the network, login, and reboot and attach to network to get new timeserver and they should be ok.

Good luck!

Ursulus

By: nephi1

nephi1 — Sat, 25 Nov 2006 22:45:30 +0000

Thank you for your replies

I will look to for that patch tomorrow.

Also when you set the server to be an hour ahead, does the client update on startup or after authentication?

(Just to get it right in my mind), if there are Kerberos authentication errors, We would have to manually adjust the client time so that kerberos can authenticate correctly?

By: flynavy

flynavy — Sat, 25 Nov 2006 09:04:15 +0000

I think the Win2k servers are more forgiving, but the 2003 servers will start logging Kerberos authentication errors with the time difference. All the 2000 and XP clients can be automatically updated if they use the 2000 and 2003 servers as time servers.
The custom apps may require changing manually if the vendor doesn’t supply a patch and they do not use the machine time for their setting. This shouls be looked at very carefully. If you remember the Y2K issue, some applications went smoothly during the transition and some crashed the applications because of the changes. It doesn;t sound like this is as complex, but not knowing the custom applications, the time could be engrained deeply in the application.