CrashPlan's uninstall script goes through some elegant dances to determine whether the package was installed as admin in root libraries or whether it was installed in the local user's libraries. Note: we were so frustrated that we used a bit of a brute force approach to finding/removing files. We were running CrashPlan client v5.4.1 on Mac OS 10.12.x - 10.14.x In the end, we sat down and parsed through the uninstall.sh (in our installation, it was located at: /Library/Application Support/CrashPlan/Uninstall.app/Contents/Resources/uninstall.sh) file that the Uninstall.app package seems to use, and found that there were only a handful of actual removal commands that needed to be called to seemingly wipe this out. All attempts to remove it via script seemed to fail in some way or another (either not doing anything, leaving leftover cruft, erroring out because of permissions issues, or failing on locked files).CrashPlan wouldn't uninstall unless you manually clicked through the uninstall app at /Library/Application Support/CrashPlan/uninstall.We recently decided to get rid of CrashPlan ProE, and came here looking for solutions to the same issues:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |