daylight savings debacle
 

If already posted, tell me. But my EIS group has issued a alert that they may not have Microsoft patches installed in our computers in time for new daylight savings time start date. They suggest printing our calendars and using the paper copies to keep track of our meeting times.


Oh, and the Mac OS has already fixed this issue.SmileWavy

You really need your computer to tell what time it is?

just look at your watch , then set PC clock.

10-4

It is not that you don't know the time or your computer can not be manually adjusted by you, it is the system arranged meeting times that get fowled up.

Just a little of 4 pages of info from EIS.

"Depending on when your system is patched and when a meeting notice was stored on the calendar, there is a risk that calendar meeting notices could be off by an hour. Even after patches are deployed, exisitng meeting set up between March 11 and April 1 will appear one hour off and will not appear correct until the meeting organizers send updates."

Or, set the time zone manually.
You would think the sky was falling around here. All of our midrange OS has been patched. 200 or so servers. JDK's and JRE's are everywhere, since nobody reigned in the cowboy programmers....
TZDB patches EVERYWHERE...

Y2K- NEVER FORGET!!!

LOL!!
There are people here saying it's WORSE than Y2K.
ANYBODY can work in IT here....
Morons....

+ 1

I think that the impact to the user WILL be worse than Y2K. AFAIK, there was no real impact to the user on 1.1.2000, but I am 99% sure you will see a clock somewhere that has the incorrect time in March, and then again in April.

Sure there will be impact, but what's the business impact? In most cases remediation is a TZDB patch OR JUST CHANGING THE FRIGGIN' CLOCK.
Much different activity than expanding fields in in applications and recompiling.
BIG difference....

Because I/you don't work in my EIS? :)

Sounds like you are an Exchange shop. Patching enterprise servers and workstations is not too tough. Even patching the Exchange server is pretty simple. Outlook is the tougher problem. There are 4 solutions. 2 of them have been published for months. MS introduced a 3rd one last week.

The fourth option is what your group is suggesting. It is the easy way out. There was plenty of time to get this done, even in hugh businesses. Get on EIS's case, not anyone else's.

Man, if I miss a meeting in March, big s***. It would be the best thing to happen to me all month.

Re: daylight savings debacle
 

Who would expect microsoft to issue the patch until they stole the fix from someone else, most notably Apple? I received the Apple O/S patch last night, so I guess we will see microsoft's ba$tardized version shortly.

Yes, because with the slew of extremely talented programmers MS has on payroll, they really need to "steal" a fix from Apple, right?

Give me a break, seriously.

And I think Bill Gates owns enough of Apple he doesn't have to steal anything.

And why, exactly, are they going to daylight savings a month early? The news said to save energy. But I've heard nothing about fuel oil shortages, and we've had no rolling blackouts. Oil prices are down, which means a good supply. What gives? Global warming?

I'm not going to like getting my 2 kids ready for school in the dark.

T'was a joke (sans the ubiquitous smiley faces)

I think the whole thing is being way overblown. C'mon, there are TONS of devices that do not auto-adjust for DST and never did, never will. People seem to be spending more time and energy on FUD than just dealing with a few manual clock adjustments...

I am curious to see what happens with my various computers and other stuff that syncs with the NIST time sources.

Re: daylight savings debacle
 

NO. Mac did NOT issue a fix for this issue, because Mac are not capable of having 'this issue'. These issues are related to calendering, which almost certainly means you have an Exchange/Outlook environment. Apple DOES NOT MAKE enterprise software of this caliber, and thus there is nothing to patch.

Grrrrrrrrrrrrrrrrr........:mad:

SO ****** sick of comments from mac users who don't understand squat about enterprise level management issues.

Please spare me comments about Xserve.......

(Yes, I'm tired and cranky. Sorry)