jamf/Setup-Manager
1
0
Fork 0
mirror of https://github.com/jamf/Setup-Manager.git synced 2026-02-03 14:13:24 +00:00
Code Issues 37 Actions Packages Projects Releases Wiki Activity

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

New Issue
Closed
opened 2026-01-19 18:31:28 +00:00 by michael · 7 comments
michael commented 2026-01-19 18:31:28 +00:00
Owner
Copy Link

Originally created by @iamflaurian on GitHub.

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

Originally created by @iamflaurian on GitHub. 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
michael added the bugSupport labels 2026-01-19 18:31:28 +00:00
michael commented 2026-01-19 18:31:28 +00:00
Author
Owner
Copy Link

@scriptingosx commented on GitHub:

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

@scriptingosx commented on GitHub: Do you have the `DEBUG` key set to `true` in your profile?
michael commented 2026-01-19 18:31:28 +00:00
Author
Owner
Copy Link

@iamflaurian commented on GitHub:

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.

@iamflaurian commented on GitHub: > > 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.
michael commented 2026-01-19 18:31:28 +00:00
Author
Owner
Copy Link

@scriptingosx commented on GitHub:

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 commented on GitHub: 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.
michael commented 2026-01-19 18:31:28 +00:00
Author
Owner
Copy Link

@scriptingosx commented on GitHub:

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?

@scriptingosx commented on GitHub: > 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?
michael commented 2026-01-19 18:31:28 +00:00
Author
Owner
Copy Link

@iamflaurian commented on GitHub:

No

@iamflaurian commented on GitHub: No
michael commented 2026-01-19 18:31:29 +00:00
Author
Owner
Copy Link

@iamflaurian commented on GitHub:

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.

@iamflaurian commented on GitHub: 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.
michael commented 2026-01-19 18:31:29 +00:00
Author
Owner
Copy Link

@scriptingosx commented on GitHub:

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

@scriptingosx commented on GitHub: 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
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
duplicate
enhancement
enhancement
question
Support
wontfix
No Label bug Support
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
michael
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: jamf/Setup-Manager#84
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?