Comments on: Few glitches after daylight saving shift

Earlier than usual switch to daylight saving time causes some snags, but no major disruptions are reported.

[Seaspray0]

Get update here - free - from microsoft

Microsoft has provided FREE instructions to everyone on how to update your computer. I've already seen claims that MS is charging for a patch and you can get it from us for $.... Well, here's how to do it for free, and directly from MS.

http://support.microsoft.com/kb/914387/en-us

The instructions are detailed and even provide the notes on how to publish to your computers on a domain or simply do a single computer.

[Arrgster]

They were charging for 2000 systems

Still had a few but we just used a free third party patch.

[Microsoft_Facts]

Only Microsoft systems had any problems at all

My *nix/Linux, NetWare systems had no problems. But random Windows systems decided to ignore the new DST systems. Out of about 80 Windows servers, 20 of them Win2000, 10 of the 2000 servers and a few 2003 servers just totally ignored the new DST settings. We had to manually push them to change with "net time" commands. Some we had to use the GUI time applet to disable/re-enable automatic adjust for DST to get them to sync up. 400+ Unix and NetWare servers, not a single problem. The morale of the story? Once again Microsoft products highlight the inconsistencies and unreliability of MS technologies.

[Arrgster]

Same here

I didn't have to do anything with the red hat servers, but the MS ones were all a pain. One domain controller with win 2003 even crashed on me after the update. Got stuck at the preparing network connections screen. Had to reinstall the NIC drivers, not sure what that has to do with DST but then again I didn't write the software...

[RealWorld2]

Rich Kaplan lies

Few problems? Rich is clearly not paying attention. He is right that we lost no data, but to say this was just a annoyance is incredibly misconstrued. Outlook/Exchange - with all patches applied - didn't handle the "gap" appointments. Recurring events that were entered before the MS patch date were correct up to March 10, one hour late from March 11 to March 31, and CORRECT again on April 1. Individual appointments, however, remained correct. So called "standing meetings" are wrong for 3 weeks - and they're now mixed with single appointment that are correct. I invite Mr. Kaplan to "re-phrase" his comments and reflect a more accurate notion that the patch was flawed.

[alexei_roudnev]

Smoothly?? not!

Hmm, change run well, yes?

Not true at all. Win2K was not patched by Microsoft (I am not talking about older versions), and few unofficial patches was around. Even when patched, patch apply only when you logout and then login.

It is not the worst. Oracle Grid agents died if server was patched and agent was not (and not many expected that thhey muct patch agent, released only 1/2 year ago or less). And I expect many other problems.

Moreover, some problems can appear later, when reporting software run and make reports; some appear in the end of month when time shifted before.

20 alerts from dying Oracle agents != smooth. 4 places to patch on each Oracle server (OS itself; jre in oracle, jde in oracle; oracle zoneinfo) is not a small patch. I am pretty sure that many MS application experience the same problem, too.

[Vegaman_Dan]

Non Issue

The news hype was far bigger than the actual issue itself, which with Apple and MS releasing updates, wasn't really an issue at all.

[superdave132]

no big issues except xm radio clock prob!

xm radio clocks didn't take to the shift and xm is working on it.

[trevors99]

Smoothly at Microsoft

Since Vista had the new DST rules built-in, I would have expected things to go "smoothly" at Microsoft, at least from their end-user perspective.
Most of us outside MS are still on XP, however...