Refs: #148942, #241773
Complexity: 3
Create Issue
Last month the implementation of macOS policy was on the test plan. I provided testers with a sample configuration profile. This month, i've implemented generation of those profiles in core and ship them with each release.
Follow the public documentation (in vnext) to edit and install a configuration profile bundled with the latest insiders. Confirm that:
- The default
.mobileconfig file (+ your policy edits) work as expected when installed on your machine
- The schema files under
Contents/Resources/app/policies/<locale> can be used to generate a .mobileconfig via a GUI app like https://imazing.com/profile-editor
I am intentionally being vague here in hopes that the public documentation is sufficient - please provide feedback on the clarity of those docs as well!
Notes
- See this issue for details on additional policy that is not yet documented
Known issues
Refs: #148942, #241773
Complexity: 3
Create Issue
Last month the implementation of macOS policy was on the test plan. I provided testers with a sample configuration profile. This month, i've implemented generation of those profiles in core and ship them with each release.
Follow the public documentation (in vnext) to edit and install a configuration profile bundled with the latest insiders. Confirm that:
.mobileconfigfile (+ your policy edits) work as expected when installed on your machineContents/Resources/app/policies/<locale>can be used to generate a.mobileconfigvia a GUI app like https://imazing.com/profile-editorI am intentionally being vague here in hopes that the public documentation is sufficient - please provide feedback on the clarity of those docs as well!
Notes
Known issues