Skip to main content
Question

Uninstallation of Nexthink through JAMF

  • June 19, 2023
  • 3 replies
  • 131 views
Asifahmed
Forum|alt.badge.img+9

Hello All,

 

I was looking for a solution to uninstall Nexthink collector from mac device, if I run the uninstaller extracting from .dmg file which contains 4 .pkg it says 

uninstaller” can’t be opened because the identity of the developer cannot be confirmed.

 

Should I run rm -rf /Library/Application\\ Support/Nexthink and rm -rf /Library/Application\\ Support/NexthinkVersions  or do we have a better solution on this?

    3 replies

    sdagley
    Forum|alt.badge.img+25
    • sdagley
    • Jamf Heroes
    • June 20, 2023

    @Asifahmed The `uninstaller` script on the NexThink .dmg has multiple extended attributes attached:

    com.apple.FinderInfo 32B com.apple.ResourceFork 104K com.apple.cs.CodeDirectory 135B com.apple.cs.CodeRequirements 224B com.apple.cs.CodeRequirements-1 171B com.apple.cs.CodeSignature 8.9K com.apple.macl 72B

    If you simply package that script with Composer for deployment to a target Mac those attributes will be lost. I'd recommend you try the following approach:

    • Compress the uninstaller script into a .zip file
    • Create a Composer package containing the .zip'ed uninstaller script
    • Add a postinstall script that extracts the uninstaller script from the .zip and executes it

    (Or you could use Packages to create a .pkg containing the uninstaller script with the options set to retain the extended attributes )

    Asifahmed
    Forum|alt.badge.img+9
    • Asifahmed
    • Author
    • Contributor
    • June 20, 2023

    @Asifahmed The `uninstaller` script on the NexThink .dmg has multiple extended attributes attached:

    com.apple.FinderInfo 32B com.apple.ResourceFork 104K com.apple.cs.CodeDirectory 135B com.apple.cs.CodeRequirements 224B com.apple.cs.CodeRequirements-1 171B com.apple.cs.CodeSignature 8.9K com.apple.macl 72B

    If you simply package that script with Composer for deployment to a target Mac those attributes will be lost. I'd recommend you try the following approach:

    • Compress the uninstaller script into a .zip file
    • Create a Composer package containing the .zip'ed uninstaller script
    • Add a postinstall script that extracts the uninstaller script from the .zip and executes it

    (Or you could use Packages to create a .pkg containing the uninstaller script with the options set to retain the extended attributes )


    I am not understanding what you are saying on this, but I did in different way to implement the way Nexthink site mentioned.

    I uploaded the .dmg in CDP, I created a policy and added this .dmg file with action cache, then I took help of hdiutil attach -nobrowse -noautoopen /Library/Application\\ Support/Jamf/Waiting Room/Nexthink DMG file ; /Volumes/nexthink Collector/ uninstaller 

     

    and it worked, it just uninstall the Nexthink from Mac but it cant remove the entry from Nexthink console.

    Any idea if we can remove the entry from Nexthink console after uninstallation of Nexthink collector from Mac?

    pete_c
    Forum|alt.badge.img+16
    • pete_c
    • Honored Contributor
    • June 20, 2023

    I am not understanding what you are saying on this, but I did in different way to implement the way Nexthink site mentioned.

    I uploaded the .dmg in CDP, I created a policy and added this .dmg file with action cache, then I took help of hdiutil attach -nobrowse -noautoopen /Library/Application\\ Support/Jamf/Waiting Room/Nexthink DMG file ; /Volumes/nexthink Collector/ uninstaller 

     

    and it worked, it just uninstall the Nexthink from Mac but it cant remove the entry from Nexthink console.

    Any idea if we can remove the entry from Nexthink console after uninstallation of Nexthink collector from Mac?


    Nexthink will automatically remove a device that has been inactive for more than 90 days. You can open a support request to make a change to that value; I don't know whether they can remove a single device upon request.

    Terms & ConditionsCookie settingsAccessibility statement