github-starred/MonitorControl

Fork 0

mirror of https://github.com/MonitorControl/MonitorControl.git synced 2026-05-15 14:15:55 -06:00

[GH-ISSUE #747] Managed Preferences #489

New issue

Closed

opened 2026-05-05 06:07:07 -06:00 by gitea-mirror · 8 comments

gitea-mirror commented

2026-05-05 06:07:07 -06:00

Owner

Originally created by @iceman60 on GitHub (Oct 28, 2021).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/747

Before opening the issue, have you...?

Searched for existing issues

I'm packaging MonitorControl at work and I need to control updates manually. I actually can't control any preferences using my MDM platform.

Describe the solution you'd like

Use the /Library/Preferences to control MC configurations. First I need to control Automatically Check for Update setting and be able to disable the Check for updates.. menu.

Describe alternatives you've considered

Blocking update retrieve by FW rules

Anything else?

thanks for your work !

Originally created by @iceman60 on GitHub (Oct 28, 2021). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/747 ### Before opening the issue, have you...? - [X] Searched for existing issues ### Is your feature request related to a problem? Please describe I'm packaging MonitorControl at work and I need to control updates manually. I actually can't control any preferences using my MDM platform. ### Describe the solution you'd like Use the /Library/Preferences to control MC configurations. First I need to control _Automatically Check for Update_ setting and be able to disable the _Check for updates.._ menu. ### Describe alternatives you've considered Blocking update retrieve by FW rules ### Anything else? thanks for your work !

gitea-mirror

2026-05-05 06:07:07 -06:00

closed this issue
added the
Status: Abandoned

enhancement
labels

gitea-mirror commented

2026-05-05 06:07:16 -06:00

Author

Owner

@waydabber commented on GitHub (Oct 28, 2021):

You can change Automatic Check by updating me.guillaumeb.MonitorControl.plist under the user's Library/Preferences (SUEnableAutomaticChecks).

Currently there is no way to disable the check for update menu and button under About but a setting could be added for that in the preferences file.

@waydabber commented on GitHub (Oct 28, 2021): You can change Automatic Check by updating me.guillaumeb.MonitorControl.plist under the user's Library/Preferences (SUEnableAutomaticChecks). Currently there is no way to disable the check for update menu and button under About but a setting could be added for that in the preferences file.

gitea-mirror commented

2026-05-05 06:07:20 -06:00

Author

Owner

@iceman60 commented on GitHub (Oct 29, 2021):

Didn't see this plist 🤭
Correct ?

@iceman60 commented on GitHub (Oct 29, 2021): Didn't see this plist 🤭 Correct ? ![image](https://user-images.githubusercontent.com/4654408/139445186-d6a2f987-e886-4f3d-8182-898f811bbe84.png)

gitea-mirror commented

2026-05-05 06:07:22 -06:00

Author

Owner

@waydabber commented on GitHub (Oct 29, 2021):

Yes that should work.

@waydabber commented on GitHub (Oct 29, 2021): Yes that should work.

gitea-mirror commented

2026-05-05 06:07:24 -06:00

Author

Owner

@iceman60 commented on GitHub (Oct 29, 2021):

Nope.

the checkbox is not grayed or hidden

@iceman60 commented on GitHub (Oct 29, 2021): Nope. the checkbox is not grayed or hidden

gitea-mirror commented

2026-05-05 06:07:28 -06:00

Author

Owner

@waydabber commented on GitHub (Oct 30, 2021):

Oh, that just changes the setting itself, does not gray out or hide the setting. There is currently no logic for that, a new DisableAutoUpdate setting should be implemented while making sure that a preferences reset does not wipe this setting.

An alternative solution until that time is to block the URL to the appcast.xml on the firewall so the app can't reach the update feed and check for updates.

The appcast feed is: https://monitorcontrol.app/appcast.xml

@waydabber commented on GitHub (Oct 30, 2021): Oh, that just changes the setting itself, does not gray out or hide the setting. There is currently no logic for that, a new `DisableAutoUpdate` setting should be implemented while making sure that a preferences reset does not wipe this setting. An alternative solution until that time is to block the URL to the appcast.xml on the firewall so the app can't reach the update feed and check for updates. The appcast feed is: `https://monitorcontrol.app/appcast.xml`

gitea-mirror commented

2026-05-05 06:07:30 -06:00

Author

Owner

@bradtchapman commented on GitHub (Nov 5, 2021):

Managed Preferences would be nice—perhaps @iceman60 should consider donating a lot more since they are clearly thinking about a mass deployment for enterprise—but we must consider more essential MDM-less deployments that ship with a "default" configuration, that still allow the user to make changes. Perhaps they want to get automatic updates?

Apple's Workgroup Manager on Open Directory was great because you could set a preference "once" and then allow the user to change it. Managed Preferences with MDM does not allow that sort of flexibility by design.

Deploying a pre-configured .plist doesn't work correctly. For instance, I tried editing the binary plist with PlistEdit Pro to set "SUEnableAutomaticChecks" to "false." The app still launched with "Automatic Updates" enabled. Prior to editing the file, I made sure MonitorControl was quit, ran "killall cfprefsd" to flush the cache, and then edited the file. On the next launch, MonitorControl ignored my setting and auto updates were enabled anyway.

P.S.: Thank you @waydabber for backporting 4.0.1 to to Mojave. It works a treat.

@bradtchapman commented on GitHub (Nov 5, 2021): Managed Preferences would be nice—perhaps @iceman60 should consider donating a lot more since they are clearly thinking about a mass deployment for enterprise—but we must consider more essential MDM-less deployments that ship with a "default" configuration, that still allow the user to make changes. Perhaps they want to get automatic updates? Apple's Workgroup Manager on Open Directory was great because you could set a preference "once" and then allow the user to change it. Managed Preferences with MDM does not allow that sort of flexibility by design. Deploying a pre-configured .plist doesn't work correctly. For instance, I tried editing the binary plist with PlistEdit Pro to set "SUEnableAutomaticChecks" to "false." The app still launched with "Automatic Updates" enabled. Prior to editing the file, I made sure MonitorControl was quit, ran "killall cfprefsd" to flush the cache, and then edited the file. On the next launch, MonitorControl ignored my setting and auto updates were enabled anyway. P.S.: Thank you @waydabber for backporting 4.0.1 to to Mojave. It works a treat.

gitea-mirror commented

2026-05-05 06:07:32 -06:00

Author

Owner

@waydabber commented on GitHub (Nov 5, 2021):

Well, changing settings is rather important for MonitorControl as all relevant stuff is constantly stored in user preferences not only simple settings. For a proper lockdown of some preferences in an enterprise environment to work a lot more work should be done. Obviously a generous enterprise donation would greatly accelerate the work on this but this is not generally on the radar at the moment.

Changing the SUEnableAutomaticChecks in the plist file should work (but note that there is an other setting that can be toggled which manages automatic download of the updates which is not exposed in the preferences GUI but can be enabled in the sparkle update popup window) if the cache is properly flushed (it is best to restart the mac or at least log in/out and also make sure that the preference file version under the ByHost folder is deleted as well as that can act as a secondary permanent storage for preferences).

@waydabber commented on GitHub (Nov 5, 2021): Well, changing settings is rather important for MonitorControl as all relevant stuff is constantly stored in user preferences not only simple settings. For a proper lockdown of some preferences in an enterprise environment to work a lot more work should be done. Obviously a generous enterprise donation would greatly accelerate the work on this but this is not generally on the radar at the moment. Changing the SUEnableAutomaticChecks in the plist file should work (but note that there is an other setting that can be toggled which manages automatic download of the updates which is not exposed in the preferences GUI but can be enabled in the sparkle update popup window) if the cache is properly flushed (it is best to restart the mac or at least log in/out and also make sure that the preference file version under the ByHost folder is deleted as well as that can act as a secondary permanent storage for preferences).

gitea-mirror commented

2026-05-05 06:07:34 -06:00

Author

Owner

@stale[bot] commented on GitHub (Nov 5, 2022):

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require attention? This issue may be closed if no further activity occurs. Thank you for your contributions.

@stale[bot] commented on GitHub (Nov 5, 2022): Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require attention? This issue may be closed if no further activity occurs. Thank you for your contributions.