Basically, it is like a version of Windows Update that runs on your network. Your SUS server will sync with Windows Update at pre-selected intervals, and then your clients will be able to download the updates from the SUS server and install them on a schedule that you choose. You can also configure the patch installations to take place at specified times, and your users won't need admin rights for it to run. In fact, your users won't have to interact with it at all.
I have thought about that. Our network consists of about 50 clients and 2 servers. The servers are DC,s, run DNS and WINS. These are not very powerful servers. Will running SUS be a big load on one of these boxes or is a separate server required?
SUS Generally dosen't take that much overhead. Microsoft's claim is that a dedicated SUS box will suport upto 15,000 users. We have a dedicated 600mhz box for SUS for about 600 clients.
I have my SUS on a DC/DNS server. The box is nothing special; dual P3-866, 256MB RAM, and it runs just fine. Network bandwidth would probably be more of an issue than processing. It is determined what updates are needed (ie OS, SP level) and I believe it is the client side service that does performs this check. SUS requires IIS, but you can disable pretty much all of the services except for www.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.