Slashdot Mirror
Microsoft Piracy Plan Means Concerns for IT
coondoggie writes to mention an article on Information Week about possible unintended consequences of the Microsoft Software Protection Plan (SPP) discussed on Slashdot on Wednesday. The new initiative is intended to protect consumers from pirated software, but may cause major headaches for IT shops. From the article: "Microsoft will support SPP in current and future reporting and asset management tools such as System Center Operations Manager. 'On paper it might sound pretty good, but we have to see how it works,' says Jeff Allred, manager of network services for the Duke University Cancer Center. One of his concerns is that a reduced functionality mode kicks in three days after changing out a motherboard in a server if the software is not revalidated. 'That really jumped out at me. We change out motherboards in our servers all the time,' he says. The provision only covers a swap with a non-OEM motherboard, which Allred admits doesn't happen often."
Do you guys do that crazy thing where you, you know, verify the links in a story before clicking the Post button?
Protect consumers from pirated software??? What if I don't want to be protected???
To avoid all the problems with Vista, don't install Vista. Voila. Problem solved. It's like upgrading your OS every time Microsoft puts something new out is a disease that IT suffers from. There are companies who never upgraded NT 4 or 2000 who are doing just fine.
Read my short stories - You won't regret it.
I believe this is the correct link to the story: http://www.networkworld.com/news/2006/100506-micro soft-antipiracy.html?t5
You can't underestimate the lowest rank of society, but I think a large portion of the general population would understand the issue a lot more if the mainstream press were to rephrase all those headlines by one word:
[
Uh, it sounds like you need to find a better vendor if you're changing out motherboards "all the time".
I don't reply to Anonymous posts; if you have something to say to me, identify yourself or I won't reply.
Yes. You've obviously never worked in corporate IT. When a server is down, the last thing you're worried about is contacting the frickin' vendor to get the OS activated. Servers in the corporate datacenter aren't likely to have Internet access. So to getting it activated is going to likely require a phone call. Every minute that server is down, it's costing the company $$$ in lost productivity. And what if someone forgets to do it? Ouch.
My blog
...from pirated software"
Yes, Microsoft designed and built that to protect us hmmhmmm.
the mods may say you posted flamebait, but to me it's a flame that warms my heart. rock on, brother! --chebucto
Well, the article is Slashdotted, but I don't need any expert opinion or research to tell me what it means for IT. I'm the head of an IT department, and it means that I'll be avoiding updates to any Microsoft technology with any "Piracy Prevention", and when I do need an upgrade, I'll be looking for Microsoft alternatives. I have friends who head IT departments, and I'm getting the same sentiment from them.
Not because we pirate. We're too afraid of the BSA sniffing around to do that. The problem is, these things cause problems, artificially created by Microsoft, for no reason. To stop piracy? If I pirated software, then I'd know where to find cracks for these things. Microsoft's "protection" wouldn't stop me.
But I've made a general policy in my department that we've stopped purchasing or installing software that requires "activation" or any other kind of phoning-home. I've run into too many problems where an otherwise working computer breaks itself by the developers own purposeful code because I've done a normal, legal repair job. In a large organization, an instance of the IT dept. replacing some hardware or imaging a disk shouldn't trigger a flag as "suspicious activity".
In my organization, I think we're likely to have more Macintosh purchases. Users like them, they're easy to fix, disk imaging is INCREDIBLY easy, they're reliable, and they work great with our Windows and Linux servers. And we'll see more Linux servers. If Microsoft wants my business back, they can stop trying to limit their OS to do less for me, and start working on how they can improve it to do more for me.
Let me raise a very viable scenario that may not have been presented. This is that the system reports a false positive for pirated hardware. Now, the person quoted in the submission works for the Duke Cancer Center; this might mean they get the same licensing deal that the university presumably gets. Now, let me use an example I am familiar with.
At Ohio State, one of the most populous universities in the country, they have a deal with Microsoft that gives students access to Microsoft software on the cheap. At the same time, this deal applies to departments and other machines for the university. Since this deal is based on mass distribution, and in many cases does not include permanent media, if any media at all (basically, students take the disks, install the software, return the disks), everyone uses the same key. This is the case for XP and Server 2003. It is also the case for 2000, in fact the key is "embedded" on the Win 2k disk, so no input is required from the user.
Now, let us assume that OSU has about 50,000 students (not too far off actually). And each student has this version of Vista installed. Now, let us assume each department is using Windows (actually very few at OSU are not), that is even more copies of the software being used. I would venture that it might not be too far fetched to assume that OSU could have 100,000 or more copies of the same OS installed on various student, faculty and departmental machines. Now, the server installations are quite a bit fewer; however, I do know the department I worked for already have several (as in 8-10) servers running various Windows versions. If all these were upgraded to the server equivalent to Vista, then that would mean 10 servers with the same key, and possibly hundreds (if not thousands) across the campus.
Okay, so let us assume none of this duplication creates a false positive. Instead, let us take the example where someone has offered these versions of Windows to the internet as pirated copies. We now hit a new dilemma. There is the potential for massive piracy in this. You cannot simply cut off every version with this key, since you would be cutting off thousands of legitimate copies. You also cannot do some sort of limitation based solely on IP, since students do not live strictly in dorms and since this would enter a new realm of privacy invasion. You see, there is a huge problem with this sort of re-activation issue. You risk hurting many people. Also, for gaming enthusiast who changes components frequently, this could also lead to issues. And what if your MoBo died? Will it be a problem replacing it with another copy of the same board? You should not have to activate this product everytime your system changes. Defeating piracy is one thing, but causing a lot of headache and issues for paying customers is not. In the end, they will only hurt the paying customers, since the hackers will defeat whatever stupid system they come up with anyway.
"Some days you just can't get rid of a bomb."
I agree that if it takes you 3 days to get a server up and running, then your disaster plans suck.
However, consider the following:
- Server crashes due to hardware failure
- Techs follow the existing standard procedure to restore (i.e. replace motherboard)
- Service is restored on time according to SLAs.
- The server continues to happily serve out data and requests.
- Three days pass and suddenly the server is offline *AGAIN* because it wasn't activated and is now refusing requests.
- Spend more time on the phone with Microsoft than it took to replace the motherboard.
Suddenly, that hardware failure had a MUCH larger impact than it had to.
I guess we never learned anything from the mid 80s.
Software copy protection and DRM don't work. You annoy legitimate users who have a corner case (usually enough for them to buy a competitor's product) and the h4x0rz work around it. The few pennies you save are more than made up for with bad publicity.
I've had to call Microsoft about WinXP activation a few times ... and we lease all our machines from HP. The activation code is on a sticker on the machine. There should not be ANY problems with our activation. Particularly with me because we have two other people who do desktop support. And we have just over 100 desktops.
But between key generators and lazy co-workers who use the wrong codes on the wrong machines, I've had to call Microsoft to straighten this out a few times.
And I'm in a small company.
Microsoft's stated plan depends too much (entirely) upon the honesty/skill of my co-workers and the failure of key generators.
No fucking way, dude. Why should I waste MY time (emphasis on the fact that it is MY fucking time) because Microsoft is too lazy/stupid to figure out a better way of doing this?
Novell, way back when, used to link their licenses to specific companies and you could call them and they would tell you every license you had registered with them. If you lost a license disk, they would replace it.
Microsoft refuses to do the same. Even with the improved technology that we have today. They would rather put the burden on ME to:
a. Make sure that nothing does go wrong.
and
b. Call them when something does go wrong.
Eh? What's that? You don't have an exit strategy? My God man, have you been paying no attention at all for the last four years? You've slept through all the warnings? You didn't think through XP Registration and where it was headed? You slept right through WGA? Maybe you should panic. Best get cracking on a plan. The rest of you slow down, take your time BUT GET THE HELL OFF THIS SHIP BECAUSE YOU DON'T WANT TO STILL BE HERE IN FIVE YEARS
You can't see ANYTHING from a car, You've got to get out of the goddamned contraption and walk...Edward Abbey