From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_01A9_01C5BAFA.8D187DB0
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   I don't know.  Seems like a reasonable option to offer.

Rich

  "Rich Gauszka"  wrote in message =
news:432b6f48$1{at}w3.nls.net...
  Thanks - I can understand the first boot after install. What I meant =
was will the network incoming connections still be blocked if a WU check =
shows there are critical updates that need to be applied well after the =
installation ( weeks, months ) ?  I suspect not but was unsure about the =
technet statement below=20

  For example,=20
  Windows Vista's firewall blocks all inbound traffic until a computer =
has the=20
  latest security updates installed=20



  "Rich"  wrote in message news:432b64a8{at}w3.nls.net...
       I didn't read the page to which you refer but the description you =
give matches the Windows Server 2003 SP1 behavior at installation.  At =
first boot after install the network is blocking incoming connections = and
when the admin logs on he is presented with UI to check for updates.

    Rich

      "Rich Gauszka"  wrote in message =
news:432b27c1$1{at}w3.nls.net...
      Does this mean that Vista's firewall  will stop all incoming =
Internet=20
      activity if there are security updates available?  Or am I reading =
too much=20
      into the statement below?

      http://www.microsoft.com/technet/windowsvista/evaluate/overvw.mspx


      The personal firewall built into Windows Vista builds on the =
functionality=20
      that is included with Microsoft Windows XP Service Pack 2. For =
example,=20
      Windows Vista's firewall blocks all inbound traffic until a =
computer has the=20
      latest security updates installed=20


------=_NextPart_000_01A9_01C5BAFA.8D187DB0
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   I don't
know.  Seems =
like a=20
reasonable option to offer.
 
Rich
 

  "Rich Gauszka" <gauszka{at}hotmail.com>">mailto:gauszka{at}hotmail.com">gauszka{at}hotmail.com>
wrote =
in message=20
  news:432b6f48$1{at}w3.nls.net...
  Thanks - I can understand the first boot after =
install. What=20
  I meant was will the network incoming connections still be blocked if =
a=20
  WU check shows there are critical updates that need to be applied =
well=20
  after the installation ( weeks, months ) ?  I suspect not but was =
unsure=20
  about the technet statement below 
   
  For example, Windows Vista's firewall blocks all inbound =
traffic=20
  until a computer has the latest security updates installed =

   
   
  "Rich" <{at}> wrote in message news:432b64a8{at}w3.nls.net...
  

       I
didn't read the page =
to which=20
    you refer but the description you give matches the Windows Server =
2003 SP1=20
    behavior at installation.  At first boot after install the =
network is=20
    blocking incoming connections and when the admin logs on he is =
presented=20
    with UI to check for updates.
     
    Rich
     
    
      "Rich Gauszka" <gauszka{at}hotmail.com>">mailto:gauszka{at}hotmail.com">gauszka{at}hotmail.com>
=
wrote in=20
      message news:432b27c1$1{at}w3.nls.net...Does=20
      this mean that Vista's firewall  will stop all incoming =
Internet=20
      activity if there are security updates available?  Or am =
I=20
      reading too much into the statement
below?http://www.microsoft.com/technet/windowsvista/evaluate/overvw.msp=
x">http://www.microsoft.com/technet/windowsvista/evaluate/overvw.mspx;=
The=20
      personal firewall built into Windows Vista builds on the =
functionality=20
      that is included with Microsoft Windows XP Service Pack 2. For =

      example, Windows Vista's firewall blocks all inbound traffic =
until a=20
      computer has the latest security updates installed=20
 


------=_NextPart_000_01A9_01C5BAFA.8D187DB0--

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