managed_installs item keeps installing

[nate]

i have a simple manifest with one item included (http://pastebin.com/
76XZ0zZL).

the clients pick it up, install properly, then install it again on the
next managed software update run.

here's the catalog: http://pastebin.com/vnqkE1zq

what am i missing?

server and client have the latest svn version as of this morning
installed.

thanks,

nate

[Nate]

I'd start by making an installs item (/usr/local/munki/makepkginfo -f) for it instead of relying on the package receipts.  See where that takes you.

Nate

--
You received this message because you are subscribed to the Google Groups "munki-dev" group.
To post to this group, send email to munk...@googlegroups.com.
To unsubscribe from this group, send email to munki-dev+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/munki-dev?hl=en.

[Sable C.]

>
> here's the catalog: http://pastebin.com/vnqkE1zq

There is an extra <array> in line 10. That happened to me too.

Sable

[Greg Neagle]

On Feb 24, 2011, at 10:56 AM, nate wrote:

> i have a simple manifest with one item included (http://pastebin.com/
> 76XZ0zZL).
>
> the clients pick it up, install properly, then install it again on the
> next managed software update run.
>
> here's the catalog: http://pastebin.com/vnqkE1zq
>
> what am i missing?

Accurate "installs" or "receipts" in the pkginfo. If there is no "installs" list, munki uses the "receipts" list if it exists.
In either case, if any item in the list is missing or older than the item as described in the pkginfo, munki considers the item as not installed, and attempts to install it.

In this particular case, the Filemaker Pro 11 metapackage does not actually install all of the packages in the receipts list; but rather a subset of them.

Easiest workaround is to create an installs key and add it to the pkginfo:

/usr/local/munki/makepkginfo -f </path/to/Filemaker Pro 11.app>

This way munki checks only for the existence of the actual Filemaker Pro app itself.

-Greg

[Sable C.]

DOH! I mistyped. Not in line 10.

12 through 14 are out of order:

<key>managed_installs</key>
<string>FileMaker Pro</string>
<array>
</array>

Should be <array><string>Filemaker</string></array>

Sable

[Greg Neagle]

Of course, the FileMaker Pro 11 package has other issues as well, and will need its post-* scripts modified in order to install from a root process...

-Greg

[nate]

thanks, all.

do i add/replace the relevant chunk in the app's pkginfo file with the
output of makepkginfo here?

i basically wrapped the mpkg in a dmg and added it via munkiimport, as
usual.

i'll check the wiki for any details on fmp post/preflight gotchas.

filemaker should have died long ago, but unfortunately, people still
want the stuff installed. bane of my existence…

[Nate]

You can add an installs section and munki will use that over the receipts.  No need to remove the receipts though, they might be handy later for documentation or troubleshooting.

Nate

[Bernstein, Gary Robert]

You should be able to find some info that I posted in the archives about Filemaker. I went round and round with it. I would give you the short information, but I am running out to a meeting.

Looking at my server real quickly, I see that I ended up repackaging Filemaker and using an installs key.

-Gary

> --
> You received this message because you are subscribed to the Google Groups "munki-dev" group.
> To post to this group, send email to munk...@googlegroups.com.
> To unsubscribe from this group, send email to munki-dev+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/munki-dev?hl=en.
>

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
-- "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]

Worse -- if you remove the receipts, munki can no longer uninstall the item. 

Sent from my iPhone

[nate]

add the installs section (the output of makepkginfo) to the pkgsinfo
file for the app installer, correct?

just trying to clarify here.

[Nate]

No, the app itself.  The installs item tells munki what the installer has installed.

Nate

[nate]

i ended up punting and repackaging it in the interest of saving some
time.

adding the installs block seemed to work in testing but not when
rolling it out to machines with an older version of fmp already
installed. the version is clearly stated in the installs section, but
the app name is the same. not sure what the issue was/is, but it
basically didn't work as i'd hoped in this case.

thanks for your help, all.

[Nate]

On a machine that already has it installed, run makepkginfo -f fmp.app and compare that to your new ones.  They must be the same for it to not even install. (Or something else is going on).

Nate

[Sable C.]

Filemaker is incredibly slick and powerful software :D I'm glad to
see you deploying it.

Did correcting the manifest work for you?

It was on the pastebin like this:

<key>managed_installs</key>
<string>FileMaker Pro</string>
<array>
</array>

Should be:

<key>managed_installs</key>
<array>
<string>FileMaker Pro</string>
</array>

[nate]

i'll have to try again someday. even after correcting the manifest
syntax, i don't think it worked as expected.

they had fmp 5.5 (!) installed across the board already. installing
fmp 11 via munki worked but then repeated the install on every managed
software update run.

for many reasons, i didn't spend the time to get the munki deployment
with the stock installer working, unfortunately.

- they're not a regular client
- they're paying for my time @ $150/hour, so i just needed to get
something working
- they don't have any other regular change/package management, central
server, or even IT support in place
- this was more of a one-off deployment for a very small group of maybe 15 hosts
- etc.

anyway, thanks for all your help.

[S. Cantus]

FWIW, I support a couple of small shops. One client is in downtown Los Angeles and when we upgraded them to FM 11, it was worth the time for me to go to each machine - about 10 - just to make sure that they were all updated and working with the printers.

They are all Mac and only need laptop attention once or twice a year. It's the FM database that they keep modifying that keeps them calling me!

Sable

[jo...@orensteins.com]

I am having an issue where the Fuse and VeraCrypt keep installing every time I update.  Can some one show this newbie what I did wrong?

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<dict>

<key>OnDemand</key>

<false/>

<key>_metadata</key>

<dict>

<key>created_by</key>

<string>admin</string>

<key>creation_date</key>

<date>2017-09-14T23:12:37Z</date>

<key>munki_version</key>

<string>3.0.3.3352</string>

<key>os_version</key>

<string>10.12.6</string>

</dict>

<key>allow_untrusted</key>

<true/>

<key>autoremove</key>

<false/>

<key>catalogs</key>

<array>

<string>testing</string>

</array>

<key>category</key>

<string>Security</string>

<key>description</key>

<string>Needed for VeraCrypt</string>

<key>developer</key>

<string></string>

<key>display_name</key>

<string>FUSE</string>

<key>installed_size</key>

<integer>8800</integer>

<key>installer_item_hash</key>

<string>19f4fda0f1258c688b9839155b60ab1f7b24b09f2fa01d58c3a4b6b5c43c215a</string>

<key>installer_item_location</key>

<string>apps/fuse/FUSE for macOS 3.6.3.pkg</string>

<key>installer_item_size</key>

<integer>5142</integer>

<key>minimum_os_version</key>

<string>10.5.0</string>

<key>name</key>

<string>FUSE for macOS</string>

<key>receipts</key>

<array/>

<key>suppress_bundle_relocation</key>

<true/>

<key>unattended_install</key>

<false/>

<key>unattended_uninstall</key>

<false/>

<key>uninstall_method</key>

<string>removepackages</string>

<key>uninstallable</key>

<false/>

<key>version</key>

<string>3.6.3</string>

</dict>

</plist>

THANKS

[Mr. Alan Siu]

It doesn't appear that you have any receipts or an installs array in your pkginfo? This is a generally good guide for your issue:

https://github.com/munki/munki/wiki/How-Munki-Decides-What-Needs-To-Be-Installed

Alan Siu

Client Systems Analyst

St. Ignatius College Preparatory

--
Find related discussion groups here:
https://github.com/munki/munki/wiki/Discussion-Group
---

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+unsubscribe@googlegroups.com.

To post to this group, send email to munk...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[jo...@orensteins.com]

I have three apps that keep installing every time I update in Managed Software Center.  I am totally new to this and have got most of this working but i am stuck on these 3 apps

_________

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<dict>

<key>OnDemand</key>

<true/>

<key>_metadata</key>

<dict>

<key>created_by</key>

<string>admin</string>

<key>creation_date</key>

<date>2017-09-15T01:10:41Z</date>

<key>munki_version</key>

<string>3.0.3.3352</string>

<key>os_version</key>

<string>10.12.6</string>

</dict>

<key>allow_untrusted</key>

<true/>

<key>apple_item</key>

<false/>

<key>autoremove</key>

<false/>

<key>catalogs</key>

<array>

<string>testing</string>

</array>

<key>category</key>

<string>Quicktime</string>

<key>description</key>

<string>Older Quicktime that can be upgraded to Pro</string>

<key>developer</key>

<string>Apple</string>

<key>display_name</key>

<string>Quicktime 7</string>

<key>installed_size</key>

<integer>32914</integer>

<key>installer_item_hash</key>

<string>c088f8742fd7f28b02ddd43a837275ddbec5b5444c03147738c4e7fa4fcb4811</string>

<key>installer_item_location</key>

<string>apps/quicktime/QuickTimePlayer7.6.6_SnowLeopard-7.6.6.1.1249367152.pkg</string>

<key>installer_item_size</key>

<integer>10823</integer>

<key>minimum_os_version</key>

<string>10.5.0</string>

<key>name</key>

<string>QuickTimePlayer7</string>

<key>receipts</key>

<array/>

<key>suppress_bundle_relocation</key>

<false/>

<key>unattended_install</key>

<true/>

<key>unattended_uninstall</key>

<false/>

<key>uninstall_method</key>

<string>removepackages</string>

<key>uninstallable</key>

<true/>

<key>version</key>

<string>7.6.6.1.1249367152</string>

</dict>

</plist>

____________________

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<dict>

<key>OnDemand</key>

<true/>

<key>_metadata</key>

<dict>

<key>created_by</key>

<string>admin</string>

<key>creation_date</key>

<date>2017-09-15T17:12:48Z</date>

<key>munki_version</key>

<string>3.0.3.3352</string>

<key>os_version</key>

<string>10.12.6</string>

</dict>

<key>allow_untrusted</key>

<true/>

<key>apple_item</key>

<true/>

<key>autoremove</key>

<false/>

<key>catalogs</key>

<array>

<string>testing</string>

</array>

<key>category</key>

<string>Apple</string>

<key>description</key>

<string>ARD Client</string>

<key>developer</key>

<string>Apple</string>

<key>display_name</key>

<string>Remote Desktop Client</string>

<key>installed_size</key>

<integer>14102</integer>

<key>installer_item_hash</key>

<string>c09f2a99374f2927a919c49ffca16cd68223969a24dfab5016ed772aeb712bbb</string>

<key>installer_item_location</key>

<string>apps/apple/RemoteDesktopClient-3.9.3.0.1.1497319096.pkg</string>

<key>installer_item_size</key>

<integer>9084</integer>

<key>minimum_os_version</key>

<string>10.5.0</string>

<key>name</key>

<string>RemoteDesktopClient</string>

<key>receipts</key>

<array>

<dict>

<key>installed_size</key>

<integer>14102</integer>

<key>packageid</key>

<string>com.apple.pkg.RemoteDesktopClient</string>

<key>version</key>

<string>3.9.3.0.1.1497319096</string>

</dict>

</array>

<key>unattended_install</key>

<true/>

<key>unattended_uninstall</key>

<false/>

<key>uninstall_method</key>

<string>removepackages</string>

<key>uninstallable</key>

<true/>

<key>version</key>

<string>3.9.3.0.1.1497319096</string>

</dict>

</plist>

_______________

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<dict>

<key>OnDemand</key>

<true/>

<key>_metadata</key>

<dict>

<key>created_by</key>

<string>admin</string>

<key>creation_date</key>

<date>2017-09-15T00:19:30Z</date>

<key>munki_version</key>

<string>3.0.3.3352</string>

<key>os_version</key>

<string>10.12.6</string>

</dict>

<key>allow_untrusted</key>

<true/>

<key>autoremove</key>

<false/>

<key>catalogs</key>

<array>

<string>testing</string>

</array>

<key>category</key>

<string>Adobe</string>

<key>description</key>

<string>PDF editor</string>

<key>developer</key>

<string>Adobe</string>

<key>display_name</key>

<string>AdobeCC2017 (Acrobat DC) [MAC]</string>

<key>installer_item_hash</key>

<string>9032981d9f6b6611f0ecd4b3b9fdd1ba2155b3afbd24e960b87aad37cf490b49</string>

<key>installer_item_location</key>

<string>apps/adobe/AdobeCC2017 Acrobat DC_Install-17.009.20044.dmg</string>

<key>installer_item_size</key>

<integer>1101729</integer>

<key>installer_type</key>

<string>AdobeCCPInstaller</string>

<key>minimum_os_version</key>

<string>10.6.8</string>

<key>name</key>

<string>AdobeCC2017(AcrobatDC)[MAC]</string>

<key>suppress_bundle_relocation</key>

<false/>

<key>unattended_install</key>

<true/>

<key>unattended_uninstall</key>

<false/>

<key>uninstallable</key>

<true/>

<key>version</key>

<string>17.009.20044</string>

</dict>

</plist>

On Thursday, February 24, 2011 at 10:56:25 AM UTC-8, nate wrote:

[Nick McSpadden]

Alan Siu gave you the answer, and I strongly recommend you read the wiki link he provided.  All three of those are marked as "OnDemand" = True, which means they will install every single time Munki runs. I don't think that is at all what you want.

--

Find related discussion groups here:
https://github.com/munki/munki/wiki/Discussion-Group
---
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+unsubscribe@googlegroups.com.
To post to this group, send email to munk...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

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

[Mr. Alan Siu]

Hi, Josh. I'd responded to your first message yesterday, but the same advice applies here:

It doesn't appear that you have any receipts or an installs array in your pkginfo? This is a generally good guide for your issue:

https://github.com/munki/munki/wiki/How-Munki-Decides-What-Needs-To-Be-Installed

P.S. In the future, you may want to post questions like this to Munki-Discuss instead of Munki-Dev.

Alan Siu

Client Systems Analyst

St. Ignatius College Preparatory

On Fri, Sep 15, 2017 at 10:26 AM, <jo...@orensteins.com> wrote:

--

[jo...@orensteins.com]

Thank you all for the help! This is by far the best community I have ever been a part of!

To unsubscribe from this group and stop receiving emails from it, send an email to munki-dev+...@googlegroups.com.

[Brian LaShomb]

The naming of “OnDemand” is tricky if you think about how that means “Self Service” in other fields (like Cable DVRs). Could see OnDemand meaning “optional install” to some.

As we use optional installs much more frequently than persistent installs, a recipe level setting for having items show up as as “optional install” would be useful, with the less used OnDemand setting relegated to the manifest.

[Gregory Neagle]

On Sep 20, 2017, at 5:08 AM, Brian LaShomb <br...@lashomb.com> wrote:

The naming of “OnDemand” is tricky if you think about how that means “Self Service” in other fields (like Cable DVRs). Could see OnDemand meaning “optional install” to some.

Sure. Naming things so everyone understands is hard. Documentation can help. The wiki is one set of Munki documentation. You do need to understand what you are doing to effectively use Munki.

If the community can agree on a replacement name for "OnDemand" we could implement it, but of course as not to break anyone we'd need to continue supporting OnDemand for a very long time...

As we use optional installs much more frequently than persistent installs, a recipe level setting

? You must be thinking of autopkg -- Munki does not have recipes.

for having items show up as as “optional install” would be useful, with the less used OnDemand setting relegated to the manifest.

This seems precisely backwards to me (and since I'm the primary developer, that's really important!).

OnDemand items need to be added to optional_installs anyway: OnDemand is additional information that changes the behavior of an optional install, just as RestartAction changes the behavior of an install, as does blocking_applications.

Any item you import into Munki could be added to managed_installs, managed_uninstalls, managed_updates, or optional_installs. It might even be in managed_installs for some manifests, managed_uninstalls for another set of manifests, and  optional_installs in yet another set of manifests. And of course an imported item might not be in any section of any manifest! It makes no sense (to me, and again that's important!) to store that information in an item's pkginfo.

-Greg

[Mr. Alan Siu]

Just on the naming piece, I actually think OnDemand fits perfectly if you're using a cable/DVR analogy.

When you watch a movie "on demand," you aren't permanently downloading the movie or buying it to keep forever—you're saying "I just want to watch this movie right now." Same deal for Managed Software Center: "I don't want to permanently 'install' this script (or whatever it is)—I just want to run it right now."

Alan Siu

Client Systems Analyst

St. Ignatius College Preparatory

[Brian LaShomb]

You are right, I’m mixing Autopkg and Munki together in my head. And using some questionable logic to boot, as your explanation makes perfect sense in retrospect.