Full Disclosure mailing list archives
RE: Automating patch deployment
From: "Bassett, Mark" <mbassett () omaha com>
Date: Mon, 18 Aug 2003 09:53:33 -0500
The client that has to be running is the windows auto update client. It doesn't require admin privileges unless you want it to. You can configure SUS in a lot of different ways. Unfortunately it won't run on NT4 :( <snip from http://www.microsoft.com/windows2000/windowsupdate/sus/susfaq.asp > Q. What clients does SUS support? A. Your client computers must be running Windows 2000 Professional with Service Pack 2 (SP2) or later, Windows XP Professional, or Windows 2000 Server with SP2 or later in order to run Automatic Updates. Note: Windows NT 4.0 is not supported. </snip> -----Original Message----- From: George Peek [mailto:GKPeek () AllstateTicketing com] Sent: Sunday, August 17, 2003 5:04 PM To: Bassett, Mark Subject: RE: [Full-disclosure] Automating patch deployment Cool, thanks.. Requires the client to be running? Most of our clients use NT, deploy .msi using logins script, does it require admin prv? -----Original Message----- From: Bassett, Mark [mailto:mbassett () omaha com] Sent: Wednesday, August 06, 2003 7:21 AM To: full-disclosure () lists netsys com Subject: RE: [Full-disclosure] Automating patch deployment The good thing about SUS is that you can set it up to not push out the packages until you approve them. The SUS box downloads all the critical updates and then they sit in queue until you tell them it's ok to push them out. I think that's the best way to handle the situation. Sure it creates a little admin work, but I think the advantage is clear. -----Original Message----- From: gregh [mailto:chows () ozemail com au] Sent: Wednesday, August 06, 2003 8:04 AM To: full-disclosure () lists netsys com Subject: Re: [Full-disclosure] Automating patch deployment
----- Original Message ----- From: Johnson, Mark To: George Peek ; full-disclosure () lists netsys com Sent: Wednesday, August 06, 2003 7:12 AM Subject: RE: [Full-disclosure] Automating patch deployment
Look at Microsoft Article 328010 for information on setting up Windows 2000, XP and 2003 to automatically update Microsoft's patches. I know this isn't the full solution, but maybe a start.
Just my 2 cents again - I distinctly remember March 28 2002 XP and 2000 update stuffing many systems around the world. I also remember the 811493 patch slowdown and eventual reissue by MS. Automation of update patches? Not on your Nellie! I would have a machine download patches and try installs on it before I felt comfortable about passing them on to others. *LOOK MA! NO HTML!* _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.netsys.com/full-disclosure-charter.html ************************************************************ Omaha World-Herald Company computer systems are for business use only. This e-mail was scanned by MailSweeper ************************************************************ _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.netsys.com/full-disclosure-charter.html _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.netsys.com/full-disclosure-charter.html
Current thread:
- RE: Automating patch deployment, (continued)
- RE: Automating patch deployment LaRose, Dallas (Aug 05)
- RE: Automating patch deployment Bassett, Mark (Aug 06)
- RE: Automating patch deployment Schmehl, Paul L (Aug 06)
- RE: Automating patch deployment David Vincent (Aug 06)
- RE: Automating patch deployment Altheide, Cory B. (Aug 06)
- RE: Automating patch deployment Krogh, Jefferson (Aug 12)
- RE: Automating patch deployment George Peek (Aug 17)
- RE: Automating patch deployment Jørgen Hoffmeister (Aug 21)
- RE: Automating patch deployment George Peek (Aug 17)
- RE: Automating patch deployment Richard Stevens (Aug 18)
- RE: Automating patch deployment Bassett, Mark (Aug 18)