ISA Clients, 2004 FWC -Setup failed while updating Windows Socket 2 Provider

1. 2004 FWC -Setup failed while updating Windows Socket 2 Provide

2. Setup failed Window socket 2 provider - ISA Clients

3. Setup access to windows update and other software update sites

I'd liketo set my ISA server up with the foloowing configuration;
1. All PCs have access to certain software update sites such as windows
update etc.
2. User in Active directory grup "full internet access" can browse the web
unrestricted.
3. Other users can only access those websites specified in the destination
set.

I plan to do this by:-
1. Creating a destination set for all "universally allowed sites"
2. Create a protocol rule for full web access to all
3. Create a site and content rule applied to "full internet access" group
for all destinations.
4. Create a site and content rule applied to "any user" for just the
destination set "universally allowed sites".

I assume that therefore if someone not in the full access group tries to
access a website not in the allowed sites, it will get blocked as there is
no rule explicitly allowing it??

I would be grateful if someone can tell me if this is likely to work as
unfortunately these rules will affect a lot of users. Because the site is
remote I cannnot easily test this either.

Anyway TIA for any help,

-H

4. Windows Update fails to successfully install updates after ISA Ser - ISA Configuration

5. Windows Server 2008 - Windows Update Failing - Error 8024401F

Perhaps our colleagues in the ISA-specific newsgroup might be able to lend a 
hand here, Harry?  As such, I'm forwarding this thread to 
microsoft.public.isa via crosspost.

Harry Johnston [MVP] wrote:
> Greg Wilkerson wrote:
>
>> I am not certain, but I do believe it's WSUS (do I have a choice with
>> W2k8?).
>
> As discussed in m.p.w.s.update_services, Greg isn't using WSUS.
>
>>  I am running an ISA Server.  If this is using a special port, I can
>> configure that.  I've been installing and uninstalling this on the 
>> machine
>> for the last week or so (reformatting between each install).  I kind of
>> doubt ISA server is the case, but anything is possible.  I just don't
>> recall this being an issue before.
>
> PA Bear, are you familiar with ISA?  I'm not sure what sort of
> troubleshooting steps would be appropriate - perhaps trying a different IP
> number, or a different computer name in case the issue is related to the 
> computer's AD
> account?
>   Harry.
>
>
>
>> "PA Bear [MS MVP]" wrote:
>>>> 8024401F = WU_E_PT_HTTP_STATUS_SERVER_ERROR
>>>> Http status 502 - error response received from gateway
>>>>
>>>> Could be a proxy or (ISA) firewall problem, Greg, or could be temporary
>>>> problems on MS's end.
>>>>
>>>> Any other errors in WindowsUpdate.log (e.g., 0x8024000C; 801901f4)?
>>>>
>>>> Are you updating via WSUS?
>>>>
>>>>
>>>> Greg Wilkerson wrote:
>>>>>> I'm at a total loss here.  I simply installed Windows 2008 Server
>>>>>> Standard and clicked the link to update windows.  Just that simple.
>>>>>>
>>>>>> None of the other machines on my network have any troubles.
>>>>>>
>>>>>> What am I missing? 

6. Working RPC over HTTP / ISA 2004 setup fails, IIS quits, forces re - Manage MS Exchange Server

7. Setup Failed While creating the services configuration (ISA Server 2004 on Server 2003)

8. ISA 2004 setup fails on brand new SBS 2003 Premium installatio - Windows Small Business Server(SBS)