From: "Glenn Meadows" 

Yes it will work on those as well.

In the SUS install instructions, are the registry entries to for doing the
config manually on each machine, which I've done on the XPHome machines we
have here as well.

Random and motley setup?  No, not really.  I would think (though not
attempted or tried) that on a laptop that travels, and is back in every so
often could still be handled.  How?  The way one of the policy settings
controls that.  If a machine has missed "checking in" on the
pre-configured timetable, it will attempt when it's next turned on (machine
off over night).  There is a setting, that determines the time delay for
that to happen.  I would think that would also be the case if the SUS
server was not available (machine is not on the local lan at the time it
checks), and the next time it's brought in, and finds the server, it would
start updating.

--

Glenn M.
"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