Skip to main content
Question

Mac Studio Keeps Crashing or Restarting

  • February 6, 2023
  • 4 replies
  • 14 views
G
Forum|alt.badge.img+3

Hi Jamf Nation!

I have a Mac studio that continues to crash and/or restart once it is enrolled. When removed from enrollment, the user says this issue does not occur, but every time we do enroll, the problem starts up. I have removed it from policies with restart payloads but not sure what would cause this to happen multiple times a day. Has anyone else experienced this? 

Thanks!

~ G

    4 replies

    dvasquez
    Forum|alt.badge.img+16
    • dvasquez
    • Valued Contributor
    • 318 replies
    • February 6, 2023

    Any, enrollment policies set to on-going?  Well you did that, LOL

    OS version? 
    Is your Jamf Pro cloud or on-premises?

    thanks!

     

    dvasquez
    Forum|alt.badge.img+16
    • dvasquez
    • Valued Contributor
    • 318 replies
    • February 6, 2023

    You're using user enrollment? 

    Have you tried to use the enrollment command from a terminal:

    sudo jamf enroll -prompt or tried it with no policy run: sudo jamf enroll -prompt -noPolicy

    Thanks

    AJPinto
    Forum|alt.badge.img+26
    • AJPinto
    • Legendary Contributor
    • 2802 replies
    • February 7, 2023
    1. Independently verify the devices behavior. Make sure you don't just have a user trying to get out of having their device managed. Rule 1 of IT, "Never Trust the User". Never trusting the user comes before never speaking in absolutes and using "should" in every example.
    2. What do the JAMF Logs say? If there is a policy running that is doing this, so long as the policy is finishing you should see a log for it. Beyond that you will need to check the Logs on the Mac to see what is happening just before it goes down.
    3. Look at Extension Attributes, some of those may be scripts. A script is just a script and if a Mac does not like the script it does not care where it comes from.
    4. Reinstall macOS

    Lastly, it sounds like you are using user initiated enrollment. If this is an organization owned device, do not use user initiated enrollment, use Automated Device Enrollment. The only reason I mention this, is both JAMF and Apple will tell you to reinstall macOS next which is the next logical troubleshooting step as its just one device having issues.

    dvasquez
    Forum|alt.badge.img+16
    • dvasquez
    • Valued Contributor
    • 318 replies
    • February 7, 2023
    1. Independently verify the devices behavior. Make sure you don't just have a user trying to get out of having their device managed. Rule 1 of IT, "Never Trust the User". Never trusting the user comes before never speaking in absolutes and using "should" in every example.
    2. What do the JAMF Logs say? If there is a policy running that is doing this, so long as the policy is finishing you should see a log for it. Beyond that you will need to check the Logs on the Mac to see what is happening just before it goes down.
    3. Look at Extension Attributes, some of those may be scripts. A script is just a script and if a Mac does not like the script it does not care where it comes from.
    4. Reinstall macOS

    Lastly, it sounds like you are using user initiated enrollment. If this is an organization owned device, do not use user initiated enrollment, use Automated Device Enrollment. The only reason I mention this, is both JAMF and Apple will tell you to reinstall macOS next which is the next logical troubleshooting step as its just one device having issues.


    True, true on the Org-owned device use DEP or ABM and prestige.  

    Try not to use user enrollment. 

    Logs, logs...

    good advice @AJPinto 

     


    Terms & ConditionsCookie settingsAccessibility statement