IBM Tells Employees To Hold Off WinXP SP2
robpoe writes "As reported by ZDNet, IBM's technology department has warned internal users to not install Windows XP SP2 until IBM can fix some known issues with the way IE6 is updated, and Big Blue can make a customized version of the patch - 'The company's technology department said the delay is 'due to known application problems and incompatibility with IBM workstation applications.''" However, the article also mentions that: "One IBM employee in the company's internal technology department characterized the decision as routine."
This is very much standard practice here at IBM. We aren't even supposed to use windowsupdate and instead use an internal tool that installs patches.
Of course. No IT department of any size is going to allow end users to willy nilly install or not install OS patches and Service Packs as they choose. Anyone who doesn't use a system like SMS is going to distribute the SP, probably in a customized install, to their users through an official internal channel and say "run this".
The really funny thing is, I don't think there's a big pressing need to install this patch. Waiting a while is the best move to make.
What does this patch do for you? Well, I've been using RC2 for awhile, and here's what it's done for me:
1) Broken Thief III such that when I load levels, my computer crashes.
2) Screams bloody murder when an app opens a port - except for loopback - but even when I explicitly wanted that port opened it still raises a dialog.
3) Messed up MSN Instant Messenger's hotmail addin so it now links to Outlook and Outlook Express even though I don't even USE Outlook.
4) Messed up my MSN Instant Messenger buddy list by trying to group them into random categories I didn't even want
5) Installed more gooblygook into Windows Media Player that asks for copyright protections etc that I don't want and makes me go through the configuration screen all over again
6) Added a popup blocker I didn't want - that I can't easily turn off - into IE - that conflicts with Google Toolbar - instead of one easy click to get a popup on a site that you were expecting to pop up (such as a separate chat window for customer support), you now need to go into the options to turn popup blocking off, then click the google toolbar... twice the hassle.
And other nice oddities.
I say, wait until this beast has been patched...there's nothing worth running out for.
Tepp
I used to work desktop support for IBM and can tell you that IBM has its own web-based software distribution and installation service that it uses internally. The same thing was done for SP1 - users were told not to install from Windowsupdate.com and were instead told to install from the internal servers after the patches were changed to work better with the IBM internal machines - this is because there are modifications made to the Windows image used in system builds resulting in a custom IBM build of Windows so to speak. No real shocking news here.
Specifically it was NOT addressed to clients (note Sam doens't call them customers anymore).
It was a letter on the IBM Intranet addressed to the 300,000+ IBMers (for reference, I am one. I've read the letter. Of course, I do NOT speak for IBM). The letter does not mention specifics, but IBM develops a TON of software for use internally. These applications have to be tested with SP2 before they release SP2 internally.
This is completely routine, and has been done on many patches before this one. It is IBM being cautious and testing a new component with the thousands of other pieces of software that keep IBM moving. I for one, am glad our IT staff takes the time to do this.
The funny thing is the last sentence of the story: "One IBM employee in the company's internal technology department characterized the decision as routine".
So a routine decision makes the front page of Slashdot, clearly advertized as "IBM doesn't trust Microsoft".
The basic anti MS movement is still out there.
Write boring code, not shiny code!
"Sexy Man" is not an moderation option.
Analogies don't equal equalities, they are merely somewhat analogous.
To "fix" Issue#6. Hold down the left-CTRL key when clicking on the link that is being blocked.