Munki Client Warnings and Errors

[rp...@ussa.org]

Hi All,

We've deployed munki to clients with Mac OS 10.9 and 10.10.  We push Microsoft Office 2011 and 2016 to these clients and I've created minimum and maximum OS versions for each based on Microsoft's requirements.

When running the Managed Software Center from the terminal, I see the following errors for my 10.10 clients and same errors for 10.9 but replacing 2011 with 2016.  Each time MSC runs it adds a new entry in the local logs.

• Rejected item Microsoft Office 2011, version 14.1.0 with maximum os version required 10.9.5. Our OS version is 10.10.5.
• Could not process item Microsoft Office 2011 for install. No pkginfo found in catalogs: prod
• Rejected item Microsoft Office 2011 Update, version 14.6.2 with maximum os version required 10.9.5. Our OS version is 10.10.5.
• Could not process item Microsoft Office 2011 Update for install. No pkginfo found in catalogs: prod

The errors were inconsequential (save for the log files filling up) at first as I expected this to be a side effect of the rejected software. But now we're using MunkiReport-PHP for reporting and I'm concerned that valid errors and warnings will be lost in the sea of the above errors causing admins to ignore the feature due to the "false positives".

Anyone else experiencing this and can explain how they resolved it?  Maybe I've configured min/max wrong or can suppress errors if there is a rule associated?

Thanks for any feedback.

Ron

[Gregory Neagle]

On May 3, 2016, at 2:19 PM, rp...@ussa.org wrote:

Hi All,

We've deployed munki to clients with Mac OS 10.9 and 10.10.  We push Microsoft Office 2011 and 2016 to these clients and I've created minimum and maximum OS versions for each based on Microsoft's requirements.

Does this mean your manifests have both Office2011 and Office2016 in managed_installs? If so, you are telling Munki that both Office2011 and Office2016 must be installed.

When running the Managed Software Center from the terminal, I see the following errors for my 10.10 clients and same errors for 10.9 but replacing 2011 with 2016.  Each time MSC runs it adds a new entry in the local logs.

• Rejected item Microsoft Office 2011, version 14.1.0 with maximum os version required 10.9.5. Our OS version is 10.10.5.
• Could not process item Microsoft Office 2011 for install. No pkginfo found in catalogs: prod
• Rejected item Microsoft Office 2011 Update, version 14.6.2 with maximum os version required 10.9.5. Our OS version is 10.10.5.
• Could not process item Microsoft Office 2011 Update for install. No pkginfo found in catalogs: prod

The errors were inconsequential (save for the log files filling up) at first as I expected this to be a side effect of the rejected software. But now we're using MunkiReport-PHP for reporting and I'm concerned that valid errors and warnings will be lost in the sea of the above errors causing admins to ignore the feature due to the "false positives".

Anyone else experiencing this and can explain how they resolved it?  Maybe I've configured min/max wrong or can suppress errors if there is a rule associated?

This is a perfect use-case for conditional_items.

https://github.com/munki/munki/wiki/Conditional-Items

[rp...@ussa.org]

Hi Greg,

Thanks for the reply.

They are indeed both managed_installs.

I've used conditions for other items such as excluding laptops by hostname, but when you are talking differentiating min/max OS versions, would this mean that I will have to have a manifest for each OS?

Ron

[Gregory Neagle]

On May 3, 2016, at 4:41 PM, rp...@ussa.org wrote:

Hi Greg,

Thanks for the reply.

They are indeed both managed_installs.

I've used conditions for other items such as excluding laptops by hostname, but when you are talking differentiating min/max OS versions, would this mean that I will have to have a manifest for each OS?

No.

<key>conditional_items</key>

<array>

    <dict>

        <key>condition</key>

        <string>os_vers_minor &lt; 10</string>

        <key>managed_installs</key>

        <array>

            <string>Office2011</string>

        </array>

    </dict>

    <dict>

        <key>condition</key>

        <string>os_vers_minor &gt; 9</string>

        <key>managed_installs</key>

        <array>

            <string>Office2016</string>

        </array>

        <key>managed_uninstalls</key>

        <array>

            <string>Office2011</string>

        </array>

    </dict>

</array>

or similar.

Ron

On Tuesday, May 3, 2016 at 3:22:24 PM UTC-6, Gregory Neagle wrote:

On May 3, 2016, at 2:19 PM, rp...@ussa.org wrote:

Hi All,

We've deployed munki to clients with Mac OS 10.9 and 10.10.  We push Microsoft Office 2011 and 2016 to these clients and I've created minimum and maximum OS versions for each based on Microsoft's requirements.

Does this mean your manifests have both Office2011 and Office2016 in managed_installs? If so, you are telling Munki that both Office2011 and Office2016 must be installed.

When running the Managed Software Center from the terminal, I see the following errors for my 10.10 clients and same errors for 10.9 but replacing 2011 with 2016.  Each time MSC runs it adds a new entry in the local logs.

• Rejected item Microsoft Office 2011, version 14.1.0 with maximum os version required 10.9.5. Our OS version is 10.10.5.
• Could not process item Microsoft Office 2011 for install. No pkginfo found in catalogs: prod
• Rejected item Microsoft Office 2011 Update, version 14.6.2 with maximum os version required 10.9.5. Our OS version is 10.10.5.
• Could not process item Microsoft Office 2011 Update for install. No pkginfo found in catalogs: prod

The errors were inconsequential (save for the log files filling up) at first as I expected this to be a side effect of the rejected software. But now we're using MunkiReport-PHP for reporting and I'm concerned that valid errors and warnings will be lost in the sea of the above errors causing admins to ignore the feature due to the "false positives".

Anyone else experiencing this and can explain how they resolved it?  Maybe I've configured min/max wrong or can suppress errors if there is a rule associated?

This is a perfect use-case for conditional_items.

https://github.com/munki/munki/wiki/Conditional-Items

Thanks for any feedback.

Ron

--
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/c8eede50-4a31-4b79-bec0-89716adf80e9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[rp...@ussa.org]

Thank you for the quick replies Greg, that worked like a charm.