Mobile device management agent rollback systems and methods
Systems and methods for mobile device management (MDM) agent rollback are disclosed. In some embodiments, a system configured to perform operations including: detecting a triggering event during operation of a first MDM agent; designating the first MDM agent as a bad agent; designating a second MDM agent as a new active agent; determining whether a first data generated by the first MDM agent is useable for continued operations by the second MDM agent; if the first data is determined to be useable by the second MDM agent, then activating the second MDM agent for continued operations using the first data; and if the first data is determined to be not useable by the second MDM agent, then activating the second MDM agent with known good data.
1. A system for operating one or more mobile device management (MDM) agents, comprising:
at least one processor;
a memory operatively coupled to the at least one processor, the memory storing processor-readable instructions configured to perform operations including at least:
detecting a triggering event during operation of a first MDM agent;
designating the first MDM agent as a bad agent;
designating a second MDM agent as a new active agent;
determining whether a first data generated by the first MDM agent is useable for continued operations by the second MDM agent;
if the first data is determined to be useable by the second MDM agent, then activating the second MDM agent for continued operations using the first data; and
if the first data is determined to be not useable by the second MDM agent, then activating the second MDM agent with known good data.
2. The system of claim 1 , wherein detecting a triggering event during operation of a first MDM agent comprises detecting a crash of the first MDM agent.
3. The system of claim 1 , wherein detecting a triggering event during operation of a first MDM agent comprises detecting a commands reachability failure.
4. The system of claim 1 , wherein detecting a triggering event during operation of a first MDM agent comprises detecting a manual initiation of an MDM agent rollback.
5. The system of claim 1 , wherein designating the first MDM agent as a bad agent comprises changing a designation of the first MDM agent from an active agent to an inactive agent.
6. The system of claim 1 , wherein designating a second MDM agent as a new active agent comprises re-designating the second MDM agent from being an inactive agent to being the new active agent.
7. The system of claim 1 , wherein the second MDM agent comprises an updated version of the first MDM agent.
8. The system of claim 1 , wherein designating the second MDM agent as a new active agent comprises:
determining that the second MDM agent is an older version than the first MDM agent; and
designating the second MDM agent as a new active agent.
9. The system of claim 1 , wherein designating the second MDM agent as a new active agent comprises:
determining that the second MDM agent is not an older version than the first MDM agent;
obtaining an older MDM agent that is older than the first MDM agent; and
re-designating the older MDM agent as the second MDM agent.
10. The system of claim 1 , wherein the first data comprises first replica data stored during operation of the first MDM agent.
11. The system of claim 1 , wherein the known good data comprises second data stored during operation of the second MDM agent.
12. A system for operating one or more mobile device management (MDM) agents, comprising:
at least one processor;
a memory operatively coupled to the at least one processor, the memory storing an MDM master, a first MDM agent designated as an active agent, and a second MDM agent designated as an inactive agent, wherein the MDM master is configured to perform operations including at least:
detecting a triggering event during operation of the first MDM agent;
designating the first MDM agent as a bad agent;
re-designating the second MDM agent as the active agent; and
determining whether to allow the second MDM agent to use data generated by the first MDM agent or to use other data associated with the second MDM agent.
13. The system of claim 12 , wherein detecting a triggering event during operation of the first MDM agent comprises detecting a failure signal from a monitoring tool of the first MDM agent, the failure signal being indicative of an operational failure of the first MDM agent.
14. The system of claim 12 , wherein detecting a triggering event during operation of the first MDM agent comprises detecting that a command from the first MDM agent has failed to provoke a response within a designated timeout period, and detecting that a subsequent remedial action has failed to provoke the response within the designated timeout period.
15. The system of claim 12 , wherein the MDM master comprises one or more privileged components configured to perform one or more operations that require device owner privileges.
16. The system of claim 12 , wherein the MDM master comprises:
one or more privileged components configured to perform one or more operations that require device owner privileges; and
one or more general components configured to perform one or more operations that do not require device owner privileges, at least some of the one or more general components being configured with a business logic of at least one of an MDM managed entity or an MDM managing entity.
17. The system of claim 12 , wherein the MDM master comprises:
one or more privileged components configured to perform one or more operations that require device owner privileges; and
wherein at least one of the first MDM agent or the second MDM agent comprises one or more general components configured to perform one or more operations that do not require device owner privileges, at least some of the one or more general components being configured with a business logic of at least one of an MDM managed entity or an MDM managing entity.
18. The system of claim 12 , wherein determining whether to allow the second MDM agent to use data generated by the first MDM agent or to use other data associated with the second MDM agent comprises:
determining that a first replica data generated by the first MDM agent is useable for continued operations by the second MDM agent.
19. The system of claim 12 , wherein determining whether to allow the second MDM agent to use data generated by the first MDM agent or to use other data associated with the second MDM agent comprises:
determining whether a first data generated by the first MDM agent is useable for continued operations by the second MDM agent;
if the first data is determined to be useable by the second MDM agent, then activating the second MDM agent for continued operations using the first data; and
if the first data is determined to be not useable by the second MDM agent, then activating the second MDM agent with known good data associated with the second MDM agent.
20. The system of claim 12 , wherein detecting a triggering event during operation of a first MDM agent comprises:
at least one of:
detecting a crash of the first MDM agent;
detecting a commands reachability failure of the first MDM agent; or
detecting a manual initiation of an MDM agent rollback.