This usually happens when the file is not a simple system extension .plist.
The System Extensions section expects a basic plist that contains only the system extension identifiers and related values. Some ESET configuration files are actually complete Apple configuration profiles with multiple payloads bundled together, such as:
– VPN or network filter settings
– System extension policy
– Privacy Preferences Policy Control / Full Disk Access settings
– Web content or firewall filter settings
For this type of file, you do not need to split the payloads manually. Save the XML profile with a .mobileconfig extension and deploy it as a custom configuration profile instead:
1. Save the file as something like ESET_Endpoint.mobileconfig.
2. Go to Policies > macOS > Deploy Custom Configuration.
3. Upload the .mobileconfig file.
4. Associate the policy with a test Mac first.
5. Save the policy.
This allows macOS to receive all included payloads together as a complete configuration profile.
Regards,
Mary Romero