Patent Application Number: 2009200584
This discussion forum is available to allow the community of reviewers to collaborate and discuss this patent application.

Discussion that is posted on this page will not be forwarded to IP Australia. If you wish to make comment on a prior art reference and wish that comment to be considered by the patent examiner, please do so by clicking on the relevant prior art reference.

Here are some tips to facilitate discussion.
  • Flagging a post as an 'action item' signals that further research is required.
  • Flagging SPAM and ABUSE helps to manage discussion
  • Placing double brackets around a reference to a claim or prior art will create a hyperlink to the original, for example: [[claim 1]] and [[prior art 2]].
Discussion (3)
  Facilitator's Comment     Action Item
  Show without Noise
2
Mark Webbink (over 2 years ago)
Regarding Claim 1 - Every element of this claim appears to exist in Red Hat's Red Hat Network - Satellite. That system consists of a satellite server that receives provisioning (installation and updating information) from a central maintenance system and then automatically pushes the installation and update information to target machines based on their profiles. The satellite servers are stationed at customer sites to manage all of the machines on the network.
1
Mik Clarke (over 2 years ago)
If I understand this right, there is one company that is distributing software updates to a number of different customers. Each customer has their own mix of servers, clients and products. The invention provides a way for the company to package software updates so that they can be downloaded by the customers and then fed into a 3rd party software distribution server running within the customers enterprise (along with the necessary configuration for that software server) so that the updates are then pushed out to the machines that the customer has chosen to apply the updates to.

The saving/advantage/novelty would seem to be in the packaging of the instructions for the 3rd party software distribution server, avoid a scenario where each customer had to update their 3rd party software distributor with the correct distribution rules for the package.

Anyone agree/disagree?
Basil Newnham (over 2 years ago)
Hi Mik,

From what I understand the 3rd party element would be similar to the functionality already built into Microsofts Group Policy Objects (as apposed to WSUS) with the deployment of .msi packages, this allows you to deploy and update software packages based on rules. It would also seem to cover the server packages developed in the 3rd party Standard Operating Environment markets where patch management and installation is centralised and automated. In the opensource realm I would have to agree with Mark on this, it seem to be very similar to the deployment systems used by Linux distributions such as Red Hat, Debian and Ubuntu (I believe that Ubuntu also allows central control similar to WSUS but I will need to research to confirm).

Comments?