decoration decoration
Stories

GROKLAW
When you want to know more...
decoration
For layout only
Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines
ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

Click here to send an email to the editor of this weblog.


You won't find me on Facebook


Donate

Donate Paypal


No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.


What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments


Sponsors

Hosting:
hosted by ibiblio

On servers donated to ibiblio by AMD.

Webmaster
Microsoft stock shoots up investor have short memories | 55 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
Microsoft stock shoots up investor have short memories
Authored by: Anonymous on Tuesday, May 07 2013 @ 08:07 AM EDT
If my impressions from the melt down of MS Azure service earlier this year
and MS explanations then I think investors are crazy.
MS explanation of what went wrong may well be true but it shows a number
of serious problems with MS management.
A simple comparision with some thing very ordinary is useful
MS knew that the security certificates were going to expire in about 2 weeks
so they prepared new ones and placed them on a computer with for
propagation but with a low priority and they didn't get propagated so the
whole system went down.
Say your car registration papers arrive in the mail and you fill them in and
write the cheque and put both in an envelope to post - no hurry it isn't due
for a couple of weeks. You put the envelope on the desk thinking I'll do that
later. You get an invitation to a wedding and the kid brings an important
note from school etc and before you know it your rego renewal envelope is
underneath a pile of stuff and you don't realise it until you get pulled over
and get a ticket and told to leave your car right there till you get everything

paid etc.
Any checks MS made were about as effective as looking at the cheque butts
to see if you wrote out the check and didn't care about posting the
envelope.
What this tells me :-
1 the computer system was under resourced in some way because there
was no time that the load reduced to a level that allowed the propagation
to take place,
2 The individual (or team) responsible for the certificates did not know that
the system was under resourced, (if anyone at all knew)
3 No one checked to see if the certifcates had propagated and
4 there was no management processes in place to ensure proper checks
were made.
Why would any one want to use MS Azure service if that is how it is
managed? And that is how it is (maybe was) managed.
I have no idea how hard it would be to check that the certifcates had
propagated but I do know that it would be easy to check whether the
browser choice was still in Windows before sending off the certificate to the
EU that yes it is still there when it isn't.
MS problem is that the management is incompetent!!
Chris B

[ Reply to This | Parent | # ]

Microsoft stock shoots up investor have short memories
Authored by: Anonymous on Tuesday, May 07 2013 @ 08:08 AM EDT
If my impressions from the melt down of MS Azure service earlier this year
and MS explanations then I think invetors are craz.
MS explanation of what went wrong may well be true but it shows a number
of serious problems with MS management.
A simple comparision with some thing very ordinary is useful
MS knew that the security certificates were going to expire in about 2 weeks
so they prepared new ones and placed them on a computer with for
propagation but with a low priority and they didn't get propagated so the
whole system went down.
Say your car registration papers arrive in the mail and you fill them in and
write the cheque and put both in an envelope to post - no hurry it isn't due
for a couple of weeks. You put the envelope on the desk thinking I'll do that
later. You get an invitation to a wedding and the kid brings an important
note from school etc and before you know it your rego renewal envelope is
underneath a pile of stuff and you don't realise it until you get pulled over
and get a ticket and told to leave your car right there till you get everything

paid etc.
Any checks MS made were about as effective as looking at the cheque butts
to see if you wrote out the check and didn't care about posting the
envelope.
What this tells me :-
1 the computer system was under resourced in some way because there
was no time that the load reduced to a level that allowed the propagation
to take place,
2 The individual (or team) responsible for the certificates did not know that
the system was under resourced, (if anyone at all knew)
3 No one checked to see if the certifcates had propagated and
4 there was no management processes in place to ensure proper checks
were made.
Why would any one want to use MS Azure service if that is how it is
managed? And that is how it is (maybe was) managed.
I have no idea how hard it would be to check that the certifcates had
propagated but I do know that it would be easy to check whether the
browser choice was still in Windows before sending off the certificate to the
EU that yes it is still there when it isn't.
MS problem is that the management is incompetent!!
Chris B

[ Reply to This | Parent | # ]

Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )