posted by
oldbloke at 10:08am on 31/08/2007
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
Date: Sat, 25 Aug 2007 19:58:22 -0400 (EDT)
From: "David Lesher" <xxxxxx@xxxxx.xxx>
Subject: MS WGA Servers down; XP & Vista installs marked "counterfeit"
The Windows Genuine Disadvantage servers all went down.
Result: All attempted OS installations were labeled as counterfeit.
THAT means you get 'limp home' mode for the box..
<http://forums.microsoft.com/genuine/showpost.aspx?postid=2053834&siteid=25>
<http://www.boingboing.net/2007/08/25/microsoft_wga_server.html>
The recovery procedure, once you know their server is again working,
involves deleting some special files, and revisiting the WGA server.
{Sigh; haven't we had this conversation before?}
RISKS:
Creating an artificial single-point-of-failure.
Not making that single point robust/redundant enough to defend again all
enemies, foreign and domestic [i.e. outsiders vs the more likely "we have
met the enemy, and he is us..." errors.]
Not having good recovery procedure when the Can't Happen Does
Happen... [Can your mother find her data.dat file?]
I wonder if the server farm has both geographic and network diversity.
(There was a Jan 2001 failure of all Microsoft nameservice; then, they were
in one place, on one segment.)
I also worry about what happens if somehow, sometime, the MS database gets
trashed, and it decides ALL copies of XP/VISTA/Win2009/whatever are
pirated. So when every machine does its obligatory check-in, and gets
castrated...
From: "David Lesher" <xxxxxx@xxxxx.xxx>
Subject: MS WGA Servers down; XP & Vista installs marked "counterfeit"
The Windows Genuine Disadvantage servers all went down.
Result: All attempted OS installations were labeled as counterfeit.
THAT means you get 'limp home' mode for the box..
<http://forums.microsoft.com/genuine/showpost.aspx?postid=2053834&siteid=25>
<http://www.boingboing.net/2007/08/25/microsoft_wga_server.html>
The recovery procedure, once you know their server is again working,
involves deleting some special files, and revisiting the WGA server.
{Sigh; haven't we had this conversation before?}
RISKS:
Creating an artificial single-point-of-failure.
Not making that single point robust/redundant enough to defend again all
enemies, foreign and domestic [i.e. outsiders vs the more likely "we have
met the enemy, and he is us..." errors.]
Not having good recovery procedure when the Can't Happen Does
Happen... [Can your mother find her data.dat file?]
I wonder if the server farm has both geographic and network diversity.
(There was a Jan 2001 failure of all Microsoft nameservice; then, they were
in one place, on one segment.)
I also worry about what happens if somehow, sometime, the MS database gets
trashed, and it decides ALL copies of XP/VISTA/Win2009/whatever are
pirated. So when every machine does its obligatory check-in, and gets
castrated...
There are no comments on this entry. (Reply.)