Wonderful daylight savings

NYSpeed Automotive NYSpeed Off Topic
1

[left]Dear Valued Microsoft Customer,

This year Daylight Saving Time (DST) extends by approximately four weeks. In compliance with this provision in the Energy Policy Act of 2005, DST dates in the United States and Canada will start three weeks earlier (2:00 A.M. on the second Sunday in March) and will end one week later (2:00 A.M. on the first Sunday in November).

In some instances, effort will be required to accommodate the new DST legislation. For example, systems and applications may need to be updated directly, while in other circumstances the application may inherit the date and time information from the underlying system.[/left]
[left] [/left]
[left]Microsoft is committed to helping customers that are affected by the DST changes make this transition as seamless as possible. Microsoft is producing updates for Windows products as well as other Microsoft products affected by the new U.S. statute. These updates will be released through technical support channels including Microsoft Customer Service & Support (CSS), as well as online channels such as Windows Update and Microsoft Update.

Details of the updates for Microsoft Windows and affected Microsoft applications, how customers can acquire them and when they will be available can be found on the Microsoft website at http://www.microsoft.com/dst2007. Corresponding technical Knowledge Base articles are linked from this website as well.[/left]
[left] [/left]
[left]Microsoft is providing the Time Zone updates at no-cost for customers on Windows platforms that are covered by Mainstream Support. For more information on the Microsoft Support Lifecycle Policy including options available for products in Extended Support, please visit http://support.microsoft.com/lifecycle.

Further Assistance [/left]
[left] [/left]
[left]Microsoft values your business. For more information visit http://www.microsoft.com/dst2007, or contact Microsoft for assistance. A list of phone numbers is located at http://support.microsoft.com. Microsoft Premier Customers may engage their Technical Account Manager directly.[/left]
[left] [/left]
[left]Please DO NOT REPLY to this email as this is not a monitored inbox. If you have questions/inquiries please visit http://www.microsoft.com/dst2007

[/left]
[left]This e-mail is intended for distribution within the United States. Please contact your local Microsoft subsidiary for similar offerings outside the US.[/left]

2

Yeah hopefully you don’t have any Windows 2000 machines…Here at work we have roughly 500. They are not releasing a patch for it. :frowning: I’m making a script right now to run a reg file on each pc

3

i forgot that this was going to happen this year

4

So long as machines are a member of a domain, don’t they get their time from one of the DC servers? I would think if you patched the DC that handles time then all of the machines would be ok. Yes/no?

5

This thing could be easily handled by having one or two machines that gets their time from the official US time servers, and having any other machines sync up to them using the built-in windows time service. People are making a bigger deal out of this than it really is.

As 9c1 mentions, DCs are supposed to do this already.

6

Yes…Except I have to go and patch about a ton of Win2k3 servers and we still run some Win2k servers…

7

If you have that many servers, write a script to automate the whole process.

8

I can write a script to query my SQL database of server ips/logins/passwords…login to the server run the update…lol fun

9

Yes buuuuuttttttttt your DC is very particular. If you have a variance of a hour or more the time will not automatically change in WIN 2k. In XP it will. Weird shit. Hence the reason for the patch.

10

If it’s Win2k3 machines why not push it out through WSUS?