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
After you remove agent from Management console, here is what happens:
The agent will free up one seat in the license of its type(server, desktop, NAS or universal)
Agent will be removed from jobs it was directly added to. It means, you'll need manually fix jobs and re-add new source or destination agent there.
You'll see following error message in Management console:
Removed agent will be also removed from its groups.
Removing Management console agent
If you accidentally removed Management console agent, it will automatically re-connect to Management console after 420 seconds. You'll also need to re-add it to its jobs and groups.
- Once agent is removed from MC, its client_token is erased from MC records and agent is not authorized anymore. It's removed from the jobs Event 'Invalid authentication token" appears for this agent in Events. Agent appears as offline.
- Agent uses bootstrap token from its config file to attempt to reconnect to MC, in 30 seconds after being removed from MC.
- If bootstrap token matches that in MC settings, agent reconnects automatically. It won't re-join its job. To prevent agent from reconnecting in this case you may want to regenerate bootstrap in MC settings. All currently online agents wont be affected.
- If bootstrap on MC has changed by this time and token from config no longer matches it, agent won't reconnect.
Removing agent from the agent's side
Stop agent process and delete its storage folder.