Yeah they haven't deployed any users to the new symantec protection on that
machine so it wasn't an issue. They'll have to reinstall using a different
virtual directory.
He told me he just had a new computer/user download all the updates before I
fixed it this morning. So I don't know. At this point, everything's
working. And I'm all smiles. Thanks again.
"Lawrence Garvin [MVP]" wrote:
> "rvvisse" <> wrote in message
> news:2122A0FB-5DE1-4D40-94F6-...
> > OK GOT IT!
> >
> > Here was the problem. The administrator for the WSUS server had recently
> > installed Symantec Endpoint protection that OVERWROTE the content folder.
> > The content folder did exist after all, but it was pointing to the wrong
> > files.
>
> That'll do it.
>
> This issue with co-existence of SEP and WSUS has been known about for some
> time.
>
> (And my apologies for not thinking of SEP -- as many times as it's bitten
> people it ought to be higher up on my list.)
>
>
> > Once we realized the mistake, they changed the Content folder to point to
> > the correct path (D:\WSUS\WSUSupdates) and everything magically worked
> > again.
>
> Of course, now, the SEP is broken. ;-)
>
>
> > As to why the other 200 clients they have were working... my guess is that
> > they were pointing to the selfupdate folder as opposed to the content
> > folder.
>
> I suspect there's more to it than that. Either those client simply did not
> have need to download any files thus had not shown any errors, or they
> really weren't working and the WSUS Admin was oblivious.
>
> --
> Lawrence Garvin, M.S., MCITP:EA, MCDBA
> Principal/CTO, Onsite Technology Solutions, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2009)
>
> My Blog: http://onsitechsolutions.spaces.live.com
> Microsoft WSUS Website: http://www.microsoft.com/wsus
> My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>
Similar Threads
Linear Mode
