Browse Prior Art Database

Method & System to Apply Software Patches conveniently without Impacting or Requiring User Reboot Disclosure Number: IPCOM000197765D
Original Publication Date: 2010-Jul-21
Included in the Prior Art Database: 2010-Jul-21
Document File: 1 page(s) / 25K

Publishing Venue


Related People

Howard Locker: INVENTOR [+3]


Today IT organizations struggle with the ability to apply critical software patches to users systems and balance the needs of the corporation and impacting the user. While the ability to get a patch down to a user’s PC has been dramatically improved over the last few years, when a patch requires the user to shut down and re-boot their system, users often refuse of days if not weeks and months. This leaves the organization exposed to attacks the patch is urgently being distributed to stop. Users often are busy and postpone re-boot for a more convenient time, but then often forget or just can’t seem to find an appropriate time. This creates tremendous conflict between the needs of the organization and the user’s perception of the IT organization being heavy handed. This article will describe a method of balancing the needs of IT with the needs of end users.

This text was extracted from a Microsoft Word document.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 88% of the total text.

Method & System to Apply Software Patches conveniently without Impacting or Requiring User Reboot

Today there is no way to force a user’s system to shut down and re-boot at a time that is convenient to the user or that does not take over the user’s system, shutting it down at times where data is lost or work in interfered with.  Wake On


created a way to wake up systems but shut down on


cannot be used without fear of user disruption and no other methods exist today.

This method and system creates extensions to a PC’s S3 and S4 state or suspend and hibernate.  It also links in the ability to schedule an event in the body of a software distribution package or via the broadcast of a packet similar to the “magic packet” of Wake On


.  This “reboot packet” sets the system to reboot upon occurrence of a header in the software distribution package or via a broadcast of the reboot packet directly.

Here’s one way it works or an example:

An IT organization develops an emergency patch that needs to be applied quickly to protect their company from a denial of services attack.  Since the patch needs to be applied as quickly as possible the IT organization embeds the reboot packet into the software distribution package.   The package is sent out to all users or systems and users are notified to apply the packet immediately.  Unfortunately, like is always the case over 20% of users do not apply the packet, but this time the reboot packet sets the systems S3...