When you uninstall or reinstall an Endpoint Operations Management agent, various elements are affected, including existing metrics that the agent has collected, and the identification token that enables a reinstalled agent to report on the previously discovered objects on the server. To ensure that you maintain data continuity, it is important that you aware of the implications of uninstalling and reinstalling an agent.

There are two key locations related to the agent that are preserved when you uninstall an agent. Before reinstalling the agent, you must decide whether to retain or delete the files.

  • The /data folder is created during agent installation. It contains the keystore, unless you chose a different location for it, and other data related to the currently installed agent.

  • The epops-token platform token file is created before agent registration and is stored as follows:

    • Linux: /etc/vmware/epops-token

    • Windows: %PROGRAMDATA%/VMware/EP Ops Agent/epops-token

When you uninstall an agent, you must delete the /data folder. This does not affect data continuity.

However, to enable data continuity it is important that you do not delete the epops-token file. This file contains the identity token for the platform object. Following agent reinstallation, the token enables the agent to be synchronized with the previously discovered objects on the server.

When you reinstall the agent, the system notifies you whether it found an existing token, and provides its identifier. If a token is found, the system uses that token. If a token in not found, the system creates a new one. In the case of an error, the system prompts you to provide either a location and file name for the existing token file, or a location and file name for a new one.

The method that you use to uninstall an agent depends on how it was installed.