Daylight savings – Change in politics

pts.
Tags:
Database
DataCenter
Hardware
IBM DB2
Linux
Management
Microsoft Windows
Networking
Oracle
OS
Security
Servers
SQL Server
Greets to all, First off, where I live (WA, Australia) we have had a change in politics. We now have daylight savings starting in 1 week. The problem is as follows. Details * 3 Domains (not linked to each other) * Multiple external sites (not tied back to base) * Multiple DB systems and authentication systems tied together * Over 200 PCs (most are connected to the domains, but a fair few are not) * OSs = Windows 2000 (Server & Pro), XP (some), 2k3 server and some linux servers * VPN links from US/Sweden/Australia Now the problem is, how to we get all the PCs to change to daylight savings when all the software written for WA all take the stance we dont have daylight savings at all (look at Windows for example). Now we know we can get the servers to go an hour ahead, but the next problem is the client PCs and all the custom software packages may fail because of the time difference. Now first off, if we get the servers to move forward an hour what will happen to the clients when they start up the next time. Will they (A) Fail to do anything but be standalone. (B) Fail to update the time (C) Work correctly. Next the custom software, do we speak to the manufacturers and see if they can release a patch for it. Or just manually adjust them to the new time or change timezone Any suggestions on what to do and how to do it.

Answer Wiki

Thanks. We'll let you know when a new response is added.

Microsoft has posted an update to Windows XP that resolved this problem. They MAY also have updates for other Windows versions (I haven’t checked).

Jay

Discuss This Question: 5  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • FlyNavy
    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.
    0 pointsBadges:
    report
  • Nephi1
    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?
    0 pointsBadges:
    report
  • Ursulus
    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
    0 pointsBadges:
    report
  • Paul144hart
    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.
    0 pointsBadges:
    report
  • Nephi1
    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
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following