rikho / munki

Automatically exported from code.google.com/p/munki
Other
0 stars 0 forks source link

Munki 2 - SupressMyItems #367

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
If this is easy to implement, I would like an option for a new key.
This key would disable the buttons (similar to "AppleSoftwareUpdatesOnly") but 
it would also contact the munki repo.

This would be ideal in cases where users share a manifest, but you don't want a 
particular set of users to actually be able to install optional software.

sudo defaults write /Library/Preferences/ManagedInstalls SupressMyItems -bool 
true

Original issue reported on code.google.com by eriknico...@gmail.com on 18 Aug 2014 at 11:45

GoogleCodeExporter commented 9 years ago
"but you don't want a particular set of users to actually be able to install 
and remove optional software"

Original comment by eriknico...@gmail.com on 18 Aug 2014 at 11:46

GoogleCodeExporter commented 9 years ago
I don't see myself implementing such a feature. Every additional code path is 
yet another thing to test and make sure continues to function. Since a Munki 
admin could just create a different manifest without optional_installs, the 
problem can be addressed without the need to make the code more complex.

Original comment by gregnea...@mac.com on 18 Aug 2014 at 11:48

GoogleCodeExporter commented 9 years ago
Okay, I understand. I wasn't entirely sure how easy this would be, but was 
somewhat hopeful.

Original comment by eriknico...@gmail.com on 18 Aug 2014 at 11:53

GoogleCodeExporter commented 9 years ago
In this particular case, I was going to assign different MC X to the same 
machine based on user membership, to allow techs to install/remove software, 
but not allow a "normal" user.

Original comment by eriknico...@gmail.com on 18 Aug 2014 at 11:54

GoogleCodeExporter commented 9 years ago
So instead you can create a different manifest and use MCX to point the machine 
at that manifest. Same end result, no new Munki code.

Original comment by gregnea...@mac.com on 18 Aug 2014 at 11:55

GoogleCodeExporter commented 9 years ago
Why didn't I think of that.......

Okay, awesome.

Original comment by eriknico...@gmail.com on 18 Aug 2014 at 11:57

GoogleCodeExporter commented 9 years ago
If you use MCX to manage preferences, it must be done at the computer or 
computer group level:

https://code.google.com/p/munki/wiki/MCXSupportInMunki

Original comment by gregnea...@mac.com on 18 Aug 2014 at 11:57

GoogleCodeExporter commented 9 years ago
Perhaps I will look into a preflight script or a custom launchd then.

This puts me in the right direction.

Original comment by eriknico...@gmail.com on 18 Aug 2014 at 11:59

GoogleCodeExporter commented 9 years ago
Closing this.

Original comment by gregnea...@mac.com on 19 Aug 2014 at 12:00