Agent Identity and Cloning
Every endpoint running the SparkLogs Agent has one device record in your workspace. That record carries the endpoint's history: its events, its collection health, and the organization (for most MSPs, a client) it belongs to.
What keeps its identity
The same device record is kept across:
- Agent reinstalls, including an uninstall that wipes local enrollment state (
PURGE_STATE=1) followed by a fresh install into the organization the device belongs to. - Reimaging a machine from its own backup image, including a rebuild back to a known-good baseline.
- Daily disk-restore tools that revert the system volume on every reboot, such as Deep Freeze. A machine that is thawed and refrozen every night keeps one device record rather than adding one per day.
- Hostname changes, including a display name that changes when a VPN connects. A device is never given a new identity because its name changed.
An endpoint that keeps its local enrollment data through a reinstall stays on its device record, whatever the new installer carries. An endpoint that lost that data, through a purge, a reimage or a disk-restore cycle, enrolls again into the organization its installer points at. That is the organization of its registration token, or the client organization that its RMM or PSA client ID matches under that token.
- If that organization holds the device's record, the endpoint returns to it.
- If the record belongs to another organization, the endpoint enrolls as a new device in the organization the installer points at. The other record keeps its history, and this endpoint no longer reports to it.
A registration token never takes over, moves or reveals a device record that belongs to another client. To move a device to another organization, use Change Ownership, then point the endpoint's deployment package at the new client. See Moving devices and organizations.
All of this identifies a machine by its own hardware. An endpoint that reports no stable hardware identity, such as some virtual machines, should enroll from a prepared image so each one is distinct from first boot.
When the stored identity no longer matches
An install is never failed because the identity stored on the endpoint no longer matches a device record.
- A device that changed hands, or that is restored from a backup old enough that the record it names is gone, receives a fresh identity and starts collecting.
- Enrollments of the same endpoint that start at the same moment produce one device record, not several. Scripting a rollout across a fleet, or reimaging many machines at once, does not leave you with duplicate device records for one endpoint.
Enrollment is refused on purpose for a device you deleted yourself. Deleting a device stops that machine from enrolling again into the same organization, through later wipes and reinstalls. To bring it back at the same client, undelete it on Configure > Agents.
An install that resolves to an organization you deleted is refused too. Undelete the organization, then run the install again. To reuse the hardware for a different client, install with that client's registration token or RMM or PSA client ID. The machine enrolls there as a new device.
Change which organization owns a device
Move a device to another organization with Change Ownership. The move holds while the endpoint keeps its local enrollment data. After a wipe, reimage or restore, the endpoint enrolls where its installer points, so update its deployment package to the new client as part of the move. See Moving devices and organizations for what moves, what stays, and what you need.
Reuse a machine for a different client
Two ways to hand a physical endpoint to a new client:
- Keep its device record: use Change Ownership on Configure > Agents, and point the endpoint's deployment package at the new client.
- Start fresh: wipe the endpoint and install the agent with the new client's registration token or RMM or PSA client ID. It enrolls there as a new device with none of the old record's history. Delete the old record if the machine is not coming back to the previous client.
Either way, data collected under the previous client stays with that client. See Moving devices and organizations.
Cloned machines
An image captured with agent enrollment data still on it, then deployed to many machines, gives every one of those machines the same starting identity.
SparkLogs separates them without any action from you:
- The duplication is detected automatically, and each machine is separated onto its own identity soon after both machines are running.
- The machine that was there first keeps the original device record and its history.
- Each other machine receives its own device record and collects under it from then on.
- A machine that is split off and later rebuilt or restored returns to the record it already owns. Repeated wipe or restore cycles do not add new records.
Until the separation completes, the machines sharing one record are reported together on Configure > Agents, so the row's name and health can move between them. That settles once each machine is on its own record.
Separation needs both machines to be running and checking in. A pair whose second machine has been powered off for a long time stays on one record until it comes back. In rare cases, two machines are such complete copies of each other that no automatic check can tell them apart, and they stay on one record. The same can happen on hardware that does not report a distinguishing identity of its own. If a pair does not separate on its own, SparkLogs support can move one of the machines onto a fresh record remotely, with no visit to the endpoint and no reinstall. The machine collects under its new record from then on, and the record left behind is retired separately so you decide what happens to its history. Separating a pair this way needs agent 1.9.7 or later on the endpoint.
Cloning without preparation works. A prepared image is better, because every clone enrolls with its own identity from first boot. See Prepare a golden image.
No duplicate data
A device that comes back from a reinstall, a reimage, or a nightly restore resumes where it left off. It does not re-upload log or telemetry data that already reached SparkLogs, so a fleet of frozen machines does not re-ingest the same history on every thaw.