Client machines are using Windows Update but I'd rather have them all
automated to use WSUS...I have WSBA 2.0 on the server and would like to set
it up for WSUS...is that the right "terminology"? I gave the title because I
saw several hundred other posts about it in the forum. This is the first time
I'm having this problem here.
since it applies to all the clients and NOT the server (got it to completely
update with no problems at all) then it's obviously a server setting. I still
suspect the ISA settings are not properly done. I also suspect that I can
skip the ISA setting if I get WSBA/WSUS setup properly. Is that correct? (As
you can tell, I know just enough to be dangerous. It's the draw back of being
the super user in a company too small to afford a full-time IT person.) Sure
appreciate the help!!!
Jay
"PA Bear [MS MVP]" wrote:
> We need to know if the (client) machines in question update via Windows
> Update or WSUS. Jay.
>
> You give this thread the subject "Error 80072EFD...yet again." Have you had
> such problems before and did you get that error then?
>
> You may receive an..."Error 0x80072EFD"...error message when you try to use
> the Windows Update Web site or the Microsoft Update Web site:
> http://support.microsoft.com/kb/836941
> --
> ~PA Bear
>
>
>
> Jay Hill wrote:
> > Performed %windir%\WindowsUpdate.log on client and got "The process cannot
> > access the file because it is being used by another process." What now?
> >
> > J
> > "PA Bear [MS MVP]" wrote:
> >
> >> Are these machines updating via WSUS?
> >>
> >> Microsoft Security Advisory (954960): Microsoft Windows Server Update
> >> Services (WSUS) Blocked from Deploying Security Updates:
> >> http://www.microsoft.com/technet/sec...ry/954960.mspx
> >> --
> >> ~Robear Dyer (PA Bear)
> >> MS MVP-IE, Mail, Security, Windows Desktop Experience - since 2002
> >> AumHa VSOP & Admin http://aumha.net
> >> DTS-L http://dts-l.net/
> >>
> >>
> >> Jay Hill wrote:
> >>> Tried all instructions in all posts, articles, help, etc. No Go. Have 25
> >>> clients that used to be able to auto-update without problems. Just
> >>> noticed
> >>> the latest update in the network is 2/18/08. We are running XPSP2 on
> >>> clients
> >>> with our IP traffic through Windows Server 2000 with ISA 2000. Have
> >>> checked
> >>> and configured all sites in Trusted Sites on clients and in ISA
> >>> Management
> >>>>
> >>> Access Policy | Site and Content Rules | Windows Update AND | Access
> >>> Policy
> >>>> Protocol Rules | Windows Update AND | Policy Elements | Destination
> >>>> Sets
> >>>>
> >>> Windows Update. I even tried disabling all of these to allow "ALL". No
> >>> go.
> >>> Turned Real Time Virus Scan off on the test client and the IP Traffic
> >>> Server. No go. What am I missing? Any ideas? By the way, this all
> >>> started
> >>> when a particular client's IE could no longer identify/use a personal
> >>> digital certificate required to access one of our sites required to
> >>> process
> >>> a critical function. Thanks for any help!!!!!
>
>