Re: Vista Upgrade Advisor bombs

Hi Fellows,

I seem to have those same kind of errors using Vista Ultimate / x64 MSDN media
via a non-microsoft proxy that requires auth (error 802441b).

Jack.

"JPenrose" wrote:

> Hey Rich, thanks for the reply.
>
> Are you saying that WU fails with Vista RTM clients behing ISA 2004? I had
> issues when setting up WSUS way back when that caused me to create some
> custom access filters on the ISA box and WSUS worked there after. Perhaps
> Vista WU utilizes different URLs.
>
> I didn't see anything specific in the ISA monitor but a couple hits in the
> list eluded to anon access so I just presumed that was the issue and hoofed
> it to the NG to post.
>
> I find it stageringly hard to beleive that MS engineers couldn't reproduce
> the issue using WVUA and an authenticating proxy? Maybe ther's more to it if
> other features fail as well. This product releases to business customers in a
> few days; the fact that basic functions like WU and WVUA etc fail is going to
> have some impact.
>
> Keep this alive here if you can. You obviously have access to some key areas.
>
> Thanks again,
> John
>
> "Rich Milburn" wrote:
>
> > Hello JPenrose,
> >
> > I believe that is exactly the problem We have ISA 2004 server requiring
> > authentication as well. I've been reporting this issue (because it only
> > gets worse, hold on) since at least RC1. Did you see it trying to access
> > anonymously?
> >
> > So that's just the upgrade advisor. IME Windows Update also fails, and there
> > are various other things that fail too, such as the icon showing if you're
> > connected to the Internet.
> >
> > Apparently Microsoft couldn't reproduce the issue somehow. I should use
> > one of my support incidents to escalate this... anyway... I'll see if I can
> > pass your issue on through the private beta newsgroups...
> >
> > Rich Milburn
> > MVP - Directory Services
> >
> > > So I scarf down my MSDN copy of the Vista RTM iso image and cut a disk
> > > for testing. I see this helpful looking option on the splash screen to
> > > scan my PC for readiness. Seems like a good idea so I launch it and it
> > > promptly fails telling me that it could not contact the 'web service'
> > > bla bla bla your internet connection was lost bla bla bla try again
> > > later bla bla uninstall etc.
> > >
> > > Ok, so I'm not shocked since I'm on a corporate LAN behind ISA 2004
> > > but I am surprised that this code that took so long to produce and is
> > > so much anticipated by the community fails on such a rudimentary
> > > IMPORTANT function like checking for pre install compat? I'm sorry but
> > > WTF; that above anything is the first step in applying an update (SP,
> > > OS, software; whatever) so for it to fail on a corporate LAN doesn't
> > > instill a heap of confidence. I ran the same routine from the same
> > > MSDN disk on an identical machine on my home network and it sailed
> > > through to completion. I have to conclude that my proxy is getting in
> > > the way.
> > >
> > > I then configured ISA to log activity from my PC and observed via RDP
> > > the results of launching WVUA. Big fat nothing to report there.
> > >
> > > So, PSS (anyone), what's the solution? WFW isn't getting in the way, I
> > > don't have any other security software running on this box outside of
> > > Defender and NAV corp 9 so I can't see what could be preventing the
> > > connection other than the service trying to connect anonymously to the
> > > 'web service' which ISA won't allow.
> > >
> > > TIA
> > > JPenrose MCSE/A
> >
> >
> >