From: /m 

On Sat, 3 Jun 2006 12:47:01 -0400, "Rich Gauszka"
 wrote:

>
>"/m"  wrote in message
>news:sa6382lc6tq7ed3kc6ro26kq5nrhd64lr1{at}4ax.com...
>> On Sat, 3 Jun 2006 09:20:33 -0400, "Rich Gauszka"

>> wrote:
>>
>>>
>>>"Robert Comer"  wrote in message
>>>news:447e3f93$1{at}w3.nls.net...
>>>>> I may load it when they have a non "pre
release" version .
>>>>> Personally
>>>>> I don't think they should use  "pre release"
software for a "critical"
>>>>> update. I do wonder what they are communicating to MS.
>>>>
>>>> My WAG would be that it's checking for new pirate key
signatures, but I
>>>> have no idea what it really does.  I really, really, really, really,
>>>> hate
>>>> WGA...
>>>>
>>>> --
>>>> Bob Comer
>>>>
>>>
>>>
>>>
>>>     * Windows product key
>>>     * PC manufacturer
>>>     * Operating System version
>>>     * PID/SID
>>>     * BIOS information (make, version, date)
>>>     * BIOS MD5 Checksum
>>>     * User locale (language setting for displaying Windows)
>>>     * System locale (language version of the operating system)
>>>     * Office product key (if validating Office)
>>>     * Hard drive serial number
>>>
>>>others are reporting that WGA appears to connect with that info on every
>>>startup. 
>>>
>>>http://forums.microsoft.com/Genuine/ShowPost.aspx?PostID=448083&SiteID=25
>>>
>>
>>
>> I previously noted here that the firewalls on my PC and notebooks have
>> been blocking boot-up connection attempts to something like
>> stats.update.microsoft.com (my original message on this topic has the
>> exact URL).
>>
>> /m
>
>Heaven help you if your firewall blocks the WGA outbound validation when it
>installs ( Isn't the purpose of a firewall to block any unknown outgoing
>connection? )

When I'm in Microsoft Update I am usually running with a lower level of
security (i.e., I'm letting evil Active-X run), plus my firewall rules are
looser.

It sounds like I will have to tighten things up a bit.



>
>http://forums.microsoft.com/Genuine/ShowPost.aspx?PostID=445799&SiteID=25
>I talked with my lead developer on this issue. Looking at the time-stamps of
>the install log (WGAError.log) you gave us (Thanks so much by the way!) -
>We're under the impression that the Firewall could have blocked outbound
>network connections during install and validation (it validates when it
>installs). Thus, causing an error and throwing the initial
"non-genuine"
>message.
>


Never saw that particular message.

 /m

--- BBBS/NT v4.01 Flag-5