Best way to tell a client to stop updating for a while

[David Ross]

Is there a best practice for this?

I want to basically shut down munki updates on a client for a few days.
Actually have it stop trying to reach our munki server.

Thanks
David

[Mike Solin]

You’d probably have better luck controlling access to the server - either by changing the hostname, blocking IP ranges, etc.

If you pushed a script to your clients to stop checking in, how will they know to check in again? You’ve effectively cut off their ability to receive new instructions.

Mike

--

mi...@mikesolin.com / @flammable
http://mikesolin.com

> --
> You received this message because you are subscribed to the Google Groups "munki-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to munki-dev+...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[David Ross]

I can push out things via ARD or similar to run a script to turn things
back on.

I don't want ALL computers in an office to stop asking just certain ones.

I guess a related question is how often is the client configuration checked?

If I push out a defaults write for:
SupressUserNotification
SupressAutoInstall
SupressLoginwindowInstall
setting all to False will the MSU app see it every hour or at some other
time?

David

On 4/17/15 12:48 AM, Mike Solin wrote:
> You’d probably have better luck controlling access to the server -
> either by changing the hostname, blocking IP ranges, etc.
>
> If you pushed a script to your clients to stop checking in, how will
> they know to check in again? You’ve effectively cut off their
> ability to receive new instructions.
>
> Mike
>

[Tim Schutt]

How about temporarily adding an entry into your /etc/hosts that resolves your munki server to 127.0.0.1?

T.

[Adam Barnett]

Could you not just disable the launchd job? 

--

You received this message because you are subscribed to the Google Groups "munki-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to munki-dev+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Adam Barnett

[Gregory Neagle]

That would be my suggestion:

launchctl unload -w /Library/LaunchDaemons/com.googlecode.munki.managedsoftwareupdate-check.plist

and later, to resume checking:

launchctl load -w /Library/LaunchDaemons/com.googlecode.munki.managedsoftwareupdate-check.plist

-Greg

[Dials Mavis]

approx. once every hour, yo! FAQ

[Eric Holtam]

Unloading the LaunchDaemons are the way to go if you have remote access to the machines via other vectors.

Running `sudo launchctl -w unload /Library/LaunchDaemons/com.googlecode.munki.*` will disable the launchdaemons and stop them from loading even after reboot.

To turn the service back on run `sudo launchctl -w load /Library/LaunchDaemons/com.googlecode.munki.*`

Test first to verify it does what you expect.

-Eric

[David Ross]

Thanks.

On 4/17/15 8:58 AM, Gregory Neagle wrote:
> That would be my suggestion:
>
> launchctl unload -w
> /Library/LaunchDaemons/com.googlecode.munki.managedsoftwareupdate-check.plist
>
> and later, to resume checking:
>
> launchctl load -w
> /Library/LaunchDaemons/com.googlecode.munki.managedsoftwareupdate-check.plist
>
> -Greg
>
>> On Apr 17, 2015, at 5:16 AM, Adam Barnett <adamba...@gmail.com

[David Ross]

Yes. The FAQ does state how often the client checks the server for
updates but NOT how often the client checks to see if the preferences
have changed.

I guess my sub-question is does the client process check for pref
changes at each run or at boot time. I suspect each run.

On 4/17/15 7:07 AM, Dials Mavis wrote:
> approx. once every hour, yo! FAQ

> <https://github.com/munki/munki/wiki/FAQ#q-how-often-do-munki-clients-check-for-updates>

>
> On Friday, April 17, 2015 at 3:17:28 PM UTC+10, David Ross wrote:
>
> I can push out things via ARD or similar to run a script to turn things
> back on.
>
> I don't want ALL computers in an office to stop asking just certain
> ones.
>
> I guess a related question is how often is the client configuration
> checked?
>
> If I push out a defaults write for:
> SupressUserNotification
> SupressAutoInstall
> SupressLoginwindowInstall
> setting all to False will the MSU app see it every hour or at some
> other
> time?
>
> David
>
> On 4/17/15 12:48 AM, Mike Solin wrote:
> > You’d probably have better luck controlling access to the server -
> > either by changing the hostname, blocking IP ranges, etc.
> >
> > If you pushed a script to your clients to stop checking in, how will
> > they know to check in again? You’ve effectively cut off their
> > ability to receive new instructions.
> >
> > Mike
> >
> >>> On Apr 15, 2015, at 2:07 PM, David