Munki KickStart

[Matt Jelley]

Hi All,

I'm just wanting to clarify something. If I've installed the Munki KickStart pkg onto my MacBook's should it run every time the MacBook's are ideal and on the login window? I have been installing multiple applications and Mac OS updates with Munki and now I'm seeing workstations not pulling updates. I re-run the Munki KickStart pkg from my USB key log off then it pulls updates. It's like the KickStart is being removed on its own but not sure why.

Any guidance would be great.

Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Employees of ClickOn IT London Ltd are expressly required not to make defamatory statements and not to infringe or authorise any infringement of copyright or any other legal right by email communications. Any such communication is contrary to company policy and outside the scope of the employment of the individual concerned. The company will not accept any liability in respect of such communication, and the employee responsible will be personally liable for any damages or other liability arising. This email, its content and any files transmitted with it are intended solely for the addressee(s) and may be legally privileged and/or confidential. If you are not the attended recipient please delete and contact the sender via e-mail return. Unless expressly stated otherwise, this e-mail does not form part of a legally binding contract or agreement between the recipient and ClickOn IT London Ltd.

Unless otherwise stated to be non confidential, this email and any attachments are private and confidential and are for the addressee only. If you have received this email in error, please notify us upon receipt and delete it from your records

ClickOn IT London Ltd is registered in England and Wales (registered no. 05907730). Registered Office: Trident Court, 1 Oakcroft Road, Chessington, Surrey, KT9 1BD

[David Nelson]

When the computer starts, Munki looks for a file called “/Users/Shared.com.googlecode.munki.checkandinstallatstartup” and runs immediately if found. When it’s done the file is removed. 

As you could infer from this, the kickstart process is designed to run once — for example to get everything installed right away after bootstrapping a new machine. 

If you do want it to run on every boot you could make an outset script that touches the file on every boot, essentially achieving the same thing as reinstalling the kickstart package on every boot. 

--
You received this message because you are subscribed to the Google Groups "munki-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to munki-discus...@googlegroups.com.
To post to this group, send email to munki-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/munki-discuss/79ed60f7-b3de-4d32-8fd1-e543802771e0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[David Nelson]

Oops, missed a slash. 

/Users/Shared/.com.googlecode.munki.checkandinstallatstartup