Rollback AgentX migration
Rollback a migration from Logpoint Agent to AgentX to restore the previous configuration.
Prerequisites
Migration from Logpoint Agent to AgentX previously completed
Logpoint Agent Collector installed on endpoints
Device configurations have not been changed since migration
Administrator access to Logpoint
Important limitations
Rollback only works if configurations are unchanged You can only rollback the migration if device configurations have not been modified since the migration. If configurations were changed after migration, rollback is not possible.
Logpoint Agent must be reinstalled Before performing rollback, ensure Logpoint Agent Collector is installed on the endpoints. The rollback process does not automatically reinstall Logpoint Agent.
Procedure
Ensure Logpoint Agent Collector is installed on all endpoints that will be rolled back.
Go to Settings > Configuration and select AgentX.
Select Rollback.
Review the rollback information and select Yes to confirm.
Expected outcome
Logpoint displays a confirmation message when rollback completes successfully. Logpoint Agent resumes collecting logs from the endpoints using the original configuration.
Verification
Verify that Logpoint Agent service is running on the endpoints.
Go to the Logpoint search interface.
Run queries for both Logpoint Agent and AgentX logs to verify which is actively collecting:
Logpoint Agent logs:
AgentX logs:
Replace <hostname> with an endpoint hostname.
After successful rollback, Logpoint Agent logs should appear and AgentX logs should stop appearing for new events.
Configuration guidelines
Verify Logpoint Agent installation Before initiating rollback, verify that Logpoint Agent Collector is installed and configured correctly on all target endpoints. Rollback will fail if Logpoint Agent is not present.
Plan rollback during maintenance window During rollback, there may be a brief gap in log collection. Plan the rollback during a maintenance window to minimize impact.
Document rollback reason Document why rollback was necessary to inform future migration attempts and prevent recurring issues.
Last updated
Was this helpful?