Learn how to move a device from one Blueprint to another
You can easily move devices between Blueprints. Once moved, the device will receive all of the items and parameters specified in the destination Blueprint. Moving a device ensures all of the device's history is retained across multiple Blueprints.
Examples
Below are a few examples of why you may wish to move devices to a new Blueprint.
- A user has moved from one department to another, and their device needs a new set of applications and parameters enforced.
- You've finished testing an updated Blueprint for your team, and you're ready to deploy it to your team.
- A Blueprint is no longer needed; however, a few devices are still assigned that you wish to keep enrolled in Kandji.
Instructions
- Login to Kandji and open the device record you wish to move.
- Click on the More (...) button and select Edit Blueprint Assignment.
- Select the Blueprint to which you wish to move this device, then click Change.
Results
macOS
Mac computers will enforce Parameters and other Agent-driven Library Items, like Passport, the next time the Mac checks in via the Kandji agent. Parameters that were enforced on the previous Blueprint will change from their current state unless a new parameter enforces a different behavior. Auto Apps and Custom apps that were enforced in the previous Blueprint will not be removed, but Profiles, and Apps and Books apps will be added or removed as soon as possible during the next MDM check-in. More information about the differences in MDM and Agent check-in types can be found in our macOS Check-In support article.
iOS, iPadOS, and tvOS
All Library Items, including apps and profiles, will be added or removed as soon as possible during the next MDM check-in. More information about iOS check-in can be found in our iOS Check-In support article.
For more detailed information about taking action on devices, see the Devices section of our Knowledge Base.