HP To Charge For Service Packs and Firmware For Out-of-Warranty Customers
New submitter josh itnc writes "In a move that is sure to put a wedge between HP and their customers, today, HP has issued an email informing all existing Enterprise Server customers that they would no longer be able to access or download service packs, firmware patches and bug-fixes for their server hardware without a valid support agreement in place. They said, 'HP has made significant investments in its intellectual capital to provide the best value and experience for our customers. We continue to offer a differentiated customer experience with our comprehensive support portfolio. ... Only HP customers and authorized channel partners may download and use support materials. In line with this commitment, starting in February 2014, Hewlett-Packard Company will change the way firmware updates and Service Pack for ProLiant (SPP) on HP ProLiant server products are accessed. Select server firmware and SPP on these products will only be accessed through the HP Support Center to customers with an active support agreement, HP CarePack, or warranty linked to their HP Support Center User ID and for the specific products being updated.' If a manufacturer ships hardware with exploitable defects and takes more than three years to identify them, should the consumer have to pay for the vendor to fix the these defects?"
... they sure as hell will now.
I'm not an IT person, but weren't there a few companies that tried this crap wwaayy back when? I seem to remember them all failing miserably.
One more reason to avoid buying or recommending HP to would be buyers. The last thing I'd want to deal with is not being able to get a copy of a firmware update for someone's out of warranty system, server or not because I'm not "HP certified support" or whatever. In 2014, there is no fucking reason whatsoever to not have all issued patches available as direct downloads. This is especially true for legacy hardware.
does not qualify as news
Hewlett and Packard were something special.
Now it's just a bunch of MBAs trying to massage their stock price.
It shouldn't be a legal mandate either. Keeping already released patches available should be a courtesy that all vendors willingly do. The good will encourages repeat buys. Eventually, vendor support will be so expensive and so unappealing that people will just run a free unix on commodity hardware because they get better help from internet forums than they do from vendors.
Ladies and gentleman, this is it.
This is the end of Hewlett Packard.
"Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
Aren't service packs and firmware updates fixes to defective computers/software? Why are they trying to charge for fixing something that is not supposed to be broken in the first place?
Is there something that I do not understand about this?
Yes. They want more customers to pay for support.
What THEY do not understand is that people will start buying Dell.
Wow! What a great reason to avoid buying new server hardware from HP! It is a massive disincentive to purchase. I cannot help but think this is supremely short sighted and a decision made by somebody up high who is not technically inclined.
Look at this the other way. Lets say you sell something you warrant to work for three years. Some four years later, there's some kind of security flaw - why should the company not need some extra funds to develop a fix? To my mind this change is something that will lead to better support for older products, because you can keep on paying and demanding fixes for your payments...
Car analogy! Have you ever heard of a safety recall? You will note that it isn't only new vehicles, or vehicles still under warranty that get recalled. It's ALL the defective vehicles, and the manufacturer has to pay for the repairs. Why you may ask? Because they designed something that is faulty and thus poses a risk not only to the people who bought the car, but to everyone else on the road. Why should software security be any different? If you get compromised, it doesn't just affect you, it can potentially affect a lot of other people.
Now of course for bugs that aren't security related you maybe have a point, if the back seat cupholder tends to break in a car the manufacturer may not be held reliable to fix it, as it doesn't pose a safety risk, but of course not fixing it is sort of a dick move....
Monstar L
Except that due to the extreme complexity of computer products, it's practically impossible to make anything non-trivial that isn't initially riddled with defects.
After all, when is the last time you heard of a recall of a 1978 Chevy? There is a sunset period beyond which no one cares anymore. With the speed of computer development, that period is much shorter than cars.
Absoloutely not! Thats why i always use trustworthy sites like TPB rather than the manufacturers site as they love to ppackage all sorts of crap with their downloads. ;)
I won't touch Cisco gear with a 10 ft pole, and this is exactly why.
On the other hand...
When working in a Fortune 500 company there were some mighty expensive premium contracts with Cisco. Among them was an agreement I learned about when we had an outage late in the afternoon that affected about 15 people. We have hardware that could have affected hundreds of people, but in this case the outage only affected a few.
Cisco found the closest duplicate replacement part in another state, chartered a flight to a nearby airport, had a taxi driver on standby when the plane arrived, and delivered it to our door within about four hours of reporting the fairly minor problem.
I understand the contract is in place because we had hardware that affects hundreds of thousands of people. The Cisco crew was adamant that the contract had a clause that required a six-hour turnaround on any of that class of hardware. If it had been a major device at a major data center those same four hours could have felt like an eternity, so for those people where an outage can cost thousands of dollars every second in lost productivity and sales I can certainly understand the need for the contract with the devil.
//TODO: Think of witty sig statement
You'd think they'd look at what happens to companies candidates had "turned around" in the several years AFTER they left when evaluating CEO, COO, and CFO candidates. But apparently they usually don't.
No, that is part of the scam. The MBA applying for the new job points out how everything went to shit after they left, so clearly their genuius is worth paying big bucks for and any other merely qualified applicant will surely fail in such a high pressure, highly skilled role.
const int one = 65536; (Silvermoon, Texture.cs)
SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
I'm not an IT person, but weren't there a few companies that tried this crap wwaayy back when? I seem to remember them all failing miserably.
If you were a reader of slashdot you'd know that Oracle is suing companies for providing patch access to customers without a support contract right now. And people are finding ways not to be an Oracle customer (right now) as a result. Naturally HP thought it would be a good idea, as they have too many customers.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
Bad assumption. The people making purchasing decisions (especially at large organizations) do not base their decisions on unimportant things like "quality" or "technical factors", they very frequently make those decisions based on 1) initial cost and 2) who they play golf with. I've seen this in action, where the people who actually know things are standing on their heads trying to get management to understand why buying $x is a bad idea for valid technical reasons, and some retard MBA makes the wrong decision because a sales rep bought them dinner at a conference once.
Never underestimate the power of stupid people in large groups.
Bullshit. It's not MY job to keep THEIR lights on. If they want to keep their lights on, give me a reason to buy more products from them. These days, better support and customer service will earn more business than trying to nickel and dime everyone. If HP wanted to increase their sales, they should have improved their support and service instead of decreasing it.
More importantly, it is THEIR job to provide me with a working product. The warranty covers problems with the device caused in the field. If they sold me a product that has known issues then it is their responsibility to provide the fixes, regardless of whether or not I am in warranty. If I plug my 120v (US) router into a 240V (uk) outlet and let out the magic smoke and am out of warranty* that's fair. But if I'm sold an internet firewall that has a secret admin password that can't be changed, it's the company's responsibility to provide the necessary fix so the firewall works as expected.
This should be no different than how automobile companies are expected to act. If a serious flaw is found in a car, it doesn't matter if it is this year's model or from ten years ago, or whether you are the original owner or have purchased it used; you are entitled to that fix. Why some software vendors have somehow gotten it into their heads that they have the right to sell us lemons and then make us pay for the privilege of fixing their mistakes.
* actually, warranty probably wouldn't cover this sort if user-stupidity either, but you get my point ;-)
For far less money than the Cisco support contract, you could have just bought several spares of each model of Cisco device, and have had the replacement on-hand a quickly as you could walk over and grab it.
Perhaps you missed the first part of my post. Fortune 500 data center.
If you are talking about consumer devices and even common office server room equipment that is quite true. We had lots of commodity stuff lying around. We also kept a bit of less common stuff around, such as spare UPS racks; the $30,000 price tag is low enough cost that we could keep a few of them around when equipment shuffles.
Note that some critical equipment gets mighty expensive. You can find a good deal on low latency, high volume interconnect that can handle ten million concurrent connections for around $250K, but you'll probably want to pay around $350K for the better ones. It would be insane to just keep a few of EVERYTHING lying around, just in case. Far cheaper for the Cisco contract that will get us any replacement we need, quickly.
//TODO: Think of witty sig statement
What's even more interesting is that interlocking directorates in the same industry are illegal in the US per the Clayton Act, however the article points out that 1 in 8 interlocks are indeed in the same industry. There's simply no enforcement of this. Thanks again, Obama.
And the previous four administrations. This didn't happen in just the past 6 years. It started a long long time ago, and the Clayton Act, like the Sherman Act, has been out of favor for decades, because it inconveniences people with money.
Thank you Supreme Court for making sure people with money will always have the best government their money can buy.