RE: [ActiveDir] Microsoft Patch

[Eric Fleischman]

The definition of the word superior is probably in the mind of the reader. The most important thing you need to decide for patch management is what your goals are. Do you want accounting? Push abilities? Just getting the patch out there as clients request it? What sorts of controls? What sorts of packages (just a few MS products, all products by many vendors, etc.)? There are more questions than one might think.   If you come up with a list of desires it’s easier to evaluate solutions. IE you’re taking a “ready-fire-aim” approach without first deciding what you want in the solution.   That said, currently in the MSFT world you have SUS 1.0 (2.0 around the corner) and SMS 2003. Good solutions, but there are certainly others that are very good as well. It’s really up to you and what your goals are. Then, pick the product that works best for you.   My line to customers is pick what works best for you. If SUS or SMS is that product, great! If not, great! Just pick what does the job for you. As long as you get patches out there I’m fine with any solution. J   ~Eric     From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rimmerman, Russ Sent: Monday, March 15, 2004 3:47 PM To: '[EMAIL PROTECTED]' Subject: RE: [ActiveDir] Microsoft Patch   Yes, we're using Patchlink www.patchlink.com and it's working quite well.   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cariglia, Daniel Sent: Monday, March 15, 2004 3:43 PM To: [EMAIL PROTECTED] Subject: [ActiveDir] Microsoft Patch I am in the process of looking at alternatives to distribute/manage Microsoft patches.  We have SUS running in a lab setup and it seems alright.  My question is are there superior products out there that someone has used and can recommend that work well with AD?  Running AD with an empty root and 2 child domains where the users reside, users are either Windows 2000 Pro or XP Pro.  Any suggestions would be appreciated.             Thank You,     Dan   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This e-mail is confidential, may contain proprietary information of the Cooper Cameron Corporation and its operating Divisions and may be confidential or privileged. This e-mail should be read, copied, disseminated and/or used only by the addressee. If you have received this message in error please delete it, together with any attachments, from your system. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~