There are two ways to delete the abandoned machine agent, either from controller UI by creating a dummy application or through a manual step to delete the agent from the database. See the steps for either process under Delete abandoned machine agent.
There are two solutions for this, found in Agent Status on .NET
The "account key doesn't match with the current account for machine id" message indicates that the account key generated by the AppDynamics Controller during the registration may be now changed. This could happen if you migrate the Controller without shutting down the agents.
Restart the agent to resolve the error.
Follow these steps to troubleshoot:
-XX:MaxPermSize=<value>) to a higher value (256m at least) and try again.
On requesting Agent logs in
<Application> -> Servers -> App Servers -> <tier> -> <node> -> Agents, you may experience a timeout of the log status.
One possible cause is that someone first requested the log and reset the agent before the log sends to the Controller. To resolve the error, reset the Agent before requesting the agent log.
To assign a Machine Agent to multiple applications on the same server, run one Machine Agent process for each application on a machine.
-Dappdynamics.agent.uniqueHostId=<<some unique value per application>>) to both Machine Agent and the App Agent.
-Dappdynamics.agent.uniqueHostId=a1for n1 and m1. and
-Dappdynamics.agent.uniqueHostId=a2for n2 and m2.
uniqueHostId valuecan be any unique value but should be different for each application.
Other than viewing the list of AppDynamics Agents in Settings, can I get a list of those Agents and their details in a spreadsheet format?
It's not out of the box, but there is a workaround: