Slashdot Mirror
Corporations Suffer Microsoft Activation Bug
Uncle Bob writes "Trustworthy Computing, eat your heart out! As of the 2003-04-14 update, people are reporting that Office 2000 SR1a is now asking to be "registered" again. And again, and again. Very little information has been posted on the traditional news sites (the only link I could find was The Register. Note - The Register's story is not quite accurate, but the registration bug is real. Our company with approx 80,000 PCs has been hit...."
If you have a Help Desk application that tracks hours related to working on this mess, you (and other customers) should ask for a reduction in your support costs to compensate for all the non-value added work your internal staff is having to do. Ideally, this sort of clause should be built into a purchase up front, and it would have to start with large customers, but MS (and other vendors) need to face some serious financial consequences for blunders like this...
Stop by my site where I write about ERP systems & more
Every time I hear that software price is only a small consideration in TCO, I wonder where licensing administration goes in that TCO. Be sure to file this one in there too.
I've also never seen acquisition costs for free software, "well I've got a meeting with the vendor this afternoon. we're gonna haggle over the price of 20 seats."
t
My mom used to work with a division of IBM and when I heard how large just their NC buildings were, I thought the same thing - wow, now I see where MS makes its money.
Then I wondered about switching to Linux and how much that would *save* them.
I mentioned that to my mom and she said that they discussed it many times, but they ran figures on how much money they spent/lost just switching from one *program* to another (training and help desk support), let alone to a whole new operating system.
She was in the department that hired temps and they used software that scanned in resumes and then fed them to a database and allowed searches on it and such. At the time, I worked for a company that had a superior product to what they had, it was cheaper, and had a better UI. She said in order for them to switch (after they looked into it), due mostly to training, it would add on over $2million in costs to the overall price - and their current system "worked" so they were going to change. And that was just her group which was "only" a few thousand people.
You could argue that were the software easy enough to work with, you wouldn't need to train the users... but if you think that way, you give the users WAY too much credit - something one learns quickly in the software industry - if you are writing software for end users, remember that your end users are fat dumber than you can ever estimate.
Essentially the only way you could switch (easily and cost effectively) over an office is if it were very small, and if the users were already relatively tech savvy.
for the most part, any savings in OS and program cost is lost in productivity lost during the switch and the increased support for people that are essentially all newbies at that point.
There are some odd things afoot now, in the Villa Straylight.
That our company has switched over to OpenOffice exclusively. It's been a year since we switched over from Microsoft Office, and there have only had a handful of documents that have had MS Office/Open Office incompatibilities.
Plus, OpenOffice is totally free. Retraining was a non-issue. We told the employees when we switched over that they were welcome to use MS Office, but they would have to buy the software themselves and keep the licenses handy. There were no complaints about switching over after that.
So we can sit back smugly as all of our branches are unaffected and read stories like this without blanching :) If you haven't checked out OpenOffice, I highly recommend that you do.
We hang the petty thieves, but appoint the great ones to public office. - Aesop
Yeah, it's called "synthetic time".
For those of you who don't know how NDS works (and probably don't care), I'll spill some of my useless knowledge on you.
So, let's say you set the clock back on a Novell server. Most NDS transactions are timestamped, to allow auditing, and other such nice things. The problem is, let's say you set your time back now - it's 4/17/03, 12:40pm, and you set it back to 4/17/00, 12:40pm.
NDS isn't exactly *stupid* - it has transactions leading up to 4/17/03, and time very rarely goes backwards like that. So the server is forced to issue "synthetic time", so every transaction takes place a very short ammount of time after 4/17/03, 12:40:0000, then 12:40:00.01, 12:40:00.02, and so on. This will *never fix itself*...
Well, until 4/17/03, 12:40:xx.xx pm, when things catch up. Then everything will be fine.
Never fear! You can fix this. After you roll your clocks back, just run dsrepair with the -a switch (which allows you to do the stupid things - but for the really stupid things, you can use the switches -xk2 -xk3), and pick advanced options -> Global Schema Operations. Log in, and select "Declare a new Epoch."
Then you're just really telling the Novell server, yes, strange as it may seem, time *did* go backwards. And it deals with it.
I really don't know why I bothered to write that.