Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JSM 1.2 beta: Setup Manager only supports Jamf solutions! (Setup Assistant / Enrollment) #87

Open
iamflaurian opened this issue Feb 18, 2025 · 7 comments
Labels
bug Something isn't working Support support question

Comments

@iamflaurian
Copy link

iamflaurian commented Feb 18, 2025

Hello,

First of all, I would like to say thank you for this great tool and for your effort in listening to our feedback as a community.

When I try to deploy JSM 1.2 beta by enrolling my MacBook Air (Apple Silicon, macOS 15.3.1), I receive the message: "Setup Manager only supports Jamf solutions!"—which should be the case, as I am using Jamf Pro as my MDM solution. I only have the option to restart the device, without the ability to continue. This means I have to go through the recovery process to re-install the client.

The only configuration change I made when upgrading from version 1.1 to 1.2 beta was modifying the "final action" key from "shutdown" to "restart".

Update and temporary solution:
It's actually to set "simulateMDM" with "Jamf Pro" which I not expected to set because of regular enrollment not using the debug mode. I re-install again, I got the same issue again. I reproduce it again, if I erase the MacBook Air and re-install macOS, delete the object on Jamf Pro, it works again with "simulateMDM".

greetings

@scriptingosx
Copy link
Collaborator

Do you have the DEBUG key set to true in your profile?

@scriptingosx scriptingosx added the Support support question label Feb 18, 2025
@iamflaurian
Copy link
Author

No

@scriptingosx
Copy link
Collaborator

when you switch the finalAction back to continue you should be able to continue setup without needing to restart. Alternatively, you can force quit Setup Manager with shift-ctrl-command-E before it reboots. Please share /Library/Logs/Setup Manager.log from an affected Mac.

@scriptingosx
Copy link
Collaborator

It's actually to set "simulateMDM" with "Jamf Pro" which I not expected to set because of regular enrollment not using the debug mode. I re-install again, I got the same issue again. I reproduce it again, if I erase the MacBook Air and re-install macOS, delete the object on Jamf Pro, it works again with "simulateMDM".

So this is quite confusing. Are you saying simulateMDM works, but only after erasing the device and deleting the record from Jamf Pro?

@iamflaurian
Copy link
Author

It's actually to set "simulateMDM" with "Jamf Pro" which I not expected to set because of regular enrollment not using the debug mode. I re-install again, I got the same issue again. I reproduce it again, if I erase the MacBook Air and re-install macOS, delete the object on Jamf Pro, it works again with "simulateMDM".

So this is quite confusing. Are you saying simulateMDM works, but only after erasing the device and deleting the record from Jamf Pro?

Exactly. I tested it two times.

@scriptingosx
Copy link
Collaborator

Have you tried deleting the computer record without setting the simulateMDM key? (Setup Manager doesn't read that key unless DEBUG is true)

Either way, log please? You can send to setupmanager (at) jamf.com if you don't want to post it here

@iamflaurian
Copy link
Author

You're right, "deleting the computer record without setting the simulateMDM key" also work but without deleting the computer record its not working. Logs coming in the next 15minutes to your email address.

@scriptingosx scriptingosx added the bug Something isn't working label Feb 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Support support question
Projects
None yet
Development

No branches or pull requests

2 participants