Anyone here see this before? - Configuring MDM push services

[motionbug]

Context:
Building Custom Packer Image with Tart Provisioner

Following the completion and upload of the build to the OCI repository, the image is downloaded, cloned, and then configured with Tart to create a new Mac and serial number for the virtual machine.

tart set --random-mac --random-serial <nameofvm>

The VM is enrolled, but an issue arises. Although the MDM profile is installed, it is stalled. Upon a reboot, the following startup message is displayed: after this message, the MDM profile is functional, but the device is incompletely enrolled.

This behaviour does not occur when using VM images from the Tart public registry.

Could anyone provide an explanation or have encountered this issue before?

[edigaryev]

Hi Rob,

Would you mind showing some more steps to reproduce this? I.e. how do you enroll a VM and install an MDM profile?

[motionbug]

Thanks @edigaryev

The ghcr.io/cirruslabs/macos-sequoia-vanilla:latest image have a rotating UUID, on the packer builds that I make, even with

--random-mac --randon-serial

the UUID of the device stays the same.

What am I missing, is there some other thing that you are doing to build the packer images where the UUIDs are removed after build?

Thanks