Skip to main content
added 27 characters in body
Source Link
bmike
  • 241.3k
  • 80
  • 433
  • 958

The instructions to remove the framework just require you to have a local admin password.

/usr/local/bin/jamf removeFramework

This will remove all the things that the tool installed (apps, profiles, certificates) and then remove the management framework. You do not want to do this if you have FileVault keys not in your direct control or don't have a good backup or you are trying to circumvent a proper installation.

Since this can break things, you might check with the team that runs JAMF for the organization your friend belongs. Removing the framework doesn't have to break anything if the IT department put light controls in place.

Checking with their team means they can also remotely run the uninstall or tell you the things this will delete, but you certainly don't need to throw away the hardware (or throw it here - I know several people that would use it happily).

The instructions to remove the framework just require you to have a local admin password.

/usr/local/bin/jamf removeFramework

This will remove all the things that the tool installed (apps, profiles, certificates) and then remove the management framework. You do not want to do this if you have FileVault keys or don't have a good backup or you are trying to circumvent a proper installation.

Since this can break things, you might check with the team that runs JAMF for the organization your friend belongs. Removing the framework doesn't have to break anything if the IT department put light controls in place.

Checking with their team means they can also remotely run the uninstall or tell you the things this will delete, but you certainly don't need to throw away the hardware (or throw it here - I know several people that would use it happily).

The instructions to remove the framework just require you to have a local admin password.

/usr/local/bin/jamf removeFramework

This will remove all the things that the tool installed (apps, profiles, certificates) and then remove the management framework. You do not want to do this if you have FileVault keys not in your direct control or don't have a good backup or you are trying to circumvent a proper installation.

Since this can break things, you might check with the team that runs JAMF for the organization your friend belongs. Removing the framework doesn't have to break anything if the IT department put light controls in place.

Checking with their team means they can also remotely run the uninstall or tell you the things this will delete, but you certainly don't need to throw away the hardware (or throw it here - I know several people that would use it happily).

Source Link
bmike
  • 241.3k
  • 80
  • 433
  • 958

The instructions to remove the framework just require you to have a local admin password.

/usr/local/bin/jamf removeFramework

This will remove all the things that the tool installed (apps, profiles, certificates) and then remove the management framework. You do not want to do this if you have FileVault keys or don't have a good backup or you are trying to circumvent a proper installation.

Since this can break things, you might check with the team that runs JAMF for the organization your friend belongs. Removing the framework doesn't have to break anything if the IT department put light controls in place.

Checking with their team means they can also remotely run the uninstall or tell you the things this will delete, but you certainly don't need to throw away the hardware (or throw it here - I know several people that would use it happily).