Agent_deletion - btry/glpi-plugin GitHub Wiki

#Agent deletion

There are two cases where an agent must be deleted from the database

• after success ful enrollment
• after explicit deletion by an administrator

When an administrator unenrolls an agent, a MQTT message is sent to the device running this agent to process unenrollment. Once the unenrollemnt is done, the agent sends a MQTT message to acknoledge the unenrollment request.

The backend waits for this acknoledgment to actually delete the agent from the database. The delay to send this acknoledgment is undertermined but should happen because the device is in the end of a cycle but still owned by legitimate user and is used in normal operations.

When an enrolled device is lost or stolen, and it appears impossible to retrieve it, the administrator may want to delete its data from the database. In such case we cannot unenroll th device as it is very likely offline forever. We need to delete the agent and maybe the associated computer by force.

To do this the admini strator deletes the agent fron his user interface. Next he is free to delete or keep the associated computer. This means that deleting the agent does cascade a computer deletion. This is an extra and manual action taken by the administrator.