GoogleChrome.pkg not installing properly

[ralvarezOES]

Hi all,

Starting a few weeks ago, our Google Chrome pkg has been failing.  It's strange, it's a simple policy, it's been working for years.  I even created a new policy and downloaded the newest package from Google.  The policy log says it's installed successfully on the MacBook.  It even logs an appropriate amount of time in the policy log.  But the app does not get added to the application folder.  Anyone have an ideas or ways to diagnose this?

[AJPinto]

What happens if you run the package manually?

As far as what to check, I would start with /var/log/install.log and /var/log/jamf.log. 

[junjishimazaki]

Is there a reason why you are packaging Google Chrome instead of scripting the download/installation? I'd suggest you script it. You can use Installomator: https://github.com/Installomator/Installomator

[ralvarezOES]

When I install the package manually, it works.  That is a good point about scripting it.  I'll work on that instead.  then I won't have the issue of having to update the package.  Thanks.

[junjishimazaki]

It's a pretty simple script. Once you add the script to Jamf, in the policy itself, you add the script and in the parameter value section you pass the name of app you are installing. Since you are trying to install Google Chrome, it's add googlechrome to the parameter value.

[Mattdjerome]

I'm going to ditto what junjishimazaki says. I quit packaging about 6 years ago and fuly switched to installomator. it works every time. First run it in debug mode and see how it performs. Then fully implement. You can also do Jamf App Installers if you don't mind that workflow.

[os-tech_r828]

I was also about to suggest Jamf App installers. I'm still learning to get used to using them, too, but it's been working out so far.

[ralvarezOES]

BTW, we setup Installomater and it's fantastic.  Super easy too.