Software Update Services: Difference between revisions
SUS Documentation |
No edit summary |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
'''We are no longer using SUS, we've switched to using the newer [[Setup Windows Server Update Services|Windows Software Update Services]]. This is old information.''' | |||
== Local SUS Server == | == Local SUS Server == | ||
Our local SUS server is currently hosted on '''Lancer''' (because SUS requires IIS) and directly mirrors all the updates available for Windows 2003 and Windows XP. The SUS server can be administered through [http://lancer.iat.sfu.ca/susadmin/ susadmin]. | Our local SUS server is currently hosted on '''Lancer''' (because SUS requires IIS) and directly mirrors all the updates available for Windows 2003 and Windows XP. The SUS server can be administered through [http://lancer.iat.sfu.ca/susadmin/ susadmin]. | ||
== Configure SUS | == Configure SUS On a Client Computer == | ||
SUS can be configured on any Windows 2000 SP3+ or Windows XP SP1+ by adding some registry information pointing automatic updates to our local SUS server. | SUS can be configured on any Windows 2000 SP3+ or Windows XP SP1+ by adding some registry information pointing automatic updates to our local SUS server. | ||
| Line 14: | Line 17: | ||
[[Media:SUSupdateRemove.reg]] | [[Media:SUSupdateRemove.reg]] | ||
== Useful SUS | == Monthly Maintenance == | ||
SUS has no option to auto allow new updates to be accepted and given to clients, therefore each month (after Microsoft releases new updates) a Research Administrator must log into the SUS server on Lancer and manually approve each of the new security updates one at a time. | |||
== Useful SUS Links == | |||
http://www.susserver.com/FAQs/ | http://www.susserver.com/FAQs/ | ||
Latest revision as of 17:24, 25 April 2007
We are no longer using SUS, we've switched to using the newer Windows Software Update Services. This is old information.
Local SUS Server
Our local SUS server is currently hosted on Lancer (because SUS requires IIS) and directly mirrors all the updates available for Windows 2003 and Windows XP. The SUS server can be administered through susadmin.
Configure SUS On a Client Computer
SUS can be configured on any Windows 2000 SP3+ or Windows XP SP1+ by adding some registry information pointing automatic updates to our local SUS server. Note: In System Properties, the automatic update options will be grayed out once SUS is configured.
Registry file to set a computer to use our SUS mirror: Media:SUSupdate.reg
Registry file to remove SUS from a computer: Media:SUSupdateRemove.reg
Monthly Maintenance
SUS has no option to auto allow new updates to be accepted and given to clients, therefore each month (after Microsoft releases new updates) a Research Administrator must log into the SUS server on Lancer and manually approve each of the new security updates one at a time.
Useful SUS Links
http://www.susserver.com/FAQs/
http://forums.susserver.com/index.php
Semi-useful Microsoft Documentation: Media:SUS_Deployguide_sp1.doc