Resilio Connect Management Console allows to remotely disconnect an agent and thus remove it from all jobs.
Understanding what happens next comes from knowing how agent is authorized on MC - using bootstrap token and client token (read more).
Files removalWhen removing agent from MC this way, mind parameter "Keep folder data" in Agent profile as it may force agent to remove files which were part of the job.
Here's what happens when admin deletes an Agent from the Console
Agent's client_token is erased from MC records and agent is not authorized anymore.
If agent was connected to MC using only MC's IP address (no config file), it will automatically send new request for approval with same client_token.
If agent was connected to MC using sync.conf file, it will use bootstrap_token when attempting to automatically reconnect within 30 seconds after being removed. If bootstrap_token in config is valid, the Agent will successfully reconnect. If bootstrap_token is invalid, agent will send request for approval.
Until the Agent reconnects, here's what will happen with other MC's components:
The agent will free up one seat in the license of its type (server, desktop, NAS or universal)
Agent will be removed from jobs. So if the removed agent was the only source in a Distribution or Consolidation job, the job run will give the error "There are no source agents".
Agent won't rejoin the job unless auto sorting of groups is enabled. Admin shall manually add the agent to all the jobs. Note, that the agent won't also continue interrupted distribution or consolidation job run automatically.
Removed agent will be also removed from its groups. The Agent will rejoin the group if group sorts agents by tags.
Removing Management console agent
If admin accidentally removed Management console agent, it will automatically re-connect to Management console after 420 seconds. It's also necessary to add the agent back to is groups and jobs.
Removing agent from the agent's side
Stop agent process and delete its storage folder.