Object-based computer system management

• US 9,143,360 B2
• Filed: 01/05/2011
• Issued: 09/22/2015
• Est. Priority Date: 02/16/2006
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Copeland, Bruce W., James, David C., Song, Donald Y., Ingalls, Dustin M., Sutherland, Jeffrey A., Phillips, Jeffry B., Calabig, Joseph S., Iqbal, Khuzaima, Healy, Michael J., Narayanan, Rajagopalan Badri, Pan, Zhengkai Kenneth
• Primary Examiner(s): Sough, H S
• Assistant Examiner(s): JORDAN, KIMBERLY L
• Application Number:
  US12/985,260
• Publication Number:
  US 20110099247A1
• Time in Patent Office: 1,721 Days
• US Class Current: 1/1
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: H04L 12/66 Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A method, system, and architecture for managing computer systems is provided. A management system employs management objects (MOs) to provide administrators the ability to intuitively express the administrative intent in an information technology (IT) environment, and to act out the administrative intent based on the information gathered by the management system. Managed elements of an IT environment, such as, by way of example, hardware components, software applications, software updates, software distribution policies, configurations, settings, etc., may be expressed as MOs. Actions, such as, by way of example, detect, install/apply, remove, remediate, enumerate, etc., may be associated with the MOs. The management system manages the computer systems by deploying the appropriate MOs and their associated actions onto the computer systems, and performing the actions on the computer systems.

Claims

1. A method, performed by a computer system having a memory, a processor, and a managed object instances cache, the method comprising:

receiving an indication of a desired state for the computer system, the desired state specifying at least one property for each managed object of a plurality of managed objects that are to be available for the computer system to be in the desired state, wherein each managed object is associated with a unique identifier to uniquely distinguish the managed object in a managed environment;

determining that the managed object instances cache does not include an indication of an instance of a first managed object that is to be available for the computer system to be in the desired state;

in response to the determining that the managed object instances cache does not include an indication of an instance of the first managed object that is to be available for the computer system to be in the desired state,

invoking a managed object manager to detect an instance of the first managed object at least in part by inventorying managed objects according to a managed object inventory policy, wherein the managed object inventory policy is received from a server and wherein the managed object inventory policy specifies a schedule for invoking the managed object manager, one or more managed objects to inventory, one or more managed object definitions, and one or more inventory settings, and

storing an indication of the detected instance in the managed object instances cache; and

determining, by the computer system, whether the computer system is compliant with the desired state based at least in part on indications of instances of managed objects stored in the managed object instances cache and the properties of managed objects specified by the desired state.

2. The method of claim 1 wherein the first managed object is a hardware element.

3. The method of claim 1, further comprising:

evaluating an inheritance of a second managed object to identify properties of the second managed object inherited from other managed objects.

4. The method of claim 3, further comprising:

performing an action for each of the other objects from which the second managed object inherits.

5. The method of claim 1, further comprising:

determining whether an indication of an instance of a selected managed object stored in the managed object instances cache is within tolerance at least in part by determining whether the selected managed object has been inventoried within a predetermined period of time; and

in response to determining that the indication of the instance of the selected managed object stored in the managed object instances cache is not within tolerance at least in part by determining whether the selected managed object has been inventoried within a predetermined period of time, invoking the managed object manager to detect an instance of the selected managed object at least in part by inventorying managed objects according to the managed object inventory policy.

6. The method of claim 1, further comprising:

after performing an action associated with the first managed object, storing the results of performing the action associated with the first managed object in the managed object instances cache.

7. The method of claim 1, further comprising:

in response to determining that the computer system is not in the desired state,

for each managed object, of the plurality of managed objects that are to be available for the computer system to be in the desired state, that is not available,

identifying, from among a plurality of managed object handlers, a managed object handler configured to perform an action for the managed object that is not available, and

invoking the identified managed object handler to perform the action for the managed object that is not available.

8. A computer system, having a memory and a processor, comprising:

a component configured to receive a specification of at least one property for each of a plurality of managed objects that are not allowed to be present on the computer system for the computer system to be in a desired state, wherein each managed object is associated with a unique identifier to uniquely distinguish the managed object in a managed environment;

a component configured to determine whether the computer system is compliant with the desired state based at least in part on properties of instances of managed objects associated with the desired state and stored in a cache;

a component configured to, for each of the managed objects that is not allowed to be present in the computer system for the computer system to be in the desired state and for which an instance is stored in the cache, perform an action associated with the managed object so that the computer system is brought into compliance with the desired state;

a component configured to receive a managed object inventory policy from a server, wherein the managed object inventory policy specifies a schedule for invoking a managed object manager, one or more managed objects to inventory, and one or more managed object definitions, wherein the managed object manager is configured to;

determine that an instance of a first managed object detected in the cache is not fresh enough to be returned as inventory,

in response to the determination that the instance of the first managed object detected in the cache is not fresh enough to be returned as inventory,

invoke a detect action for the first managed object,

determine that an instance of a second managed object detected in the cache is not fresh enough to be returned as inventory,

in response to the determination that the instance of the second managed object detected in the cache is not fresh enough to be returned as inventory,

invoke an enumerate action for the first managed object, wherein the enumerate action is different from the detect action; and

a component configured to evaluate an inheritance of a first managed object to identify properties of the first managed object inherited from other managed objects at least in part by recursively executing a first action associated with the first managed object for each of the other managed objects from which the first managed object inherits properties.

9. The computer system of claim 8 wherein the component configured to perform an action associated with the first managed object is further configured to perform an action for each of the other objects from which the first managed object inherits properties.

10. The computer system of claim 8 wherein the action associated with a first managed object is a remove action.

11. The computer system of claim 8, further comprising:

a component configured to display a user interface for authoring the specification of the at least one property for each of the plurality of managed objects that are not allowed for the computer system to be in a desired state.

12. The computer system of claim 8, further comprising:

a component configured to determine whether each of a plurality of instances of managed objects stored in the cache are within tolerance.

13. A computer-readable memory storing instructions that, if executed by a computer system having a memory, a plurality of managed object handlers, and a processor, cause the computer system to perform operations comprising:

receiving a specification of a first managed object that is to be available for the computer system to be in a desired state, wherein the first managed object is associated with a unique identifier to uniquely distinguish the first managed object in a managed environment;

receiving a managed object inventory policy specifying a schedule for invoking a managed object manager, one or more managed objects to inventory, and one or more inventory settings;

determining that an instance of the first managed object is not stored in a managed object instances cache of the computer system; and

in response to the determining that an instance of the first managed object is not stored in the managed object instances cache of the computer system,

identifying, from among the plurality of managed object handlers, a managed object handler configured to perform an action for the first managed object that is to be available for the computer system to be in the desired state, and

invoking the identified managed object handler to perform the action for the first managed object that is to be available for the computer system to be in the desired state;

caching, in the managed object instances cache, a first result of performing the action for the first managed object that is to be available for the computer system to be in the desired state; and

in response to determining that the cached first result of performing the action for the first managed object that is to be available for the computer system to be in the desired state is stale,

purging, from the managed object instances cache, the cached first result of performing the action for the first managed object that is to be available for the computer system to be in the desired state.

14. The computer-readable memory of claim 13 wherein the action performed for the first managed object is an enumerate action and wherein an action performed for a second managed object is a detect action, wherein the enumerate action is different from the detect action.

15. The computer-readable memory of claim 13 wherein the first managed object is associated with a managed element corresponding to a list of settings associated with an application.

16. The computer-readable memory of claim 13, the operations further comprising:

evaluating an inheritance of the first managed object to identify properties of the first managed object inherited from other managed objects.

17. The computer-readable memory of claim 16 wherein performing an action performed for the first managed object comprises performing an action associated with each of the other managed objects from which the first managed object inherits properties.

18. The computer-readable memory of claim 13, the operations further comprising:

determining whether an indication of an instance of the first managed object stored in the cache is within tolerance, wherein the tolerance specifies a period of time.

19. The computer-readable memory of claim 13, the operations further comprising:

storing, in the managed object instances cache, the results of performing a first action associated with the first managed object; and

storing, in the managed object instances cache, the results of performing a second action associated with a second managed object,

wherein the first action is different from the second action.

20. The computer-readable memory of claim 13, the operations further comprising:

in response to the purging, from the managed object instances cache, the cached first result,

invoking the identified managed object handler configured to perform the action for the first managed object,

caching, in the managed object instances cache, a second result of performing the action for the first managed object, and

sending the cached second result of performing the action for the first managed object to a management system running at a server; and

in response to determining that the cached first result of performing the action for the first managed object that is to be available for the computer system to be in the desired state is stale, sending the cached first result of performing the action for the first managed object to the management system at the server.