We use sus here and are very happy, but we only use it for clients. After MS release the patches we deploy it manually to a handfull of clients (distictly different roles) and ask them to try out all their apps.
After a couple of days if no strange behavioir has been noticed or adverse reports in the press we approve the patches for the rest of the clients. For servers, we try out on less crucial server first, and then after a couple of days manually update others. If I get a suitable box become available I will build another sus server for servers. ThenI will test on a few and deploy to the rest. SUS becomes WUS (SUS v2.0) is expected later this year... "New Features In addition to a new name, WUS sports a wide range of desirable new features. Like earlier SUS versions, WUS provides businesses with a centralized patch-management infrastructure, which lets administrators approve then roll out patches to desktops and servers. WUS adds new content download types-including patches for Microsoft Office, SQL Server, and Exchange Server-to the previously supported Windows updates and service packs. WUS includes improved targeting capabilities that let administrators take advantage of organizational units (OUs) in Active Directory (AD) environments or *****manually created groups in workgroups*** to roll out patches to the most crucial systems first. The new service also includes bandwidth-management capabilities that let you control patch delivery during peak business hours so that you can ensure your networks won't be overloaded during crucial periods" http://www.winnetmag.com/Windows/Article/ArticleID/41969/41969.html Matt Joyce Children's Cancer Institute Australia http://www.ccia.org.au > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Hilda De Nigris > Sent: Tuesday, 29 June 2004 3:44 AM > To: Exchange Discussions > Subject: Automatic Updates to Exchange 2003 IIS Server > > > We are currently running Exchange Server 2003 on Windows 2003 > server. Has anyone considered the use of a fully automated > patching product like the Windows Update service, Shavlik or similar? > > The concerns are obvious. Like all of you out there, we are > against pushing untested updates in a production environment. > However with the substantial increase of virus deployments, > Trojan drops and hacker threats we are wondering if any sort > of prolonged exposure to these threats should not be winning > the war in precedence. It seems these OS's are fairly secure > but that's just a matter of time. > > > > _________________________________________________________________ > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > Web Interface: > http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&t ext_mode=&lang=english To unsubscribe send a blank email to %%email.unsub%% Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english To unsubscribe send a blank email to [EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with.
