Kaseya VSA deleted devices: re-enrollment and history recovery

At a glance

Deleting a device in VSA 10 unenrolls it and clears its configuration settings. Preserve earlier exports and contact Kaseya support about recovering the record or its history before re-enrollment.

Distinguish VSA 10 device unenrollment from restoring previous inventory, configuration and historical records.

Published Updated

On this page

Understand what deleting a device changes

The Device Management guide describes Delete Devices and warns that it unenrolls devices and clears configuration settings. This does not specify the availability of historical inventory or a deleted-record recovery operation.

Resolve the version and desired outcome

Record whether the source is VSA 9 or VSA 10, the native device identifier, organization/site and deletion time. Check permissions and filters before diagnosing deletion. Ask support whether the record can be restored, which associated datasets survive and whether re-enrollment preserves identity or creates a new record.

Do not use VSA 9 machine-account behavior as evidence for VSA 10. Resuming agent check-ins, retrieving an audit event, restoring the platform record and recovering endpoint files are four separate tasks.

Preserve already captured evidence

Search retained device exports and reports using identifiers and capture date. A prior CSV may answer which organization owned the device; it cannot recreate omitted history or endpoint files. Keep the original export and a separate investigation note rather than editing the historical evidence.

Contact support before re-enrollment

Give Kaseya support the device details and ask what can be recovered, whether there is a deadline, and whether re-enrollment preserves its earlier identity. Keep the answer with your exports so the next technician knows which history remains available.

Official source

VSA 10 device management