Comment #10 on issue 7147 by joshwisenbaker: Mac Chrome should be able to
be centrally managed with MCX preferences/manifest
http://code.google.com/p/chromium/issues/detail?id=7147
As Apple expands in the enterprise market we see more and more use of
managed preferences via MCX policy.
Failu
Comment #9 on issue 7147 by hildahlp: Mac Chrome should be able to be
centrally managed with MCX preferences/manifest
http://code.google.com/p/chromium/issues/detail?id=7147
I agree with the reasons/cases cited above. We have 600+ Mac OS X clients.
--
You received this message because you ar
Comment #8 on issue 7147 by dayglojesus: Mac Chrome should be able to be
centrally managed with MCX preferences/manifest
http://code.google.com/p/chromium/issues/detail?id=7147
The big reason one of my senior sysadmins is reluctant to deploy Firefox is
this exact issue of policy-based
contro
Comment #2 on issue 7147 by adamsc: Mac Chrome should be able to be
centrally managed with MCX preferences/manifest
http://code.google.com/p/chromium/issues/detail?id=7147
Two comments:
* If Chrome does not use the Keychain (i.e. using CA certificates from
/Library/Keychains/System.keychain
Comment #1 on issue 7147 by pmbuko: Mac Chrome should be able to be
centrally managed with MCX preferences/manifest
http://code.google.com/p/chromium/issues/detail?id=7147
MCX-controllable preferences would put Chrome on equal footing with Safari
on the Mac
platform. Ease of management is a
Status: Unconfirmed
Owner: all-bugs-t...@chromium.org
Labels: Type-Bug Pri-2 OS-All Area-Misc
New issue 7147 by nigel.kersten: Mac Chrome should be able to be centrally
managed with MCX preferences/manifest
http://code.google.com/p/chromium/issues/detail?id=7147
Chrome Version : N/A
URLs
