Browse Prior Art Database

Method of automated prioritization and sequencing of management actions on distributed devices

IP.com Disclosure Number: IPCOM000225032D
Publication Date: 2013-Jan-21
Document File: 3 page(s) / 26K

Publishing Venue

The IP.com Prior Art Database

Abstract

A method of automated prioritization and sequencing of management actions on distributed devices is disclosed.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 01 of 3

Method of automated prioritization and sequencing of management actions on distributed devices

Disclosed is a method of automated prioritization and sequencing of management actions on distributed devices.

In large distributed or virtualized environments, when an action has to be performed on targets (such as Patch Management (Mgmt)), system administrators usually perform the actions on some test systems and then initiate the action on target groups. The method by which these target groups are selected are based on experiential 'tribal' knowledge such as, targeting human resource (HR) desktops first, then moving to finance group desktops, etc. The problem with this kind of approach is:

The knowledge is held in someone's experience and is not cataloged in any manner.


This knowledge does not take into consideration any changes that may have

happened in the environment. For example, if a new print server has been moved into the HR work group, then an unintended patch may be applied to it merely because it was in the group and had a targeted OS, even though the patch was not intended for print servers. In a virtualized environment, this situation may become even more complex requiring knowledge about a particular image before targeting it for any action.


When something like patching is done - a system administrator may not wish to

apply patches to a lot of machines at once. Even if testing had been done, it's likely that an ordering is desired. As an example, a system administrator would probably apply patches to a secretary's laptop in less important shipping department before applying them to the CIO's laptop, though they are in different work groups.

The following method is utilized to provide this support:

Based on a company internal knowledge, a set of conditions can be set to compare the target machine against and assign it a numbering score and a priority.


Based on the numbering score and priority, a set of groups of the target machines is

created. These groups are then ordered in a list.


Then actions (such as patching etc) to be performed on the target machine, are

initiated on the first group in the list.


Within a group, the set of machines can also be ordered in a sequence. An action

on a machine starts only when a specific signal is received from one or more of the following:

Another machine


1.

Managing serve


2.

Approval from a system administrator.


3.

This approach provides control of the order in which actions are applied and allows the system administrator to stop an action in case any trouble or issues arises.

ALGORITHM:

1


Page 02 of 3

STEP 1. Property Assignment

Assign properties for each of the Target machines.

The properties can be set by multiple ways:

a) T...