MCX for chrome not taking effect.

[GaToRAiD]

So I'm trying to get a setting changed in chrome via JSS, but I'm running into some issues. First off, I had an issue importing manifest into the console, but was able to get that taken care of. Now, I'm having the issue that the setting is not being applied. Here is the actual code that should be changed in the manifest, but it's not being changed.

<dict>
            <key>pfm_description</key>
            <string></string>
            <key>pfm_name</key>
            <string>EnableOnlineRevocationChecks</string>
            <key>pfm_targets</key>
            <array>
                <string></string>
            </array>
            <key>pfm_title</key>
            <string></string>
            <key>pfm_type</key>
            <string>boolean</string>
</dict>

I wouldn't have an issue changing the lines in the manifest file but I'm not sure I which line I should be editing to make the value "True". I've tried looking up the info on chromium to make the change but they just said make the setting "True".

[Matt · Accepted solution]

Yep I built my preference by hand and dropped it into the following location

/Library/Managed Preferences/User/

Worked like a charm.

Here is the policy key:

http://www.chromium.org/administrators/policy-list-3

[tron_jones]

Did you try this post to get it to upload correctly?

https://jamfnation.jamfsoftware.com/discussion.html?id=8587

[GaToRAiD]

Yes, it uploads fine, my issue is it's not taking the settings on client computer's once I've set them in JSS.

[Matt]

I am having the exact same issue. I have the manifest uploaded and have all my edits, computers are targeting the MCX correctly, however it never applies.

[GaToRAiD]

Thanks for the response Matt. Do you know how to add the setting manually to the com.google.chrome.manifest file so it will turn it on?

[Matt · Accepted solution]

Yep I built my preference by hand and dropped it into the following location

/Library/Managed Preferences/User/

Worked like a charm.

Here is the policy key:

http://www.chromium.org/administrators/policy-list-3

[GaToRAiD · Accepted solution]

Matt, here is an update. I found out some new information that might shed some light on the whole issue.

https://code.google.com/p/chromium/issues/detail?id=97590

Stated in the link above changing the manifest file does nothing, you need to have OS X server running and use Workgroup Manager to create a new file that Chrome uses for it's information.

[Matt]

I would assume uploading the manifest to JSS and deploying would work though.

[GaToRAiD]

Matt, did you make a plist when you dropped it into that location or did you make a manifest file?

[Matt]

I created a PLIST.