Re: Windows Update v5 issues and workaround

From: Gary (Gary_at_discussions.microsoft.com)
Date: 01/19/05 

Date: Wed, 19 Jan 2005 10:27:02 -0800

In my case, protocol rules for Interent access doesn't require authetication,
everyone can access the Internet to any site. Creating anonymous protocol
rule won't help me. What else can I do, other than SecureNet client. Thanks.

Gary

"Phillip Windell" wrote:

> "Tom Bokman" <TomBokman@discussions.microsoft.com> wrote in message
> news:B50C6993-1A92-4DAB-AB08-AD8CF09D9499@microsoft.com...
> > Yes, I follow everything up to step 7 but then it says:
> >
> > "NOTE: if your existing protocol rules require authentication (user or
> > group-limited), you'll have to create an anonymous
> > protocol rule for HTTP and HTTPS as follows:
>
> You obviously only see what you want to see and I am wasting my time with
> you. YES! It is an anonymous rules for HTTP and HTTPS. BUT!! It is used in
> conjunction with a Destination Set,....so THAT!....it only applies to the
> Windows Update sites. Why in the world!!! would they have you create a
> Destination Set and spend half the article explainly how to create such a
> Destination Set if you weren't going to use it for something..??
>
> I'm done with ya...
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
>

Relevant Pages

  • Re: Windows Update v5 issues and workaround
    ... In my case, protocol rules for Interent access doesn't require authetication, ... Creating anonymous protocol ... It is an anonymous rules for HTTP and HTTPS. ...
    (microsoft.public.isa.configuration)
  • Re: Windows Update v5 issues and workaround
    ... In my case, protocol rules for Interent access doesn't require authetication, ... Creating anonymous protocol ... It is an anonymous rules for HTTP and HTTPS. ...
    (microsoft.public.isa)