Replies: 1 comment
-
|
I've figured out the issue regarding the failing installation: When setting no value for Password Content Regex via iMazing Profile Editor, the profile still contains <key>customRegex</key>
<dict>
<key>passwordContentDescription</key>
<dict>
<key>default</key>
<string>Password must match custom regex.</string>
</dict>
</dict>After removing the whole customRegex segment, the profile could be installed. But this makes the workflow even more cumbersome, as signing can't be done directly within and after the consolidation in iMazing Profile Editor, but Apple Configurator or |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
When I run
generate_guidance.py -p ..., a number of .mobileprofile-files will be generated. I'm using CIS Level 2 as a baseline which leads to 17 .mobileprofile files. As it it cumbersome to install so many profiles manually on a Mac without an MDM, I want to consolidate them. Asgenerate_guidance.pydoesn't have an option to generate a consolidated profile file, what are your best practices to do so? Just c&p all the PayloadContent dicts together?The separate profiles I could install without issues (I just had to remove the Password Content Regex, as this settings requires the profile to be installed from an MDM server):

I've tried to merge the profiles using iMazing Profile Editor which shows me several warnings:
I've just ignored the warnings as I guess iMazing Profile Editor just doesn't know the options mSCP is using. But I can't install the consolidated profile, as the installation fails with "The profile ... could not be installed due to an unexpected error. CPDomainPlugIn:101" Do you have any hints what the issue is?
Beta Was this translation helpful? Give feedback.
All reactions