Open noahtalerman opened 1 year ago
Hey @zhumo taking this off the drafting board because we won't get to it in the next sprint. I added it to FF because I think we want to bring it back.
Marcos: We can do this programmatically. fleetd will do the unenroll from the old MDM and turn on MDM again to talk to Fleet.
If that’s the case, does this need to be done at all?
On Thu, Sep 14, 2023 at 12:19 PM Noah Talerman @.***> wrote:
Marcos: We can do this programmatically. fleetd will do the unenroll from the old MDM and turn on MDM again to talk to Fleet.
— Reply to this email directly, view it on GitHub https://github.com/fleetdm/fleet/issues/13667#issuecomment-1720009920, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABI4PYRQABT7CZZ7OFDHO6LX2NKCPANCNFSM6AAAAAA4IBL3LU . You are receiving this because you were mentioned.Message ID: @.***>
Marcos: 2 scenarios: 1) device is not connected to Azure and 2) device is connected to Azure
1) Easier: Programmatically unenroll via Windows API => programmatically enroll via API (already do this)
2) Is it possible to do the migrate w/o logging the user out of the device? @marcosd4h can you please leave a comment w/ the Windows APIs we should use to test this?
The MDM programmatic APIS exposed by Windows SDK are detailed here.
We can use UnregisterDeviceWithManagement with an empty argument to unenroll the device from ongoing MDM server.
Then RegisterDeviceWithManagement, RegisterDeviceWithManagementUsingAADCredentials, and RegisterDeviceWithManagementUsingAADDeviceCredentials could be used to enroll the device to a different MDM server.
Hey @dherder adn @pintomi1989 , we filed a separate user story for this request.
I removed this request from the feature fest board.
cc @rachaelshaw
User stories
22075