From: "Geo" 

And if SUS updated itself to not accept the key that the old patches were
signed with? I would imagine this capability exists in case a signing key
gets compromised.

Geo.

"Glenn Meadows"  wrote in message
news:421174f5{at}w3.nls.net...
> Move the patches out of the \content directory (or copy them).  They're
all
> downloaded as individual patches with their number, just like you manually
> download.
>
> --
>
> Glenn M.
> "Geo"  wrote in message
news:42116b61{at}w3.nls.net...
> > doesn't matter, they still have delete capabilities on the machine and
> > they
> > could still modify the SUS package so even if the files are there it
won't
> > allow installation anymore. It's the auto nature that I want away from,
I
> > don't want any changes, nothing loaded, nothing updated, nothing
modified
> > by
> > the vendor without my OK first.
> >
> > Geo.
> >
> > "Glenn Meadows"  wrote in message
> > news:421150b3$1{at}w3.nls.net...
> >> Change the permissions on the files to read/execute only, don't allow
> >> deletes in that folder.
> >>
> >
> >
> >
>
>

--- BBBS/NT v4.01 Flag-5