Microsoft Charging Businesses $4K for DST Fix 395
eldavojohn writes "Microsoft has slashed the price it's going to charge users on the daylight saving time fixes. As you know, the federal law that moves the date for DST goes into effect this month. Although the price of $4000 is 1/10 of the original estimate Microsoft made, it seems a bit pricey for a patch to a product you've already paid for. From the article: 'Among the titles in that extended support category are Windows 2000, Exchange Server 2000 and Outlook 2000, the e-mail and calendar client included with Office 2000. For users running that software, Microsoft charges $4,000 per product for DST fixes. For that amount, customers can apply the patches to all systems in their organizations, including branch offices and affiliate.' The only thing they can't do, said a Microsoft rep, is redistribute them."
free patches are available (Score:5, Informative)
Really inaccurate story. (Score:4, Informative)
They also provide a variety of workarounds (registry files you can apply, and scripts to apply to a large number of machines remotely) for Windows 2000. If you don't like that, there's unofficial patches as well (http://www.intelliadmin.com/blog/2007/01/unoffic
Yay for overblown stories!
Re:Bastages. (Score:4, Informative)
Re:Screw 'em (Score:5, Informative)
Re:Screw 'em (Score:5, Informative)
As an engineer who is right in the middle of helping our customers make the changes necessary for the DST fix, it is much more complicated than that.
First, you have all of the servers and clients which rely on one another. The biggest effect is on mail - Exchange/Outlook/OWA.
Second, you have to do it in the right order, at about the same time. If you update the server, then clients who schedule appointments will be off until they update.
Third, you've got software which calculates various things based on that date. Think financial transactions, etc.
I've blogged about the tool [cornetdesign.com] we have to help customers figure out what has to be done.
I wish it was as easy as just updating a script, but when you have to coordinate that change across 10s or 100s of thousands of servers, clients, etc, it's not an easy task.
And let's not forget Microsoft isn't the only one having to make changes. Lotus Notes, Groupwise, Blackberries - they all have changes that have to be made. I'll personally be glad when this is all done. Ugh.
Re:Bastages. (Score:2, Informative)
(MS only releases security-related fixes)
there are free utils to patch this (Score:5, Informative)
First link under "freeware downloads".
Re:Bastages. (Score:3, Informative)
TZEdit (Score:4, Informative)
Sun's worse - $10k/server, $150k/max (Score:2, Informative)
We're just modifying the timezone files with zic.
As much as I dislike MS, they're not alone in the highway robbery department here.
Re:free patches are available (Score:5, Informative)
..or just DIY (Score:4, Informative)
Three steps.
1. Create
2. Create
3a. Create GPO to import reg key and run VBScript on Win2k machines at Startup.
or
3b. In absence of AD, modify script to copy itself and
If you're such a small organization that you don't have an I.T. group.. then.. it's probably simple to use TZEdit to update your piddly network.
For fun, you can trick out the script to make sure it only runs once.
Re:Screw 'em (Score:5, Informative)
Not so Crazy... (Score:3, Informative)
Well, that's certainly not the first time F-22's have flown across the pacific, and they never had that problem before. It was because of the DST patch to their systems, the engineers skipped the regression tests that involved the dateline because it was just a patch for the US timezones. Look what happened.
So, while it may seem simple enough to change the DST handling in MS Windows, don't count on it.
Whenever you mess around with time, it is easy to create unexpected results. (cue time-travel jokes)
Re:things that make you go hmmm... (Score:5, Informative)
Talk about tinfoil hats, how paranoid do you have to be to tie a daylight savings change to the Iraq war?
The daylight savings time change is one tiny paragraph of a huge energy policy bill [loc.gov], and by the way provides for a study in 9 months to see if it actually helped, and a potential of reverting back to the 2005 schedule if it didn't help. You may not agree with the policies put forth in the bill, but it certainly wasn't prompted by a desire to avoid appropriating money --- my senators and representative (all republicans) voted against it for anti-pork reasons.
Re:things that make you go hmmm... (Score:2, Informative)
FREE Update (Score:3, Informative)
Always worth a try!
Re:Down with DST! (Score:3, Informative)
Re:Screw 'em (Score:2, Informative)
Re:Screw 'em (Score:3, Informative)
Re:Bastages. (Score:5, Informative)
Open up regedit and go to the following location:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contr
Change DaylightStart to the following
00 00 03 00 02 00 02 00 00 00 00 00 00 00
(Simply we're changing 04 to 03 and 01 to 02)
Change StandardStart to the following
00 00 0b 00 01 00 02 00 00 00 00 00 00 00
(Simply we're changing 0a to 0b and 05 to 01)
Why those changes?
DaylightStart rules:
04 becomes 03 because we're going from "April" (04) to "March" (03). 01 becomes 02 because we're going from the 1st Sunday (in April) to the 2nd Sunday (in March).
StandardStart rules:
0a becomes 0b because we're going from "October" (0a) to "November" (0b). 05 becomes 01 because we're going from the Last Sunday (in October) to the 1st Sunday (in November).
Consider that one on the house. It works for Windows 2000 at least.