From: "Glenn Meadows" 

Nope, not a requirement of the machine to be in the domain.  In the GPEDIT
of the Windows Update Server address, I just plug in the IP address of the
server.  There are several ways to configure the machines.  You can do them
with a policy from the server, or you can apply the policy locally.  On
Win2KPro, and XPPro, just run GPEDIT.MSC, and add the Windows Update policy
to the machine, and configure.

On an XP-Home machine, manually enter the registry values, the instructions
are included with the documentation.  Takes about 5 minutes per machine to
configure.

When you then open the Windows Update control panel, ALL of the options to
change anything are grayed out, so no local user changes can be entered.
This does NOT prevent anymachine from going to windowsupdate.com to check
for updates manually, just changes the way the Auto Update functions.

--

Glenn M.
"Geo"  wrote in message
news:420f781f$1{at}w3.nls.net...
>I don't think SUS will work on XP home since it can't be a domain member
> (isn't that a requirement?).
>
> Geo.
>
> "Frank Haber"  wrote in message
> news:420f60fa{at}w3.nls.net...
>> Glenn,
>>
>> >Do you have a Windows 2000 server in your office?
>>
>> (Amplifying the confessional above)
>>
>> Would you believe an unused copy of 2000 Server?  Blush.  Think a PIII
> would
>> be good enough for this sort of stuff?  How do you think SUS would run
>> on,
>> say, a 733 with 512MB?  Ever tried SUS on a random and motley,
> ever-changing
>> collection of machines that just float through and disappear?  How about
> the
>> no-gpedit situation on XP Home machines (60% of what I see).
>>
>> The time, the time.
>>
>
>

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