Skip to main content
Use this when a Windows machine should enroll under a different client in the same organization. The new client uses one of its seats. The next config pull applies the new client’s policy and branding on this machine. Conversations already captured stay on the old client. New conversations are stored on the new client when that client has capture on. Do this in order. If the machine is still active on the old client, enrolling with the new client’s installer does not move it. The new client gets a row waiting for approval, with the reason Already enrolled under another client.

​
Before you start

On the new client’s Deployment tab, run that client’s installer in step 6. Its client key is already inside the script or the downloaded file. Do not reuse the old client’s script. Do not use the global key on Organization → General. The new client needs a free seat. When that client is already at its seat cap, the machine waits for approval instead of enrolling. This page is Windows. There is no macOS unenroll or uninstall script in Admin. To take a Mac’s seat back, open the client’s Devices tab and choose Disable on that row.

​
Move the machine

  1. On the old client, stop any scheduled enrollment job for this machine. The next run enrolls it again with the old client’s key.
  2. On the machine, remove the local enrollment and leave the apps installed. Open Scripts, and under Advanced: separate actions use Unenroll only. That downloads mspilot-unenroll.exe. Run it through the RMM as SYSTEM, or double-click the download and choose Yes when Windows asks for permission. If you skip this, the machine is still enrolled on the old client, and the new client’s installer does not enroll it again. See Unenroll.
  3. On the old client’s Devices tab, choose Disable on this row. The machine loses gateway access immediately, and the seat is freed. Leave this row disabled. After the machine is active on the new client, Enable on this old row fails with This machine and user already has an active agent.
  4. In the RMM, move this computer into the organization, site, or group that is mapped to the new client in MSPilot.
  5. In MSPilot, open Integrations, open the connected RMM, and choose Sync clients. Wait until this computer is listed on the new client’s Devices tab. Not Enrolled is enough.
  6. On the new client’s Deployment tab, or on Scripts with the new client selected, run the installer. See Install.
  7. On the new client’s Devices tab, confirm this machine is active. The old client’s row stays disabled.

​
This computer still belongs to the old client in the RMM

The RMM job shows enroll_error rmm_claim_client_mismatch. MSPilot reports That RMM computer belongs to a different client. This computer is not listed on the new client yet. Finish steps 4 and 5, then run the installer again. If the new client has no RMM record for this computer, the machine does not take a seat. It waits on the new client’s Devices tab, with the reason No RMM record for this machine.

​
You enrolled the new client before Disable

The new client shows a row waiting for approval. The reason is Already enrolled under another client. On the old client, choose Disable on this machine. Then on the new client, choose Approve on the waiting row. The new client needs a free seat. Or choose Reject on that waiting row, and start again at Move the machine.
Last modified on October 9, 2026