The workstations in the domain behind the ISA server are unable to get
Windows Automatic Updates when scheduled at 3am. The error on the
workstation is:

Event Type: Warning
Event Source: Automatic Updates
Event Category: Download
Event ID: 16
Date: 5/21/2004
Time: 8:14:31 AM
User: N/A
Computer: TBDN30
Description:
Unable to connect: Windows is unable to connect to the Automatic Updates
service and therefore cannot download and install updates according to
the set schedule. Windows will continue to try to establish a
connection.


I have checked and applied (if applicable) the following: Q241783 ,
Q312955 , Q328010 , Q824208 , Q830750

I have made sure WPAD is in DNS. I have opened 443 on the ISA server
using a packet filter. Workstations fail regardless if they are using
the WSP Firewall Client or not. All use the IP address of the ISA
server as the proxy server, port 8080.

I've posted here before with no replies, so I hope this is enough
information to start.

BTW, from the workstation just going to www.windowsupdate.com and doing
an update works just fine.

Re: Client Win Auto Upd not working by Dave

Dave
Mon May 24 11:12:55 CDT 2004

If I'm understanding you correctly, WU works when run manually at the
workstation, but not when run automatically with the user logged off? In
that case (and this is just a wild shot), maybe ISA is blocking outbound
access because there's no user logged in? You could easily test this by
leaving someone logged in overnight - if that user's workstation is updated,
you'll know that's what's happening.

What I would suggest for this is to install SUS. It's little work to
install and configure if you follow the documentation provided, it only
downloads updates once per network instead of once per workstation, and IMO
it's more foolproof and trouble-free than AU.

http://www.microsoft.com/windowsserversystem/sus/default.mspx


"Dvord Direwood" <dvord@Hotmail.com> wrote in message
news:uNoEPZ1PEHA.640@TK2MSFTNGP12.phx.gbl...
> The workstations in the domain behind the ISA server are unable to get
> Windows Automatic Updates when scheduled at 3am. The error on the
> workstation is:
>
> Event Type: Warning
> Event Source: Automatic Updates
> Event Category: Download
> Event ID: 16
> Date: 5/21/2004
> Time: 8:14:31 AM
> User: N/A
> Computer: TBDN30
> Description:
> Unable to connect: Windows is unable to connect to the Automatic Updates
> service and therefore cannot download and install updates according to
> the set schedule. Windows will continue to try to establish a
> connection.
>
>
> I have checked and applied (if applicable) the following: Q241783 ,
> Q312955 , Q328010 , Q824208 , Q830750
>
> I have made sure WPAD is in DNS. I have opened 443 on the ISA server
> using a packet filter. Workstations fail regardless if they are using
> the WSP Firewall Client or not. All use the IP address of the ISA
> server as the proxy server, port 8080.
>
> I've posted here before with no replies, so I hope this is enough
> information to start.
>
> BTW, from the workstation just going to www.windowsupdate.com and doing
> an update works just fine.



Re: Client Win Auto Upd not working by Dvord

Dvord
Mon May 24 17:11:33 CDT 2004

I've been apprehensive about doing just that due to the setup, but
you're right, set it up, and forget about it for the most part (I hope).

Actually the workstations fail to update even if a user is logged in
(but the console is locked, would that make a difference??).

Thanks Dave!

Dave Nickason [SBS MVP] wrote:

> If I'm understanding you correctly, WU works when run manually at the
> workstation, but not when run automatically with the user logged off? In
> that case (and this is just a wild shot), maybe ISA is blocking outbound
> access because there's no user logged in? You could easily test this by
> leaving someone logged in overnight - if that user's workstation is updated,
> you'll know that's what's happening.
>
> What I would suggest for this is to install SUS. It's little work to
> install and configure if you follow the documentation provided, it only
> downloads updates once per network instead of once per workstation, and IMO
> it's more foolproof and trouble-free than AU.
>
> http://www.microsoft.com/windowsserversystem/sus/default.mspx
>
>
> "Dvord Direwood" <dvord@Hotmail.com> wrote in message
> news:uNoEPZ1PEHA.640@TK2MSFTNGP12.phx.gbl...
> > The workstations in the domain behind the ISA server are unable to get
> > Windows Automatic Updates when scheduled at 3am. The error on the
> > workstation is:
> >
> > Event Type: Warning
> > Event Source: Automatic Updates
> > Event Category: Download
> > Event ID: 16
> > Date: 5/21/2004
> > Time: 8:14:31 AM
> > User: N/A
> > Computer: TBDN30
> > Description:
> > Unable to connect: Windows is unable to connect to the Automatic Updates
> > service and therefore cannot download and install updates according to
> > the set schedule. Windows will continue to try to establish a
> > connection.
> >
> >
> > I have checked and applied (if applicable) the following: Q241783 ,
> > Q312955 , Q328010 , Q824208 , Q830750
> >
> > I have made sure WPAD is in DNS. I have opened 443 on the ISA server
> > using a packet filter. Workstations fail regardless if they are using
> > the WSP Firewall Client or not. All use the IP address of the ISA
> > server as the proxy server, port 8080.
> >
> > I've posted here before with no replies, so I hope this is enough
> > information to start.
> >
> > BTW, from the workstation just going to www.windowsupdate.com and doing
> > an update works just fine.
>
>


Re: Client Win Auto Upd not working by Dave

Dave
Tue May 25 11:48:47 CDT 2004

Hitting "lock computer" shouldn't matter - the user is still logged in. The
users have admin rights?


"Dvord Direwood" <dvord@Hotmail.com> wrote in message
news:umbR1vdQEHA.396@TK2MSFTNGP12.phx.gbl...
> I've been apprehensive about doing just that due to the setup, but
> you're right, set it up, and forget about it for the most part (I hope).
>
> Actually the workstations fail to update even if a user is logged in
> (but the console is locked, would that make a difference??).
>
> Thanks Dave!
>
> Dave Nickason [SBS MVP] wrote:
>
>> If I'm understanding you correctly, WU works when run manually at the
>> workstation, but not when run automatically with the user logged off? In
>> that case (and this is just a wild shot), maybe ISA is blocking outbound
>> access because there's no user logged in? You could easily test this by
>> leaving someone logged in overnight - if that user's workstation is
>> updated,
>> you'll know that's what's happening.
>>
>> What I would suggest for this is to install SUS. It's little work to
>> install and configure if you follow the documentation provided, it only
>> downloads updates once per network instead of once per workstation, and
>> IMO
>> it's more foolproof and trouble-free than AU.
>>
>> http://www.microsoft.com/windowsserversystem/sus/default.mspx
>>
>>
>> "Dvord Direwood" <dvord@Hotmail.com> wrote in message
>> news:uNoEPZ1PEHA.640@TK2MSFTNGP12.phx.gbl...
>> > The workstations in the domain behind the ISA server are unable to get
>> > Windows Automatic Updates when scheduled at 3am. The error on the
>> > workstation is:
>> >
>> > Event Type: Warning
>> > Event Source: Automatic Updates
>> > Event Category: Download
>> > Event ID: 16
>> > Date: 5/21/2004
>> > Time: 8:14:31 AM
>> > User: N/A
>> > Computer: TBDN30
>> > Description:
>> > Unable to connect: Windows is unable to connect to the Automatic
>> > Updates
>> > service and therefore cannot download and install updates according to
>> > the set schedule. Windows will continue to try to establish a
>> > connection.
>> >
>> >
>> > I have checked and applied (if applicable) the following: Q241783 ,
>> > Q312955 , Q328010 , Q824208 , Q830750
>> >
>> > I have made sure WPAD is in DNS. I have opened 443 on the ISA server
>> > using a packet filter. Workstations fail regardless if they are using
>> > the WSP Firewall Client or not. All use the IP address of the ISA
>> > server as the proxy server, port 8080.
>> >
>> > I've posted here before with no replies, so I hope this is enough
>> > information to start.
>> >
>> > BTW, from the workstation just going to www.windowsupdate.com and doing
>> > an update works just fine.
>>
>>
>



Re: Client Win Auto Upd not working by Dvord

Dvord
Tue May 25 13:04:53 CDT 2004

Yes, Domain Users is in the Administrators group on every PC.

Dave Nickason [SBS MVP] wrote:

> Hitting "lock computer" shouldn't matter - the user is still logged in. The
> users have admin rights?
>
>
> "Dvord Direwood" <dvord@Hotmail.com> wrote in message
> news:umbR1vdQEHA.396@TK2MSFTNGP12.phx.gbl...
> > I've been apprehensive about doing just that due to the setup, but
> > you're right, set it up, and forget about it for the most part (I hope).
> >
> > Actually the workstations fail to update even if a user is logged in
> > (but the console is locked, would that make a difference??).
> >
> > Thanks Dave!
> >
> > Dave Nickason [SBS MVP] wrote:
> >
> >> If I'm understanding you correctly, WU works when run manually at the
> >> workstation, but not when run automatically with the user logged off? In
> >> that case (and this is just a wild shot), maybe ISA is blocking outbound
> >> access because there's no user logged in? You could easily test this by
> >> leaving someone logged in overnight - if that user's workstation is
> >> updated,
> >> you'll know that's what's happening.
> >>
> >> What I would suggest for this is to install SUS. It's little work to
> >> install and configure if you follow the documentation provided, it only
> >> downloads updates once per network instead of once per workstation, and
> >> IMO
> >> it's more foolproof and trouble-free than AU.
> >>
> >> http://www.microsoft.com/windowsserversystem/sus/default.mspx
> >>
> >>
> >> "Dvord Direwood" <dvord@Hotmail.com> wrote in message
> >> news:uNoEPZ1PEHA.640@TK2MSFTNGP12.phx.gbl...
> >> > The workstations in the domain behind the ISA server are unable to get
> >> > Windows Automatic Updates when scheduled at 3am. The error on the
> >> > workstation is:
> >> >
> >> > Event Type: Warning
> >> > Event Source: Automatic Updates
> >> > Event Category: Download
> >> > Event ID: 16
> >> > Date: 5/21/2004
> >> > Time: 8:14:31 AM
> >> > User: N/A
> >> > Computer: TBDN30
> >> > Description:
> >> > Unable to connect: Windows is unable to connect to the Automatic
> >> > Updates
> >> > service and therefore cannot download and install updates according to
> >> > the set schedule. Windows will continue to try to establish a
> >> > connection.
> >> >
> >> >
> >> > I have checked and applied (if applicable) the following: Q241783 ,
> >> > Q312955 , Q328010 , Q824208 , Q830750
> >> >
> >> > I have made sure WPAD is in DNS. I have opened 443 on the ISA server
> >> > using a packet filter. Workstations fail regardless if they are using
> >> > the WSP Firewall Client or not. All use the IP address of the ISA
> >> > server as the proxy server, port 8080.
> >> >
> >> > I've posted here before with no replies, so I hope this is enough
> >> > information to start.
> >> >
> >> > BTW, from the workstation just going to www.windowsupdate.com and doing
> >> > an update works just fine.
> >>
> >>
> >
>
>