How to remove configuration Profiles from client?

Depends on if they were applied to the User or the Device. Have you rebooted or recon'd since?

Depends on if they were applied to the User or the Device. Have you rebooted or recon'd since?

They were applied to the device (energy settings, login screen, etc).

When you updated the Profile in the JSS, did you click on Distribute to All or Distribute to Newly Assigned Computers Only? Also have you rebooted the computers in question?

Distribute to all computers.

We see the same thing. You can update. You can add. You can never remove.

We've been trying to find a way to remove a configuration profile that we recently deployed but decided to remove from the Macs. The profile was deployed using Casper (wrapped PKG with script to install), and some during imaging time (same PKG).

The usual command does not work for us, we get an error:

sudo profiles -R -F /tmp/profile.mobileconfig

Wierd, if we log on to the Mac, we are able to remove, we are prompted for admin rights when doing so.

Any idea why an installed profile could be so much trouble to uninstall?

The profile installs 3 certs and 1 Wi-Fi config.

Any input appreciated.

Don

Which version of Casper are you guys running? I finally got our 8.62 to work with config profiles and found that it automatically sends a remove command when you "unscope" a computer from the profile.

To confirm, are any of you that are experiencing this issue seeing any of your removal commands stuck in "pending" status in JSS -> Inventory -> Management History?

Configuration profile in "Pending" status?
https://jamfnation.jamfsoftware.com/discussion.html?id=4493

I've seen that if we issue a sudo jamf enroll on an already enrolled Mac, it will REMOVE the MDM profile from the Mac. We have to issue the same command again to get the MDM profile back. Happens every time, without fail.

you could unscope the computer or user from the scope tab, then update on client side with "sudo jamf removemdmprofile, sudo jamf mdm" or wait till it updates by itself automactically. then you will find the profile disappeared.

@donmontalvo -F requires the original install file to be present before you can remove it.
Use something like

WIFI_PROFILES=$(Profiles -Lv | awk '/attribute: name:/ && /PROFILENAME/,/attribute: profileIdentifier:/' | awk '/attribute: profileIdentifier:/ {print $4}')

This will return the identifier for the profile PROFILENAME from the list of profiles.
Then try something like

profiles -R -p "$WIFI_PROFILE"

To remove it based on the identifier.
It's also possible the identifier for a certain profile is identicle on all machines in which case you may be able to reference it directly.

Hi Samuel, not sure which post you're responding to. Our command included the path to the profile which was present. This thread is over two years old, but I do remember that updating JSS fixed the problem for us. Apologies for not circling back with an update. Thanks, Don

Sorry must have been tired at the end of the day... didn't notice the post date, just saw the thread near the top.

LOL no worries that's a great bit of info you posted that'll help folks. Much appreciated. :)