Patent Application

App. No. 19/057,839

Abstract

Claims (82)

1 . A method of automated software management of a managed endpoint, the method comprising:

identifying, at an agent located on the managed endpoint, a reboot policy, wherein the reboot policy indicates one or more reboot behaviors initiated after update operations are performed at the managed endpoint;

identifying, at the agent, a first update operation associated with a first level of criticality based on metadata associated with an instruction implemented to locally perform the first update operation on the managed endpoint;

comparing, at the agent, the first level of criticality of the first update operation with the reboot policy to determine a first reboot behavior;

transitioning, at the agent, an endpoint state to a first reboot state to actuate the first reboot behavior, wherein the first reboot state comprises one or more of an advised reboot state, a mandatory reboot state, or a critical reboot state; and

actuating, at the agent, the first reboot behavior using the first reboot state.

2 . The method of claim 1 , further comprising:

actuating, at the agent, the first reboot behavior when the first level of criticality for the first update operation is a highest level of criticality when compared to one or more additional levels of criticality for one or more additional update operations identified by the agent on the managed endpoint; and

pausing, at the agent, the first reboot behavior when the first level of criticality for the first update operation is not a highest level of criticality when compared to the one or more additional levels of criticality for the one or more additional update operations.

3 . The method of claim 2 , wherein:

the agent includes two or more engines and an engine management functionality;

the two or more engines are each associated with a management service implemented at the managed endpoint;

the first update operation is performed by a first engine of the two or more engines; and

the one or more additional update operations are performed by additional engines of the two or more engines.

4 . The method of claim 1 , wherein the first level of criticality comprises:

an advised level associated with the advised state actuating an advised reboot behavior;

a mandatory level associated the mandatory state actuating a mandatory reboot behavior; or

a critical level associated with the critical state actuating a critical reboot behavior.

5 . The method of claim 1 , wherein the first update operation includes installation of a first patch; and the first level of criticality is based on one or more of a criticality score of the first patch, a patch type of the first patch, or a vulnerability type of the first patch.

6 . The method of claim 1 , wherein the reboot policy further comprises:

associating the first level of criticality with an advised reboot behavior that includes deferring a reboot for a first period of time;

associating the first level of criticality with a mandatory reboot behavior that includes deferring the reboot for a second period of time; and

associating the first level of criticality with a critical reboot behavior that includes deferring the reboot for a third period of time,

wherein:

the first period of time is longer than the second period of time, and

the second period of time is longer than the third period of time.

7 . The method of claim 1 , further comprising:

identifying, at the agent, a second update operation associated with a second level of criticality, wherein the second level of criticality is based on metadata of the second update operation;

comparing, at the agent, the second level of criticality of the second update operation with the reboot policy to determine a second reboot behavior;

comparing, at the agent, the second level of criticality and the first level of criticality; and

updating, at the agent, the endpoint state to:

the first reboot state when the second level of criticality is not higher than the first level of criticality or when the second level of criticality is equal to the first level of criticality, or

a second reboot state when the first level of criticality is not higher than the second level of criticality.

8 . The method of claim 1 , further comprising:

providing, at the managed endpoint, information related to the first level of criticality associated with the first update operation;

receiving, at the agent, from a management device, a user preference for the first level of criticality associated with the first update operation; and

adjusting the first reboot behavior based on the user preference.

9 . The method of claim 1 , further comprising:

causing display, via a graphical user interface, information about one or more reboot options associated with the first update operation, wherein the information is based on the first level of criticality; and

receiving, via the graphical user interface, input for the one or more reboot options associated with the first update operation.

10 . The method of claim 1 , further comprising receiving, at the agent, a first update package from a management device, wherein the first update package includes instructions implemented to initiate the first update operation and the metadata of the first update operation.

11 . The method of claim 10 , wherein:

the agent includes two or more engines and an engine management module;

the two or more engines are each associated with a management service implemented at the managed endpoint; and

the reboot policy includes at least one policy instruction associated with each engine of the two or more engines.

12 . The method of claim 11 , wherein:

a first engine of the two or more engines performs the first update operation based on the first update package; and

the identifying the first update operation associated with the first level of criticality is performed by the engine management functionality of the agent.

13 . The method of claim 1 , further comprising receiving, at the agent, the reboot policy that is defined by a management device, wherein the reboot policy includes definitions update operation criteria that associate the first update operation with the advised reboot state, the mandatory reboot state, or the critical reboot state.

14 . One or more non-transitory computer-readable media having encoded thereon programming code executable by one or more processors to perform or control performance of operations to automate software management of a managed endpoint, the operations comprising:

identifying, at an agent located on the managed endpoint, a reboot policy, wherein the reboot policy indicates one or more reboot behaviors initiated after update operations are performed at the managed endpoint;

identifying, at the agent, a first update operation associated with a first level of criticality based on metadata associated with an instruction implemented to locally perform the first update operation on the managed endpoint;

comparing, at the agent, the first level of criticality of the first update operation with the reboot policy to determine a first reboot behavior;

transitioning, at the agent, an endpoint state to a first reboot state to actuate the first reboot behavior, wherein the first reboot state comprises one or more of an advised reboot state, a mandatory reboot state, or a critical reboot state; and

actuating, at the agent, the first reboot behavior using the first reboot state.

15 . The one or more non-transitory computer-readable media of claim 14 , wherein the operations further comprise:

actuating, at the agent, the first reboot behavior when the first level of criticality for the first update operation is a highest level of criticality when compared to one or more additional levels of criticality for one or more additional update operations identified by the agent on the managed endpoint; and

pausing, at the agent, the first reboot behavior when the first level of criticality for the first update operation is not a highest level of criticality when compared to the one or more additional levels of criticality for the one or more additional update operations.

16 . The one or more non-transitory computer-readable media of claim 14 , wherein the operations further comprise:

associating the first level of criticality with an advised reboot behavior that includes deferring a reboot for a first period of time;

associating the first level of criticality with a mandatory reboot behavior that includes deferring the reboot for a second period of time; and

associating the first level of criticality with a critical reboot behavior that includes deferring the reboot for a third period of time,

wherein:

the first period of time is longer than the second period of time, and

the second period of time is longer than the third period of time.

17 . The one or more non-transitory computer-readable media of claim 14 , wherein the operations further comprise:

identifying, at the agent, a second update operation associated with a second level of criticality, wherein the second level of criticality is based on metadata of the second update operation;

comparing, at the agent, the second level of criticality of the second update operation with the reboot policy to determine a second reboot behavior;

comparing, at the agent, the second level of criticality and the first level of criticality; and

updating, at the agent, the endpoint state to:

the first reboot state when the second level of criticality is not higher than the first level of criticality or when the second level of criticality is equal to the first level of criticality, or

a second reboot state when the first level of criticality is not higher than the second level of criticality.

18 . The one or more non-transitory computer-readable media of claim 14 , wherein the operations further comprise:

providing, at the managed endpoint, information related to the first level of criticality associated with the first update operation;

receiving, at the agent, from a management device, a user preference for the first level of criticality associated with the first update operation; and

adjusting the first-update operation reboot behavior based on the user preference.

19 . The one or more non-transitory computer-readable media of claim 14 , wherein the operations further comprise:

causing display, via a graphical user interface, information about one or more reboot options associated with the first update operation, wherein the information is based on the first level of criticality; and

receiving, via the graphical user interface, input for the one or more reboot options associated with the first update operation.

20 . The one or more non-transitory computer-readable media of claim 14 , wherein the operations further comprise:

receiving, at the agent, a first update package from a management device, wherein the first update package includes instructions implemented to initiate the first update operation and the metadata of the first update operation; and

receiving, at the agent, the reboot policy that is defined by a management device, wherein the reboot policy includes definitions update operation criteria that associate the first update operation with the advised reboot state, the mandatory reboot state, or the critical reboot state.

Assignments (9)