Skip to main content

Our network team requires that we push machine ethernet/wi-fi profiles for ISE compliance to our Macs. We use Centrify to join our Macs to AD and push certs. They're no longer able to push machine profiles after the release of Big Sur (Apple GP change). We've been trying to use Jamf and it's just not working. Jamf nor Centrify support have been able to help.

We have a working config profile, but we get an error that the computer is not bound to AD if using Centrify. If I connect the Mac to our domain via Apple Directory Utility it works, but we lose out on other Centrify capabilities like password sync. We know Jamf Connect is an option, but I'd like to keep using Centrify for now.

Has anyone run into this? Have you found a workaround/fix?

Thanks

It may be time to move on to a new tool unfortunately. Or find a totally new work flow for your certificates that does not rely on Centrify. 

If your certificate authority is still an AD CS server, the JAMF AD CS connector may be able to get certificates from it that will work. Depending on if the certificate templates are good enough, they may satisfy your 802.1x certificate requirement. If a SCEP certificate would be good enough JAMF can also issue those from a configuration profile.

 

It may be time to move on to a new tool unfortunately. Or find a totally new work flow for your certificates that does not rely on Centrify. 

If your certificate authority is still an AD CS server, the JAMF AD CS connector may be able to get certificates from it that will work. Depending on if the certificate templates are good enough, they may satisfy your 802.1x certificate requirement. If a SCEP certificate would be good enough JAMF can also issue those from a configuration profile.

 


Ok. Thanks for the info.

Terms & ConditionsCookie settingsAccessibility statement