Skip to main content

Moving Devices and Organizations

Change Ownership moves a device to another organization. Change Parent moves an organization, with everything under it, to a different parent. Both keep history.

ToUseWhere
Move one device to a different organizationChange OwnershipConfigure > Agents
Move an organization under a different parentChange ParentConfigure > Organizations
Stop collecting from a machineDeleteConfigure > Agents

Move a device to another organization​

Select the device on Configure > Agents, choose Change Ownership, and pick the destination organization.

What happens
The device recordMoves, with its identity and history.
CollectionResumes where it left off. History is not lost, and nothing is uploaded twice or duplicated.
New eventsAre recorded under the new organization.
Data already collectedStays with the organization that owned the device when the events arrived.

Update the deployment package​

As part of the move, point the device's deployment package at the new organization: its registration token, or the new client's RMM or PSA client ID.

After the moveResult
The agent is reinstalled, and its enrollment data is still on the machineThe device stays in the organization you moved it to, whatever the package says.
The machine is wiped, reimaged or restored from a nightly image, and the package points at the new organizationThe device comes back as itself in the new organization.
The machine is wiped, and the package still points at the old organizationIt enrolls in the old organization as a new device. The moved record keeps its history and receives nothing more.

Reinstalling with another organization's registration token does not move a device. A token reaches only the device records in its own organization, so the machine enrolls there as a new device and the original record keeps its history. See Agent identity and cloning.

What you need​

  • The destination is an organization in the same workspace.
  • You can manage agents in the device's current organization and create ingest keys in the destination. The Administrator, Organization Administrator, Engineer and Deployment Manager roles can do both.
  • The destination is not deleted. To move a device into a deleted organization, undelete the organization first.

Move an organization under a different parent​

Select the organization on Configure > Organizations, choose Change Parent, and pick the new parent.

  • Everything under the organization moves with it: its sub-organizations, devices and ingest keys.
  • History moves too, including data collected before the move. Past events show under the new parent right away.
  • Access follows the tree. People and tokens with access on the new parent can now see the organization, and those with access only on the old parent no longer can.

A move is refused when:

  • The new parent is the organization itself, one of its own sub-organizations, or deleted.
  • It would make the organization top-level.
  • It would push the deepest sub-organization past the tree's depth limit.
  • You are not an Administrator or Organization Administrator on both the current parent and the new parent. Moving a top-level organization needs that role on All organizations.

Moving a large organization can take a moment.

Delete a device​

Delete a device when you are uninstalling the agent and want collection to stop. To keep collecting from it under another organization, move it.

Select the device on Configure > Agents and choose Delete.

  • An agent that is still running stops collecting and idles.
  • Data the device already collected stays.
  • The machine stays deleted through wipes. If it is wiped, reimaged or reinstalled and tries to enroll in the same organization, it is refused. To resume collection on the device, undelete it in the app, then reinstall the agent.
  • Installing with a different client's registration token or client ID enrolls the machine there as a new device, without the old record's history.

To bring a device back, undelete it on Configure > Agents.

  • A machine that is wiped and enrolls again comes back as itself, with its history.
  • A machine whose agent is still installed and idling needs its agent service restarted.