Require Logout per application & Remote launch MSU.app

[treydock]

1) Is there something similar to "RestartAction" to force a logout per
application? Right now I have things set so Munki requires logout for
all updates, but I'd like to disable that feature and specify logout
on a per-application basis.

2) Also is there a way to launch the "Managed Software Updates.app"
remotely? So that if I send a command through ARD the update window
from Munki will come up at the login screen. Right now I use the
command line tool to force installing of updates, but no update
progress or anything comes up on the remote machine. Maybe a way to
run "Open Application" from ARD and have some way of remotely
simulating a 'click' on the "Update Now" button?

Thanks
- Trey

[Bernstein, Gary Robert]

On Mar 7, 2011, at 10:01 PM, treydock wrote:

> 1) Is there something similar to "RestartAction" to force a logout per
> application? Right now I have things set so Munki requires logout for
> all updates, but I'd like to disable that feature and specify logout
> on a per-application basis.
>

try: <key>RestartAction</key>
<string>RequireLogout</string>

> 2) Also is there a way to launch the "Managed Software Updates.app"
> remotely? So that if I send a command through ARD the update window
> from Munki will come up at the login screen. Right now I use the
> command line tool to force installing of updates, but no update
> progress or anything comes up on the remote machine. Maybe a way to
> run "Open Application" from ARD and have some way of remotely
> simulating a 'click' on the "Update Now" button?
>

I don't have my notes in front of me, but I think the following might work:
/usr/local/munki/managedsoftwareupdate --manualcheck

I believe this will open MSU.app and do a manual check.

> Thanks
> - Trey
>
> --
-Gary

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
-- "The reward for work well done is the opportunity to do more."

-- "I tried, but it didn't work" is a lot better than "I wish I'd tried."

Gary R. Bernstein Director of Computer Information & Access
bern...@illinois.edu Krannert Center for the Performing Arts
217-244-1038 College of Fine & Applied Arts - UIUC
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

[Greg Neagle]

On Mar 7, 2011, at 8:01 PM, treydock wrote:

> 1) Is there something similar to "RestartAction" to force a logout per
> application? Right now I have things set so Munki requires logout for
> all updates, but I'd like to disable that feature and specify logout
> on a per-application basis.

As Gary mentioned, Apple packages can have a "RequireLogout" as a RestartAction. munki will require logouts for these for Apple packages at least; not 100% certain what will happen if you add that key to a non-Apple package (drag-n-drop DMG, Adobe package, etc)

>
> 2) Also is there a way to launch the "Managed Software Updates.app"
> remotely? So that if I send a command through ARD the update window
> from Munki will come up at the login screen.

Assuming you mean you just want progress feedback:

/usr/local/munki/managedsoftwareupdate --auto
Will do a check, and if there are any updates, will install with progress feedback over the loginwindow.

[Bernstein, Gary Robert]

On Mar 7, 2011, at 10:32 PM, Greg Neagle wrote:

> On Mar 7, 2011, at 8:01 PM, treydock wrote:
>
>> 1) Is there something similar to "RestartAction" to force a logout per
>> application? Right now I have things set so Munki requires logout for
>> all updates, but I'd like to disable that feature and specify logout
>> on a per-application basis.
>
> As Gary mentioned, Apple packages can have a "RequireLogout" as a RestartAction. munki will require logouts for these for Apple packages at least; not 100% certain what will happen if you add that key to a non-Apple package (drag-n-drop DMG, Adobe package, etc)

I've noticed that with the RestartAction key that RequireRestart value will cause munki to force the user to logout, but the machine won't actually restart when the install is done.

It would be nice to have it actually restart or shutdown, but I am guessing that munki is assuming that the installer was going to take care of that, as opposed to munki having to do it.

[Greg Neagle]

On Mar 8, 2011, at 8:26 AM, Bernstein, Gary Robert wrote:

>
> On Mar 7, 2011, at 10:32 PM, Greg Neagle wrote:
>
>> On Mar 7, 2011, at 8:01 PM, treydock wrote:
>>
>>> 1) Is there something similar to "RestartAction" to force a logout per
>>> application? Right now I have things set so Munki requires logout for
>>> all updates, but I'd like to disable that feature and specify logout
>>> on a per-application basis.
>>
>> As Gary mentioned, Apple packages can have a "RequireLogout" as a RestartAction. munki will require logouts for these for Apple packages at least; not 100% certain what will happen if you add that key to a non-Apple package (drag-n-drop DMG, Adobe package, etc)
>
> I've noticed that with the RestartAction key that RequireRestart value will cause munki to force the user to logout, but the machine won't actually restart when the install is done.
>
> It would be nice to have it actually restart or shutdown, but I am guessing that munki is assuming that the installer was going to take care of that, as opposed to munki having to do it.

If the "RequireRestart" value came from the package itself, munki will restart after install.

If you manually add a "RestartAction" of "RequireRestart" to the pkginfo for a package that does not itself actually require a restart, you will see this behavior. In other words, on install, munki is using the package itself to determine if a restart is needed, while when checking for updates, it uses the pkginfo. If you think this is a bug, please file an enhancement request along with some opinions on how munki _should_ resolve instances when the RestartAction for the pkginfo is not the same as the RestartAction for the actual package.

-Greg