Skip to main content
Solved

Deploying Configuration Profile Results in Error


Forum|alt.badge.img+4

I'm trying to deploy a new configuration profile that contains settings for kernel extensions, system extensions and privacy policy. When it attempts to push out JAMF results in an error:

-[__NSCFConstantString objectForKeyedSubscript:]: unrecognized selector sent to instance 0x7fff8adf40e0

This is an on-premise JAMF instance version 10.32.2 Has anybody else experienced this or something similar?

 

Best answer by Tribruin

I would break up the profile in to multiple profiles. I have seen that error when the profile includes invalid keys. Try create a profile for the kernel extensions, one for the system extensions, and a third for the PPPC settings. You can then narrow the scope of each profiles. In most cases you only need to scope the KEXTs to Catalina or lower and the SysExts to Big Sur. 

View original
Did this topic help you find an answer to your question?

3 replies

Forum|alt.badge.img+19
  • Honored Contributor
  • 582 replies
  • Answer
  • October 15, 2021

I would break up the profile in to multiple profiles. I have seen that error when the profile includes invalid keys. Try create a profile for the kernel extensions, one for the system extensions, and a third for the PPPC settings. You can then narrow the scope of each profiles. In most cases you only need to scope the KEXTs to Catalina or lower and the SysExts to Big Sur. 


Forum|alt.badge.img+9
  • Valued Contributor
  • 109 replies
  • October 17, 2021

Deploying profiles with kext approval payloads on M1 Macs renders an error as they are not compatible with Apple Silicon.


Forum|alt.badge.img+4
  • Author
  • New Contributor
  • 7 replies
  • October 18, 2021
Tribruin wrote:

I would break up the profile in to multiple profiles. I have seen that error when the profile includes invalid keys. Try create a profile for the kernel extensions, one for the system extensions, and a third for the PPPC settings. You can then narrow the scope of each profiles. In most cases you only need to scope the KEXTs to Catalina or lower and the SysExts to Big Sur. 


It did resolve whatever was occurring by breaking up the settings into individual profiles.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings