Closed GoogleCodeExporter closed 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
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
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
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
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
Why didn't I think of that.......
Okay, awesome.
Original comment by eriknico...@gmail.com
on 18 Aug 2014 at 11:57
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
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
Closing this.
Original comment by gregnea...@mac.com
on 19 Aug 2014 at 12:00
Original issue reported on code.google.com by
eriknico...@gmail.com
on 18 Aug 2014 at 11:45