Jamf uninstall help

mbuckner
Contributor

I’m trying to uninstall a package using the jamf commandline tool, but every time I try I get a “Uninstall Not Allowed – The JSS did not return information to uninstall this package” error. I think it has to do with the package id. Anybody know how to make this work?

Thanks!
Mark

6 REPLIES 6

tlarkin
Honored Contributor

You must first index the package in Casper Admin, then Casper can
uninstall it

jarednichols
Honored Contributor

Sounds to me like it needs to be indexed with Casper Admin first. The
"information to uninstall" is generally created during that indexing.

j
-- Jared F. Nichols
Desktop Engineer, Client Services
Information Services Department
MIT Lincoln Laboratory
244 Wood Street
Lexington, Massachusetts 02420
781.981.5436

Not applicable

Hi
Do you have the package enable for uninstall under Casper admin?

Carmelo Lopez Portilla

ITS EMBL Heidelberg
Tel. +49 (0) 6221 387 8444
Fax +49 (0) 6221 387 8517
email: lopez at embl.de

mbuckner
Contributor

That's the funny thing - I did index it in casper admin first. I can
uninstall it from a casper policy just fine. What I couldn't do was
uninstall it from the command line. The command line asks for an 'id', and
no matter what id I put in, it gives the same response.

ernstcs
Contributor III

Oh, well go into your JSS web, go to Casper Admin under Management, click on
the package in your list.

When viewing the package details look at your URL, the end will say
package=XXXX

That's the ID, use that. =)

Craig E

ernstcs
Contributor III

My last point to this is why do you want to do an uninstall using the
commandline uninstall anyway?

It's a pain because the package, if ever changed, gets a new ID and thus
requires you to modify the script or whatever that's sending the command.

I'm all for using a script if necessary, (I'm trying to have these types of
actions just show up in Self Service now) but I'd refer that back to a
manually triggered policy where I have the policy configured to do the
uninstall so it's easy to change out packages in the web interface and be
done.

/usr/sbin/jamf policy -trigger <customTriggerName>

That never has to change and then you can add anything else to that policy
you want to happen afterwards, like a recon perhaps.

Just a thought. There may a logical reason to do what you're doing, but I'm
not sure what that is.

Craig E

P.S. Can you get my email address unblocked from your SPAM filter. =)