If you have a macOS .jce file open and then try and open an iOS .jce file, the later will open a blank JCE window. Below are steps to reproduce:
Open Jamf Compliance Editor (v1.4.0)
Select “macOS “tab
Select “Create new project”
Select “sequoia”
a. Create
b. Save (~/Security Baselines)
Select “CIS Benchmark – Level 1” from Security Benchmark list
a. OK
Make a change (e.g.: deselect checkbox next to rule 2.3.1.1 Disable AirDrop)
Click “Create Guidance” button
Click Save Settings
a. Change Save As: to “Sequoia.jce”
b. Save (~/Security Baselines)
Close Jamf Compliance Editor
Open Jamf Compliance Editor (v1.4.0)
Select “iOS/iPadOS “tab
Select “Create new project”
Select “iOS 18”
a. Create
b. Save (~/Security Baselines)
Select “CIS Benchmark – Level 1 Enterprise” from Security Benchmark list
a. OK
Make a change (e.g.: deselect checkbox next to rule 3.2.1.6 Disable iCloud Keychain Sync)
Click “Create Guidance” button
Click Save Settings
a. Change Save As: to “iOS18.jce”
b. Save (~/Security Baselines)
Close Jamf Compliance Editor
Double-click iOS18.jce
a. Should open as expected with all rules and modifications
Close Jamf Compliance Editor
Double-click sequoia.jce
a. Should open as expected with all rules and modifications, but it opens to a blank JCE window.
@golbiga recommended this command as a quick workaround. Can swap back and forth depending on which OS baselines .jce you are trying to open.
defaults write com.jamf.complianceeditor mscpBaseURL "WHEREYOURFOLDERIS"
If you have a macOS .jce file open and then try and open an iOS .jce file, the later will open a blank JCE window. Below are steps to reproduce:
@golbiga recommended this command as a quick workaround. Can swap back and forth depending on which OS baselines .jce you are trying to open.
defaults write com.jamf.complianceeditor mscpBaseURL "WHEREYOURFOLDERIS"