Brian,
Thanks for the response - as you probably realized, I posted in your earlier
thread about having similar problems as you did with Proxy 2.0. I don't
believe that I can effectively use WSUS - I am still running Small Business
Server 4.5 and looking at the minimum requirements for WSUS, I don't believe
that I meet them.
What is interesting - the only machine that I am still having problems with
is the machine that did not initiate a reinstall of Windows Update V.6 after
performing the procedure that I outlined in my first post. Remember - all 5
of my machines were upgraded to Windows Update V.6 and all 5 originally
refused to connect to Update with a 0x80072F78 error. After performing the
procedure in my first post, all but 1 of my machines reinstalled the Windows
Update V.6 and were able to repeatedly connect.
This makes me believe that something was modified within Windows Update V.6
from the time that I first installed it to the point where it was
reinstalled? It just doesn't make sense to me at all! Nothing within my
proxy settings or workstation Internet Explorer settings were changed on ANY
of the workstations.
Any insight that you might have regarding a forced uninstall of Windows
Update V.6 on my 1 remaining workstation is appreciated. Thanks.
"Brian Steele" wrote:
> Nice to hear you got your PCs updating again :-).
>
> Here, we can't install the winproxy client on some PCs (e.g. the domain
> controllers). We use MSP 2.0's web proxy feature to provide Internet
> access. I've found that the only solution to the "80072F78" problem for
> those systems was to add the "Everyone" group to the access control list for
> the "WWW" protocol (see Web Proxy..Properties..Permissions).
>
> Of course this isn't an ideal solution, as now MSP2.0 anonymizes every
> outgoing connection (every connection in the web proxy log is listed as
> "anonymous").
>
> I've implemented WSUS here for our 160+ node LAN. Very nice package. Can
> tell at a glance which machines are updated, which machines require updates,
> and what updates are required. As I only used the web-based Windows Update
> procedure for testing purposes, I can work my way around it, after grumbling
> at Microsoft for implementing a Windows Update upgrade that doesn't work as
> well as the older version.
>
> Have a look at WSUS. It's useful, even if you only have 5 workstations to
> look after :-).
>
> Regards,
> Brian Steele
>
> BTW - stopping the wuauserv service before trying to delete the software
> distribution folders should've taken care of the file access problem.
>
>
>
> "npittsburgh01" <> wrote in message
> news:14708465-8FBB-41E1-B74B-...
> > During the course of updating my five workstations, I found that one is
> > giving me problems with subsequent connections to the Update Site. Four
> > of
> > the five machines initiated a reinstall the latest version of the Windows
> > Update software (V.6) after deleting the Software Distribution folder
> > discussed below. All of those machines will allow follow-up connections
> > to
> > the Windows Update site (even after a full shutdown and reboot).
> >
> > The Update Site did not want to reinstall the Windows Update software on
> > the
> > one problem machine. I was able to connect to the Update Site one time
> > but
> > not subsequent times. It appears that the success of my other four
> > machines
> > was dependent upon reinstallation of the Windows Update software. I guess
> > I
> > now have to figure out how to force reinstallation for that one machine
> > and I
> > will be good to go. Any guidance or thoughts on that subject are
> > appreciated!
> >
> > "npittsburgh01" wrote:
> >
> >> After all of the posts that I read saying that the new version of Windows
> >> Update (v.6) cannot authenticate through MS Proxy 2.0 and that the only
> >> viable solution is through the use of WSUS, all I can say is
> >> ........"yeah...right!"
> >>
> >> I have 5 Windows 2000 Professional Workstations accessing the internet
> >> through MS Proxy 2.0 on a server that utilizes Panda Corporate Antivirus.
> >> After upgrade of the workstations to V.6 of the Windows Update caused all
> >> of
> >> the subsequent connections to the Update site to fail with an Error Code
> >> 0x80072F78. I read all of the posts and KBs regarding Proxy problems,
> >> firewall problems, antivirus problems, etc. Here is what I did to
> >> correct
> >> the problem.
> >>
> >> First, I deleted all of the files and folders in the C:\WinNT\Software
> >> Distribution Folder. In order to do this, I had to reboot the machine in
> >> Safe Mode as deletion of these files in normal operating mode caused a
> >> sharing violation - files in use error.
> >>
> >> Second, after deleting the files and folders, I restarted the machine as
> >> I
> >> normally would and connected to Windows Update. I was then able to scan
> >> the
> >> system and Update forced me to re-download the latest version of Windows
> >> Update - which I did. I then had to restart the machine as directed.
> >>
> >> After the reinstallation of the new Windows Update, I noticed something
> >> peculiar - my Winsock Proxy Client no longer had a valid server name
> >> associated with it. I then re-installed the Winsock Proxy Client
> >> software
> >> and restarted the machine as directed.
> >>
> >> I then connected to the Windows Update site and was successfully able to
> >> scan, view, download and install updates. After installing all of the
> >> critical updates, I again executed Windows Update to verify that I was
> >> able
> >> to reconnect to the site. It worked just fine! In fact, in lieu of
> >> Express
> >> scan, I selected Custom scan just to verify that I could find and
> >> download a
> >> driver update.
> >>
> >> I hope this helps someone else fighting the 0x80072F78 error!
>
>
>
|
Similar Threads
Linear Mode
