Unable to decrypt encrypted profile - Configuration Profiles

[rhoward]

Hello,

We are having issues with Configuration Profiles. When we push out any configuration profile to machines, we often have this error "Unable to decrypt encrypted profile" when checking to see if it failed in the JSS. Usually if we use terminal and do either sudo jamf recon or sudo jamf manage commands it goes through, but it is not any more. We also just implemented more vLANs in our environment, but all of the other Casper functions like Remote, JSS Policies, Self Service, Managed Preferences, etc work normally. I checked the SSL and Tomcat tickets to make sure they were up to date and they are good. We are using Version 9.32. Any light on this would be great!

Ryan

[pinsent]

I ended up editing the Azure firewall IP list to include new listing that they released on 11/13/23. Hope that helps. It had nothing to do with the clients themselves.

[kkeirstead]

We are still getting the "Unable to decrypt encrypted profile" across all profiles. Verified with network security that all new IP addresses have been added to the firewall.

[Rebirthflame]

any resolution to this yet?

[Mithrandir]

I'm seeing this with newly created profiles on 11.6.1 hosted: "unable to decrypt encrypted profile."

[LuizOliver]

At my institution, we were experiencing the same issue. We updated the NetFramework server to version 4.8 and the connector to 1.1.

This solved the problem for us!

Using 11.9

[misveri]

If you are using Jamf Pro 11.9 and ADCS Connector, please read at https://learn.jamf.com/en-US/bundle/jamf-pro-release-notes-11.9.0/page/Important_Notices.html

" Integrations with Active Directory Certificate Services (AD CS) now require Jamf AD CS Connector 1.1.0.
Jamf AD CS Connector 1.1.0 requires .NET Framework 4.8 or later. "

Then take a look at https://www.rocketman.tech/post/update-your-jamf-ad-cs-connector and https://learn.jamf.com/en-US/bundle/technical-paper-integrating-ad-cs-current/page/Upgrading_the_Jam... on how to update.