Slashdot Mirror
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."
Scary headline to read while I'm in the middle of installing it right now!
Never has a first post confused me more than this one. :)
Hey, lots of companies install policies on their IT assets that flat out prevent installing unauthorized patches on corporate systems.
This is a pretty big patch, and people have known for a while that it's going to change the way some things work. It makes sense to show caution before allowing a mass deployment. There's not much news here.
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.
WinXPServicePackNews.com?
Isn't this sort of decision standard in any large organisation? As with any upgrade, IBM will want to ensure that the upgrade isn't going to break any internal applications. No large organisation is going to want employees installing significant OS upgrades without central verification.
Hehe...maybe slashdotters out there have become so overworked that they just moderate you according to your post title. Time to put that theory into practice.
I just installed it and now my I'm getting the BSOD. Dang it! I went to Linux to get rid of the !@#$ BSOD!
Oh, nevermind... my bad. That was just my screensaver and someone unplugged my mouse.
The only thing necessary for Micro$oft to triumph is for a few good programmers to do nothing". North County Computers
Helpful Deployment Tools Here
IBM's technology department has warned internal users to not install Windows XP SP2 until IBM can fix some known issues
And of course, the first thing that happens is, this internal memo somehow finds its way to ZDNet. Looks like PR FUD to me.
It's good though, at least Microsoft gets a little of its own medicine once in a while...
"A door is what a dog is perpetually on the wrong side of" - Ogden Nash
"One IBM employee in the company's internal technology department characterized the decision as routine."
One Microsoft employee in the company's unspecified division of vaguery was alleged to have characterized a response which resembled "We OWNZ you biatch!".
No really, they did.
"It's not your information. It's information about you" - John Ford, Vice President, Equifax
The reason we're being told to hold off is that the new IE might not be compatible with some internal applications on the intranet (stuff like, payroll, expenses claims etc). There's no wording that SP2 breaks stuff in general, just that some critical IBM apps are effected. So stop scare mongering!
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.
A company testing new software before installing it on every system they have? Why I never! Next thing you know they'll be telling us that we should not run every attachment we get in our email.
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.
Its better to have a system with known quirks than an system with unknown quirks
Rus
Cheap UK and US VPS
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.
Every large company has a hold off on SP2 order so their IT staff can hit reload on Slashdot for a week or so to see if any "SP2 sux0rs!!11" stories get posted. If we go 2 weeks without one, expect it to get rolled out.
Another site to check are some of the gaming forums. If it doesn't trash Doom3 and the Slashbots pretending to work don't report problems, it must be OK.
To "fix" Issue#6. Hold down the left-CTRL key when clicking on the link that is being blocked.
So if you deployed a Linux on 10000 machines on all your tech, marketing, IT, sales teams computers, and you had developped specific applications, drivers for some specific devices, and all the crap, you would just tell them: Sure, let's upgrate from 2.4 to 2.6 and cross your fingers?
The fact that they are cautious doesn't mean they distrust SP2. Like any major upgrage to a kernel (to any OS), it is going to break some of your specific devs, would it be only slightly.
This would be true for any OS. The fact that this one is Microsoft doesn't make it something against MS.
Write boring code, not shiny code!
This seems to be a valid theory!
Doesn't look like the theory is applicable to all cases. You need to create a special exception for Trolls.