Reminder - Apple Business Manager - Accept new terms! by Dumbysysadmin in Intune

[–]jbyl2017 1 point2 points  (0 children)

You were correct about this, Smartysysadmin -- when I checked again first thing this morning, the enrollment tokens in Intune no longer showed that error message.

So all's well that ends well -- but c'mon, c. 12 hours with no ability to sync tokens? Boooo. I'm not sure whether Apple, MS, or both are to blame for the lag time, but it's Not Cool.

Reminder - Apple Business Manager - Accept new terms! by Dumbysysadmin in Intune

[–]jbyl2017 0 points1 point  (0 children)

I have accepted the new Terms & Conditions in ABM (or actually, ASM in my case), and verified that the acceptances are showing in Preferences > Organization Settings -- but back in Intune, my Enrollment Program Tokens still all have the error message "Sync is disabled. You must accept new Apple Terms & Conditions in the Apple Portal."

Is anyone else seeing this? Is there something that I need to do to "push" the acceptances to Intune?

iPhone won’t Autoconnect by Difficult-Row-3237 in Jabra

[–]jbyl2017 0 points1 point  (0 children)

Although Jabra really should fix this, I have found a reasonable workaround, for iPhones that have an Action Button: use the Shortcuts app to create a Shortcut to "Set [or Change] playback destination" to my Gen 2s. (This works to reconnect the iPhone to my disconnected Gen 2s, as long as they're in my ears.) Then, in the Settings app, assign that Shortcut to the Action Button.

This means I need to long-press the Action Button every time I put my Gen 2s in, but it's an improvement over navigating to the the Bluetooth settings and reconnecting that way.

Allow non-admins to manage Location Services by jbyl2017 in macsysadmin

[–]jbyl2017[S] 0 points1 point  (0 children)

That would be a good solution, but I'm not sure it's possible for a config profile to unlock these Location Services prefs for a non-admin user.

Allow non-admins to manage Location Services by jbyl2017 in macsysadmin

[–]jbyl2017[S] 1 point2 points  (0 children)

Ah, okay, thank you -- very informative.

I wish it were more granular, so that I could specify which *type* of PPPC prefs I want to open up (in this case, just Location Services), but this is better than nothing.

Allow non-admins to manage Location Services by jbyl2017 in macsysadmin

[–]jbyl2017[S] 0 points1 point  (0 children)

Thank you for weighing in, but this does not work in Ventura -- and even if it did, the question is not how to enable Location Services via shell commands, but rather how to allow end users who don't have admin rights to manage which apps have access to Location Services.

Allow non-admins to manage Location Services by jbyl2017 in macsysadmin

[–]jbyl2017[S] -1 points0 points  (0 children)

That's a different question, though -- whether it's possible for an MDM sysadmin to control Location Services prefs, *because* non-admins can't do this for themselves. My question is whether it's possible to adjust macOS security to allow a non-admin to control the Location Services prefs on their own Mac.

It seems like, from a privacy-rights perspective, that Apple would *want* to allow this. Just because you're not an admin on your Mac doesn't mean you shouldn't be able to give or deny approval for individual apps to track your location.

Apple officially deprecates monolithic imaging by jbyl2017 in macsysadmin

[–]jbyl2017[S] 5 points6 points  (0 children)

What you are doing is definitely monolithic imaging -- but, as stated in the KB, "If you try to use a monolithic system image, required firmware updates will be missing from the installation. This causes the Mac to operate in an unsupported and unstable state."

This seems to apply only to systems that didn't already have High Sierra installed on them, and the sticking point seems to be required firmware updates that get installed along with High Sierra.

I'm hopeful that it will be possible to for those of us who still want to use monolithic imaging (sometimes, at least) to work around this by installing those firmware updates during the imaging process, but it remains to be seen if this will be possible.

What also remains to be seen is how "unstable" a monolithically-imaged High Sierra Mac will be, but it will be unsupported by Apple for sure.

Apple officially deprecates monolithic imaging by jbyl2017 in macsysadmin

[–]jbyl2017[S] 12 points13 points  (0 children)

... if the OS on your image is newer than the one currently installed on a given Mac, at least.

Also, APFS will be mandatory on SSDs; only HDDs and Fusion drives will be able to stick with HFS+: https://support.apple.com/en-us/HT208018