Skip to main content

Hello, I was looking for where to open a ticket for this issue but did not find where to do that.

Maybe some of you will have an idea about what I am doing wrong. We have Jamf Pro cloud version and I have never deployed a pkg and made it run on a user’s machine. The user is one of my bosses and he gave me a link to a DuoDeviceHealth pkg which I was able to download from Duo. I then set a cloud distribution point and uploaded the pkg. In Computer Management – Scripts I pasted the script he supplied.

sudo mkdir -p "/Library/Application Support/Duo/Duo Device Health"

sudo touch "/Library/Application Support/Duo/Duo Device Health/NoAutoLaunchAfterInstall"

sudo /usr/sbin/installer -pkg /path/to/installer/DuoDeviceHealth-3.0.0.0.pkg -target / (This path location is where the PKG file was downloaded on my laptop)

sudo rm "/Library/Application Support/Duo/Duo Device Health/NoAutoLaunchAfterInstall"

I made a policy named DuoDeviceHealth and enabled it and the trigger is Recurring Check in

In Packages the Action is Install

I set the Priority to Before

In Computer management – Check-in it is set to every 5 minutes

Still it has not installed on his laptop

Any help would be appreciated

Latest DUO Device health is v5.3.0.0 (https://duo.com/docs/device-health-notes#duo-device-health-application-for-macos). After download DUO pkg, you can upload it to Jamf cloud directly, then create policy to install it directly. Could you do a capture of your policy? From policy log, can you see target Mac is pending to run?

 

I've never deployed this app, but you normally don't need to script a folder creation and a command to install the pkg if deploying the pkg directly from jamf (it should install if set to in the policy). unless you have repackaged it to deploy the installer to a particular location to run the command.

I don't think you need that script, but that's just a guess. It doesn't seem like it's doing anything other than trying to manually run a package installation from a path. I would just place the package into a policy and push it that way. I think it should work, but for the record, I don't have experience installing Duo, so I may be missing something.

If you find you really need some of the stuff the script is doing, then create a script to run Before your package and one to run as After. In the before script, add this:

#!/bin/zsh

mkdir -p "/Library/Application Support/Duo/Duo Device Health"
touch "/Library/Application Support/Duo/Duo Device Health/NoAutoLaunchAfterInstall"

In the After script, add this:

#!/bin/zsh

rm "/Library/Application Support/Duo/Duo Device Health/NoAutoLaunchAfterInstall"

You could also just add the 'rm' command above to a Files and Processes payload, into the "Execute Command" field instead of having a separate script to do it.

I needed to deploy a certificate before deploying the application. Take a look at the following.

https://help.duo.com/s/article/6403?language=en_US

Latest DUO Device health is v5.3.0.0 (https://duo.com/docs/device-health-notes#duo-device-health-application-for-macos). After download DUO pkg, you can upload it to Jamf cloud directly, then create policy to install it directly. Could you do a capture of your policy? From policy log, can you see target Mac is pending to run?

 


kai_wang1 I did download and then upload v5.3.0.0 to Jamf. The logs for the target machine show it ran 10 times but failed. There was an error in the script. It did find the pkg, downloaded and verified but the install failed.

Executing Policy DuoDeviceHealth
Downloading DuoDeviceHealth-5.3.0.0.pkg...
Downloading https://our cloud /DuoDeviceHealth-5.3.0.0.pkg...
Verifying package integrity...
Installing DuoDeviceHealth...
Installation failed. The installer reported: installer: Package name is Duo Device Health
installer: Installing at base path /
installer: The install failed. (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance. An error occurred while running scripts from the package “DuoDeviceHealth-5.3.0.0.pkg”.)

I've never deployed this app, but you normally don't need to script a folder creation and a command to install the pkg if deploying the pkg directly from jamf (it should install if set to in the policy). unless you have repackaged it to deploy the installer to a particular location to run the command.


SCCM I did upload to our Jamf Cloud and the logs show it is finding it but fails to install

Executing Policy DuoDeviceHealth
Downloading DuoDeviceHealth-5.3.0.0.pkg...
Downloading https://our cloud /DuoDeviceHealth-5.3.0.0.pkg...
Verifying package integrity...
Installing DuoDeviceHealth...
Installation failed. The installer reported: installer: Package name is Duo Device Health
installer: Installing at base path /
installer: The install failed. (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance. An error occurred while running scripts from the package “DuoDeviceHealth-5.3.0.0.pkg”.)

SCCM I did upload to our Jamf Cloud and the logs show it is finding it but fails to install

Executing Policy DuoDeviceHealth
Downloading DuoDeviceHealth-5.3.0.0.pkg...
Downloading https://our cloud /DuoDeviceHealth-5.3.0.0.pkg...
Verifying package integrity...
Installing DuoDeviceHealth...
Installation failed. The installer reported: installer: Package name is Duo Device Health
installer: Installing at base path /
installer: The install failed. (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance. An error occurred while running scripts from the package “DuoDeviceHealth-5.3.0.0.pkg”.)


Also I did remove the script

I don't think you need that script, but that's just a guess. It doesn't seem like it's doing anything other than trying to manually run a package installation from a path. I would just place the package into a policy and push it that way. I think it should work, but for the record, I don't have experience installing Duo, so I may be missing something.

If you find you really need some of the stuff the script is doing, then create a script to run Before your package and one to run as After. In the before script, add this:

#!/bin/zsh

mkdir -p "/Library/Application Support/Duo/Duo Device Health"
touch "/Library/Application Support/Duo/Duo Device Health/NoAutoLaunchAfterInstall"

In the After script, add this:

#!/bin/zsh

rm "/Library/Application Support/Duo/Duo Device Health/NoAutoLaunchAfterInstall"

You could also just add the 'rm' command above to a Files and Processes payload, into the "Execute Command" field instead of having a separate script to do it.


mm2270 I did remove my script and in Files and Processes added the rm line you have but no luck so far, same error log as above

I needed to deploy a certificate before deploying the application. Take a look at the following.

https://help.duo.com/s/article/6403?language=en_US


_gsm I will check this out

kai_wang1 I did download and then upload v5.3.0.0 to Jamf. The logs for the target machine show it ran 10 times but failed. There was an error in the script. It did find the pkg, downloaded and verified but the install failed.

Executing Policy DuoDeviceHealth
Downloading DuoDeviceHealth-5.3.0.0.pkg...
Downloading https://our cloud /DuoDeviceHealth-5.3.0.0.pkg...
Verifying package integrity...
Installing DuoDeviceHealth...
Installation failed. The installer reported: installer: Package name is Duo Device Health
installer: Installing at base path /
installer: The install failed. (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance. An error occurred while running scripts from the package “DuoDeviceHealth-5.3.0.0.pkg”.)


Download pkg from https://duo.com/docs/checksums#macos and upload to your cloud directly (no need any change for the pkg we download).

For cross check issue, you can download pkg to a Mac and try to install it manually to see if you can install it successfully.

 

Also, as _gsm said you need push a cert prior.

kai_wang1 I did download and then upload v5.3.0.0 to Jamf. The logs for the target machine show it ran 10 times but failed. There was an error in the script. It did find the pkg, downloaded and verified but the install failed.

Executing Policy DuoDeviceHealth
Downloading DuoDeviceHealth-5.3.0.0.pkg...
Downloading https://our cloud /DuoDeviceHealth-5.3.0.0.pkg...
Verifying package integrity...
Installing DuoDeviceHealth...
Installation failed. The installer reported: installer: Package name is Duo Device Health
installer: Installing at base path /
installer: The install failed. (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance. An error occurred while running scripts from the package “DuoDeviceHealth-5.3.0.0.pkg”.)


That a generic error ive seen it on other packages which download as zip if downloaded onto a windows machine from a website, rather than on a mac itself then uploaded to jamf. Manually installing those files normally works, just not via jamf.

That a generic error ive seen it on other packages which download as zip if downloaded onto a windows machine from a website, rather than on a mac itself then uploaded to jamf. Manually installing those files normally works, just not via jamf.


From https://duo.com/docs/checksums#macos we can get .pkg directly and upload to Jamf directly.

 

I needed to deploy a certificate before deploying the application. Take a look at the following.

https://help.duo.com/s/article/6403?language=en_US


Thank all of you for the help and advice.
What finally worked was SCCM suggesting using a Mac to download and upload the pkg
Seems like Windows machines can mess up Mac files
Thanks to kai_wang1 for prompting me to check the logs
As mm2270 said I didn't need the script
Also as _gsm suggested I checked the link provided (and used the Mac) to create the cert after giving the sh file execute permission
Pushed out the certificate to the target machines and then added the target machines to the policy
It worked on my test machine and I am hoping on the bosses machine, time will tell

Reply


Terms & ConditionsCookie settings