Comments on: Patch Deployment in 3 Easy Steps

By: Ben Vincenti

Ben Vincenti — Tue, 11 Jan 2011 11:40:28 +0000

Hi everybody,

Thank you for your comments. Indeed patch deployment is never an easy task however, luckily, GFI LANguard simplifies this process. Furthermore, with the introduction of version 9.6, it is now possible to patch a plethora of software platforms. You can visit http://kbase.gfi.com/showarticle.asp?id=KBID003469 for more information.

Kind regards,

Ben Vincenti

By: philip c.

philip c. — Wed, 05 Jan 2011 03:42:09 +0000

Although there has been a lot of discussion on the implementation of either automated or non-automated patch management, I agree that the deployment of the actual patches themselves still have a lot of bearing on making sure a company’s workflow isn’t disrupted in the process. The steps and recommendations highlighted by this article are definitely good foundations to effectively rolling out a patch, whether it’s for an internal or external system.

By: Jeremy Stenton

Jeremy Stenton — Fri, 10 Dec 2010 07:14:22 +0000

I’ve actually had to work in scenarios where a network audit had turned up unpatched servers of less than 1% (more like .5 actually). And having been pressed for time on a particular project, had to run with the system in hopes that the majority of servers would make up for the unpatched ones. Unfortunately, we had the whole system crashing down on us in a matter of minutes and found ourselves worse of than when we first started.

By: taylor

taylor — Fri, 10 Dec 2010 07:07:05 +0000

Patch deployment is never actually simple, but it’s great how this article pretty much distills the process down to its elements. A lot of time and effort goes into making sure that patch deployment goes as quickly and easily as possible, and when it doesn’t, that’s immediately countless hours down the drain with countless hour more to go. Not necessarily a situation that any company wants to experience first hand.