Profile not installing via automatic install

I have two profiles setting proxies up in the com.apple.SystemConfiguration domain.

Both work if I double click on the profile and install via system settings, neither work if I install them via Self Service or pushing them from Jamf.

Running 'scutil --proxy' shows an empty dictionary and trying various websites that should work all fail.

I've tried a few different version of Sonoma and none work. I'm running "11.1.1-t1701704198" Jamf Pro on-prem.

Page 1 / 1

Here is one of the profiles with details redacted

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1">
  <dict>
    <key>PayloadUUID</key>
    <string>33707949-A585-4DE1-AD97-2049AFA2416A</string>
    <key>PayloadType</key>
    <string>Configuration</string>
    <key>PayloadOrganization</key>
    <string>Mouser Inc</string>
    <key>PayloadIdentifier</key>
    <string>33707949-A585-4DE1-AD97-2049AFA2416A</string>
    <key>PayloadDisplayName</key>
    <string>CBA_20231214</string>
    <key>PayloadDescription</key>
    <string>NOTE: This is a test profile that has PayloadRemovalDisallowed set to false so we can remove it if anything goes wrong. This will have to be set to true before production. The distribution method should also be changed at the same time.</string>
    <key>PayloadVersion</key>
    <integer>1</integer>
    <key>PayloadEnabled</key>
    <true/>
    <key>PayloadRemovalDisallowed</key>
    <true/>
    <key>PayloadScope</key>
    <string>System</string>
    <key>PayloadContent</key>
    <array>
      <dict>
        <key>PayloadUUID</key>
        <string>C798390D-7F1C-4F6B-B86E-DAD9BDACA34D</string>
        <key>PayloadType</key>
        <string>com.apple.SystemConfiguration</string>
        <key>PayloadOrganization</key>
        <string>Mouser Inc</string>
        <key>PayloadIdentifier</key>
        <string>C798390D-7F1C-4F6B-B86E-DAD9BDACA34D</string>
        <key>PayloadDisplayName</key>
        <string>Proxies</string>
        <key>PayloadDescription</key>
        <string/>
        <key>PayloadVersion</key>
        <integer>1</integer>
        <key>PayloadEnabled</key>
        <true/>
        <key>Proxies</key>
        <dict>
          <key>Exceptions</key>
          <array>
            <string>*.exmaple, *.example.com, autodiscover.example.com, lync.example.com.au, example.cloudfront.net, mymac.example.com</string>
          </array>
        	<key>FallBackAllowed</key>
          <integer>1</integer>
          <key>ProxyAutoConfigURLString</key>
          <string>http://config.example.com/example.pac</string>
          <key>ProxyAutoConfigEnable</key>
          <integer>1</integer>
        </dict>
      </dict>
    </array>
  </dict>
</plist>

Does Jamf show them as successfully installed?

They show as installed in the computer record and are also visible in the System Settings profile pane.

Here is one of the profiles with details redacted

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1">
  <dict>
    <key>PayloadUUID</key>
    <string>33707949-A585-4DE1-AD97-2049AFA2416A</string>
    <key>PayloadType</key>
    <string>Configuration</string>
    <key>PayloadOrganization</key>
    <string>Mouser Inc</string>
    <key>PayloadIdentifier</key>
    <string>33707949-A585-4DE1-AD97-2049AFA2416A</string>
    <key>PayloadDisplayName</key>
    <string>CBA_20231214</string>
    <key>PayloadDescription</key>
    <string>NOTE: This is a test profile that has PayloadRemovalDisallowed set to false so we can remove it if anything goes wrong. This will have to be set to true before production. The distribution method should also be changed at the same time.</string>
    <key>PayloadVersion</key>
    <integer>1</integer>
    <key>PayloadEnabled</key>
    <true/>
    <key>PayloadRemovalDisallowed</key>
    <true/>
    <key>PayloadScope</key>
    <string>System</string>
    <key>PayloadContent</key>
    <array>
      <dict>
        <key>PayloadUUID</key>
        <string>C798390D-7F1C-4F6B-B86E-DAD9BDACA34D</string>
        <key>PayloadType</key>
        <string>com.apple.SystemConfiguration</string>
        <key>PayloadOrganization</key>
        <string>Mouser Inc</string>
        <key>PayloadIdentifier</key>
        <string>C798390D-7F1C-4F6B-B86E-DAD9BDACA34D</string>
        <key>PayloadDisplayName</key>
        <string>Proxies</string>
        <key>PayloadDescription</key>
        <string/>
        <key>PayloadVersion</key>
        <integer>1</integer>
        <key>PayloadEnabled</key>
        <true/>
        <key>Proxies</key>
        <dict>
          <key>Exceptions</key>
          <array>
            <string>*.exmaple, *.example.com, autodiscover.example.com, lync.example.com.au, example.cloudfront.net, mymac.example.com</string>
          </array>
        	<key>FallBackAllowed</key>
          <integer>1</integer>
          <key>ProxyAutoConfigURLString</key>
          <string>http://config.example.com/example.pac</string>
          <key>ProxyAutoConfigEnable</key>
          <integer>1</integer>
        </dict>
      </dict>
    </array>
  </dict>
</plist>

I would use Profile Creator and sign the exported profile. Then upload it to Jamf Pro and distribute it to a Mac.

Did you try to change the Payload Scope? Some Profiles only work in User Scope.

Hi, so did you ever find the fix for this?

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded