Yes, AFAIK you need to log the machine into a domain, have it accept a
group policy that sets the update repo path, do the updates, and then
disjoin it from the domain and pray that the GP doesn't stick around
after that.
Thane Sherrington wrote:
At 09:48 AM 20/02/2008, Greg Sevart wrote:
Thane,
I'm actually kinda surprised you don't just run an internal WSUS
server for
in-house patching. I've always preferred it over third party tools.
Sure, it
still requires multiple reboots, but at least pulling updates is nearly
instantaneous. After a couple botched systems caused by Autopatcher, I
just
don't trust those tools to get the dependencies right.
It doesn't help much "in the field" so to speak, but could certainly
assist
in-house.
I understood that in order to use a WSUS server, I'd have to log the
machine to be updated into my server. Then I'd have to convince the
machine to go back to normal Windows Updates when the customer takes the
computer home. I've done some very basic reading on this, and it
doesn't appear anyone has WSUS working in a repair shop setting. If you
have some pointers, I'd be interested in giving it a try.
T
