Can I force MSC to check for new Managed Packages?

32 views
Skip to first unread message

Alex Bernal

unread,
Feb 6, 2024, 10:46:04 AMFeb 6
to munki-discuss
Hi All,

I just added some new packages through MunkAdmin, but they are not installing on the Clients yet. I verified that the packages exist at the SoftwareRepoURL, so I think MSC just hasn't phoned home yet so it not aware of them.

Can I run a terminal command to force MSC to phone home, detect the new packages, and install them? If so what is the command? If not, how often does MSC check, and can I change the interval?

Nick McSpadden

unread,
Feb 6, 2024, 11:00:24 AMFeb 6
to munki-...@googlegroups.com
You can use MSC.app to check for updates, or you can invoke it via the Terminal:
`sudo managedsoftwareupdate`

Munki checks for updates approximately once an hour:

--
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 view this discussion on the web visit https://groups.google.com/d/msgid/munki-discuss/6331fc47-30d2-43c2-84e9-9c1d5c657f30n%40googlegroups.com.


--
--
Nick McSpadden
nmcsp...@gmail.com

Gregory Neagle

unread,
Feb 6, 2024, 11:04:06 AMFeb 6
to 'Gregory Neagle' via munki-discuss
See also https://github.com/munki/munki/wiki/Overview#munki-behaviors

People new to Munki are often quite anxious to tweak the default behaviors they don’t yet quite understand. Take your time and live with the default behaviors for a bit. Most people find they are just fine.

-Greg

Alex Bernal

unread,
Feb 6, 2024, 11:19:10 AMFeb 6
to munki-discuss
Thanks Nick, that command was what I needed. I ran it, but my package was not installed. In fact, the output of the command makes no mention of it.

The way this was set up, every Mac is represented as a Manifest in MunkiAdmin (by serial Number), let's call is M1. M1 Contains M2, which Contains M3. M3 is configured with some Managed Instals, including my new package and Zoom. 

When I first turned on the laptop, MSC advised a Zoom update was available, and I installed it with no issue. Since the New Package is in the same Manifest (M3) as Zoom, and in the same section (Managed Installs) as Zoom, I thought it would have been silently/force installed. I also verified the package is configured as Unattended Install.

I must still be missing something; and in case it's relevant, the package is Microsoft Company Portal. I'm going to be enrolling the Macs in Intune.

Gregory Neagle

unread,
Feb 6, 2024, 11:27:41 AMFeb 6
to munki-...@googlegroups.com
A tip/suggestion:

Instead of _describing_ your issue —  show it.

Show us the output of `/usr/local/munki/managedsoftwateupdate`.

Show us the manifests — they are just text files.

This is far more useful for everyone than just a description, which might easily leave important info out.

-Greg

Alan

unread,
Feb 6, 2024, 11:35:48 AMFeb 6
to munki-...@googlegroups.com
Any time you make a change to your repo, you probably want to run makecatalogs

Not sure if you did that.

That said, your best bet to see what's going on is to look at verbose output from the client Mac:

Alex Bernal

unread,
Feb 6, 2024, 11:51:35 AMFeb 6
to munki-discuss
Gregory, here are the manifests and the output of the update command. You will see mention of MacOS Ventura, but this is rejected sine the it's already installed.

Last login: Tue Feb  6 10:48:57 on console

administrator@### ~ % sudo managedsoftwareupdate

Password:

Managed Software Update Tool

Copyright 2010-2023 The Munki Project

https://github.com/munki/munki


Starting...

Checking for available updates...

    Retrieving list of software for this machine...

    Retrieving list of software for this machine...

    Preventing idle sleep

WARNING: Could not process item outset for install. No pkginfo found in catalogs: production

WARNING: Could not process item outset-custom for install. No pkginfo found in catalogs: production

WARNING: Rejected item Install_macOS_Ventura, version 13.2.1 with maximum os version required 12.99. Our OS version is 13.2.1.

WARNING: Could not process item Install_macOS_Ventura for install. No pkginfo found in catalogs: production

ERROR: Error executing script installcheck_script: [Errno 2] No such file or directory: '/tmp/munki-o2130j20/installcheck_script'

ERROR: Error executing script installcheck_script: [Errno 2] No such file or directory: '/tmp/munki-o2130j20/installcheck_script'

ERROR: Error executing script installcheck_script: [Errno 2] No such file or directory: '/tmp/munki-o2130j20/installcheck_script'

    Getting client resources...

    Getting client resources...

    Allowing idle sleep

Finishing...

    Performing postflight tasks...

Done.

administrator@### ~ % 


apps_universal M4
bus_dev M2
Mac Manifest M1
common M3

Gregory Neagle

unread,
Feb 6, 2024, 3:01:48 PMFeb 6
to munki-...@googlegroups.com
A lot of issues going on there in that managedsoftwareupdate run. Which are you working on resolving first?

-Greg

To view this discussion on the web visit https://groups.google.com/d/msgid/munki-discuss/2235eb74-0218-4233-a521-ee7089d57e2fn%40googlegroups.com.
<apps_universal M4.xml><bus_dev M2.xml><Mac Manifest M1.xml><common M3.xml>

Gregory Neagle

unread,
Feb 6, 2024, 3:04:35 PMFeb 6
to munki-...@googlegroups.com
Also, you’ll find it useful/instructive to run managedsoftwareupdate with one or more -v flags to get more detail. I usually go straight to `managedsoftwareupdate -vvv` but that might be overwhelming…

-Greg

Alex Bernal

unread,
Feb 6, 2024, 3:08:13 PMFeb 6
to munki-discuss
The only thing I need to do is get Company Portal installed. I honestly don't know what the rest of the errors refer to and they have likely been there for months.

Alex

Alan

unread,
Feb 6, 2024, 4:44:55 PMFeb 6
to munki-...@googlegroups.com
Please try sudo managedsoftwareupdate -vvv --checkonly to see where exactly it's failing.

Reply all
Reply to author
Forward
0 new messages