RE: SUS Server Hardware

["BOWSER, DAVID" <[EMAIL PROTECTED]>]

I have had the exact scenario and hardware you described (minus the
WINS) running for almost a year. 

The biggest issue I have is convincing people to reboot, shutdown, or
even logoff their PCs so that changes which require reboot or login will
take effect. I have resorted to using HFNETCHKPRO to scan and PSTools to
reboot the rogue machines. I ran into several within the last week that
had not been rebooted since last months patch release.

David Bowser 
 
Network Engineer 
SIB Mortgage


-----Original Message-----
From: Evan Mann [mailto:[EMAIL PROTECTED] 
Sent: Thursday, April 29, 2004 4:18 PM
To: Patch Management Mailing List
Subject: SUS Server Hardware


In deploying SUS, I'd like to maximize my bandwidth and deploy a local
SUS server in each of my remote offices, so those local machines get
their patches from that server.  In many of these offices, this machine
is a Windows 2003 DC running WINS, DNS, DHCP and file storage.  They are
typically 1ghz machines or faster with 512megs of RAM.  My newer
machines are 2.4ghz P4's.  There is plenty of HDD space.

Would it not be adviseable to run an SUS server on these machines, or
does it not matter?  If it's not adviseable, then I'd probably not
deploy a local SUS server and make them update over the WAN (not my
preffered method).

For my main office, I have some spare machines, older Dell PE's in the
700mhz P3 range, 1 gig of RAM.  Is this level of machine adequate to
handle 100-150 clients?



---
To unsubscribe send a blank email to
[EMAIL PROTECTED]

---
To unsubscribe send a blank email to [EMAIL PROTECTED]