mirror of
https://github.com/usnistgov/macos_security.git
synced 2026-02-03 05:53:24 +00:00
Monterey 800-171 .GlobalPreferences settings mobile config not importing into JAMF #158
Reference in New Issue
Block a user
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?
Originally created by @AlfredAleman on GitHub.
Summary
Once the project is run the mobile config for .GlobalPreferences settings will not import into JAMF and Apple Configurator. Both show up blank with no configurations within it. All settings are blank.
Steps to reproduce
Create a baseline using MsCP for 800-171
Open JSS and go to config profiles click new button and import the mobile config from your path.
Look at newly created Config Profile and all settings within it are blank and not configured
Navigate to the file and open with Apple Configurator 2 and inspect. Same behavior all settings are blank and not configured
I have created with Jamf Compliance editor and mscp command line and same results
Operating System version
Monterey all sub versions
Intel or Apple Silicon
both Intel based process and Apple Silicon Mac
What is the current bug behavior?
imports blank config profile into jamf pro
What is the expected correct behavior?
the import would create a config profile with settings to control auto reboot after 24 hour period
Relevant logs and/or screenshots
screen shots of the blank profiles and how I created the profile with the plist which does work
Output of checks
None
Possible fixes
(If you can, link to the line of code that might be responsible for the problem)
@robertgendler commented on GitHub:
Closing this issue. There isn't much that we can do about this. It's more a Jamf Pro thing.
@golbiga commented on GitHub:
@AlfredAleman I was just able to import using Jamf Compliance Editor. You are correct that uploading the
com.apple.GlobalPreferences.mobileconfigas is will not work within Jamf Pro, but it is a valid profile. If you open the profile with Low Profile.app it shows as valid, see image below.Jamf Compliance Editor uploads it as a custom profile, as we identified the same issue originally.
Hope this helps.