Re: Windows Update now fails on all clients
From: Neil (anonymous_at_discussions.microsoft.com)
Date: 09/02/04
- Next message: Stevea: "VPN and change of TCPIP Static address"
- Previous message: Neil: "Re: Windows Update now fails on all clients"
- In reply to: Neil: "Re: Windows Update now fails on all clients"
- Next in thread: Kevin Weilbacher: "Re: Windows Update now fails on all clients"
- Reply: Kevin Weilbacher: "Re: Windows Update now fails on all clients"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 2 Sep 2004 03:25:23 -0700
Nope the changing to HTTPS does not work either
Ive looked around and YES this is a BIG problem - Also
called Microsoft and they cant help at this stage either.
Its a bug me thinks - but what a bad time to have it when
XP Sp2 is out !
Also my error code is 0x80072F78
AND - apart from updating to all the latest service pack
I have done nothing to ISA server - all default settings.
Neil
>-----Original Message-----
>Nice to see some good debate on this topic
>
>>From what I can see you should not be able to go Windows
>Update v5 with ISA server 2000 without a fix - check out
>the Windows update newsgroup for the ever growing issue -
>yes others have the similar problem but EVERY one of our
>clients have the issue putting the blame back on WU v5
or
>SBS2000 components.
>I have been happy with SBS 2000 for years now and if WU
v4
>works then v5 should work also.
>Kevin, I has seen to many sites with exactly the same
>problem for it to be anything but a bug.
>I will try the HTTPS and see what happens
>
>Microsoft please publish a fix soon !
>
>Neil
>
>
>>-----Original Message-----
>> Norm -- there are several of us that are running SBS
>with ISA and have
>>implemented WU v5.
>>
>>Simply saying that MS has 'forgotten' us in SBS is
>neither accurate nor
>>complete. In fact, several posts in the Windows Update
>newsgorup indicate
>>that people NOT using SBS are also having problems
>similar to yours.
>>
>>The fact that there is a problem with WU v5 with some
>folks, however, is a
>>true and accurate statement.
>>
>>--
>>Kevin Weilbacher [SBS-MVP]
>>"The days pass by so quickly now, the nights are seldom
>long"
>>
>>
>>
>>"N. Hughes" <quadrantcomputerNOSPAM@hotmail.com> wrote
in
>message
>>news:eep8VaCkEHA.1136@tk2msftngp13.phx.gbl...
>>> Hi Kevin
>>>
>>> Thanks for your suggestions. Re.the IE Proxy, as
>system admins running
>>SBS
>>> for our clients, in the properties page for IE, we
>always check the
>>tick-box
>>> for our IE clients to access HTTP 1.1 via proxy - so
no
>joy there.
>>>
>>> And yes, we have tried re-registering MSXML3.dll as
per
>your suggestion,
>>no
>>> joy there either.
>>>
>>> It seems to us that this really is a "bug" :
Microsoft
>have somehow
>>> "forgotten" about SBS and simply assumed that
corporate
>WAN users will use
>>> SUS (or WUS, or whatever it's called now) to effect
>automatic updates. In
>>> fact, on one of their web pages
(from "troubleshooting
>Windows Update") it
>>> aslmost says as much. And I've logged a call with MS
>Online Support 3 days
>>> ago and not received a work-around.
>>> NOT GOOD ENOUGH MS!!!!
>>>
>>> No Cheers this time!
>>> Norm Hughes
>>>
>>>
>>> .dll "Kevin Weilbacher" <kweilbacMVP@gte.net> wrote
in
>message
>>> news:OMlql0BkEHA.2788@tk2msftngp13.phx.gbl...
>>> > Norm, here is another "fix" that I found as well.
>>> >
>>> > Hi,
>>> >
>>> > If error 0x80244001 occurs when trying to update
from
>windows update
>>site
>>> > it is most likely a most likely an MSXML
installation
>problem.
>>> >
>>> > This problem can be resolved by re registering the
>MSXML3.dll and see if
>>> it
>>> > helps:
>>> >
>>> > 1. Click Start > Run.
>>> >
>>> > 2. In the Run box, type:
>>> > "%windir%\system32\regsvr32.exe %windir%\system32
>\MSXML3.dll"
>>> > (please remove ")
>>> >
>>> > 3. Click OK.
>>> >
>>> > This will reregister the MSXML3.DLL. please let me
>know if this
>>> information
>>> > helps!
>>> >
>>> >
>>> >
>>> > --
>>> > Kevin Weilbacher [SBS-MVP]
>>> > "The days pass by so quickly now, the nights are
>seldom long"
>>> >
>>> >
>>> >
>>> > "N. Hughes" <quadrantcomputerNOSPAM@hotmail.com>
>wrote in message
>>> > news:uGTS1t6jEHA.2788@tk2msftngp13.phx.gbl...
>>> > > Kevin
>>> > >
>>> > > I have 3 SBS sites of 5 users or less and they
all
>have the same
>>issue,
>>> as
>>> > > does our own office, the specific error number is
>0x80244021.
>>> > > Searching other newsgroups indicates the problem
is
>increasing, it
>>only
>>> > > affects XP machines with ISA; it has something to
>do with
>>> authentication.
>>> > I
>>> > > have posted to MS Online tech Support but no
>answers yet.
>>> > >
>>> > > Norm Hughes
>>> > >
>>> > > "Kevin Weilbacher [SBS-MVP]"
<kweilbacMVP@gte.net>
>wrote in message
>>> > > news:%23gRdAn1jEHA.384@TK2MSFTNGP10.phx.gbl...
>>> > > > Also, try this --- edit the WU5 URL that's
>displayed for you and
>>> change
>>> > > the
>>> > > > http://v5... to https://v5...
>>> > > >
>>> > > > That has helped someone in the past.
>>> > > > --
>>> > > > Kevin Weilbacher [SBS-MVP]
>>> > > > "The days pass by so quickly now, the nights
are
>seldom long"
>>> > > >
>>> > > >
>>> > > > "Kevin Weilbacher [SBS-MVP]"
><kweilbacMVP@gte.net> wrote in message
>>> > > > news:%23J1d5j1jEHA.1040@TK2MSFTNGP10.phx.gbl...
>>> > > > > What error message are you getting? WU5 is
>working fine for me. Do
>>> you
>>> > > > > have ISA enabled on your server?
>>> > > > >
>>> > > > > I doubt that this is a "major problem
>spreading" as there have
>>been
>>> > > > > virtually no such issues reported here in
this
>NG.
>>> > > > >
>>> > > > > As an alternative, have you checked out
either
>Microsoft's SUS or
>>> > > > > Shavlik's HfNetCHKPr? Both are solutions that
>allow you to manage
>>> and
>>> > > > > update your workstations from a central spot.
>Shavlik's solution
>>> also
>>> > > > > allows you to scan and update for Office
>patches, and handles
>>> > > > > SQL/Exchange/and ISA patches (which WU does
>not).
>>> > > > >
>>> > > > > Furthermore both solutions are free (well,
>Shavlik's is free if
>>you
>>> do
>>> > > not
>>> > > > > have more than 10 workstations on your local
>network).
>>> > > > >
>>> > > > > Let's see what else we can find out!
>>> > > > >
>>> > > > > --
>>> > > > > Kevin Weilbacher [SBS-MVP]
>>> > > > > "The days pass by so quickly now, the nights
>are seldom long"
>>> > > > >
>>> > > > >
>>> > > > > "Neil" <anonymous@discussions.microsoft.com>
>wrote in message
>>> > > > > news:079e01c48f3c$b49a5740$a401280a@phx.gbl...
>>> > > > >> Since updating through windows update to WU
5 -
> now all
>>> > > > >> my clients cannot do a Windows Update. We
use
>SBS2000 and
>>> > > > >> its been perfect for WU - now nothing - from
>what I can
>>> > > > >> see this is a major problem spreading
>>> > > > >>
>>> > > > >> Anyone with any ideas as Microsoft was
>unhelpful
>>> > > > >>
>>> > > > >> Neil
>>> > > > >
>>> > > > >
>>> > > >
>>> > > >
>>> > >
>>> > >
>>> >
>>> >
>>>
>>>
>>
>>
>>.
>>
>.
>
- Next message: Stevea: "VPN and change of TCPIP Static address"
- Previous message: Neil: "Re: Windows Update now fails on all clients"
- In reply to: Neil: "Re: Windows Update now fails on all clients"
- Next in thread: Kevin Weilbacher: "Re: Windows Update now fails on all clients"
- Reply: Kevin Weilbacher: "Re: Windows Update now fails on all clients"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|