Notice: Use only 10.15.0 Jamf Remote after upgrading to 10.15.0

[cbrewer]

I discovered the hard way that using a version of Jamf Remote older than 10.15.0 to connect to a Mac with the binary already upgraded to 10.15.0 will break the Jamf binary on that computer.

It's always best practice to use the current version of Jamf Remote but this time it's a bit more critical.

When the binary breaks, that computer will no longer run policies or check in so it's fairly impactful. Running the jamf binary on a broken machine results in "/usr/local/bin/jamf: cannot execute binary file".

The fix? Use Jamf Remote 10.15.0 and set the preferences to install CLI apps using SCP. Do an inventory update on the broken computer and it should reinstall the binary.

[cbrewer]

Product Issue: PI-007483

Related Feature Request:
https://www.jamf.com/jamf-nation/feature-requests/8910/jamf-remote-version-check

[ooshnoo]

Thank you for this. Was racking my brain over this the past couple days.

@cbrewer What do you mean by: Use Jamf Remote 10.15.0 and set the preferences to install CLI apps using SCP. Do an inventory update on the broken computer and it should reinstall the binary.

[cbrewer]

[Chris_Hafner]

... wow.

[tomt]

What @Chris_Hafner said...

[jhalvorson]

Thanks for the fix @cbrewer

[jlimonesatwork]

Thank you for this! I too was racking my brain over this the past couple days.

[CasperSally]

Think we're running into this as well. thanks for posting this. wish the old remote versions wouldn't work.

[cbrewer]

Seeing this issue again while using a 10.17.0 version of Jamf Remote on a 10.17.1 client.

Jamf - Please don't ship another version of Jamf Remote until you add some version checking.