How to uninstall jamf software or prevent the daemon from running
I've used my MacOS Sierra machine to access a client's intranet, but in order to gain access, I had to install jamf.
My current version of jamf is:
$ jamf -version
version=9.101.4-t1507816971
Today, there was a dialog on my computer insisting that I had to upgrade my OS, without an obvious way to dismiss it:
That's fine, I discovered in Activity Monitor that the jamfHelper
was responsible and I could easily kill this.
Edit: The dialog is back after an hour or so after freezing the jamf
daemon & jamfAgent
processes.
Aside: I'm running the latest security patched version of MacOS Sierra and don't have time for a clean build or to test an upgrade to High Sierra right now.
I just want out. It's my machine, but has this software on it.
🚩 How do I remove it without taking out a bunch of stuff which I still need?
I'm concerned about running sudo jamf -removeFramework
as I just don't know what it does.
Killing the jamf*
precesses just launches new versions of them.
Here's what's currently running after some recent kill
s:
$ ps -ef | grep jamf
0 68775 1 0 11:34am ?? 0:00.33 /usr/local/jamf/bin/jamf launchDaemon -enforceRestrictions -monitorNetworkStateChanges
0 68852 1 0 11:34am ?? 0:00.08 /usr/local/jamf/bin/jamfAgent
501 68906 68221 0 11:35am ttys019 0:00.00 grep jamf
🚩 Is there an easy way to prevent the jamf daemon from launching?
macos-sierra
add a comment |
I've used my MacOS Sierra machine to access a client's intranet, but in order to gain access, I had to install jamf.
My current version of jamf is:
$ jamf -version
version=9.101.4-t1507816971
Today, there was a dialog on my computer insisting that I had to upgrade my OS, without an obvious way to dismiss it:
That's fine, I discovered in Activity Monitor that the jamfHelper
was responsible and I could easily kill this.
Edit: The dialog is back after an hour or so after freezing the jamf
daemon & jamfAgent
processes.
Aside: I'm running the latest security patched version of MacOS Sierra and don't have time for a clean build or to test an upgrade to High Sierra right now.
I just want out. It's my machine, but has this software on it.
🚩 How do I remove it without taking out a bunch of stuff which I still need?
I'm concerned about running sudo jamf -removeFramework
as I just don't know what it does.
Killing the jamf*
precesses just launches new versions of them.
Here's what's currently running after some recent kill
s:
$ ps -ef | grep jamf
0 68775 1 0 11:34am ?? 0:00.33 /usr/local/jamf/bin/jamf launchDaemon -enforceRestrictions -monitorNetworkStateChanges
0 68852 1 0 11:34am ?? 0:00.08 /usr/local/jamf/bin/jamfAgent
501 68906 68221 0 11:35am ttys019 0:00.00 grep jamf
🚩 Is there an easy way to prevent the jamf daemon from launching?
macos-sierra
1
Why not run the uninstall command as you're already running the rest of their code? Nevertheless, have you tried freezing the processes instead of killing them?
– dsstorefile1
Mar 2 '18 at 11:58
Sounds good. How do I freeze the processes though? Is thatkill -STOP ${PID}
?
– dvdsmpsn
Mar 2 '18 at 12:07
1
Yes, try that and see if jamf is smart enough to thaw itself.
– dsstorefile1
Mar 2 '18 at 12:09
No 😥 the upgrade modal is back again. The daemon & jamfAgent are still frozen though, so I think something else is running
– dvdsmpsn
Mar 2 '18 at 13:23
related: jamf.com/jamf-nation/discussions/27335/…
– Cœur
Sep 28 '18 at 9:22
add a comment |
I've used my MacOS Sierra machine to access a client's intranet, but in order to gain access, I had to install jamf.
My current version of jamf is:
$ jamf -version
version=9.101.4-t1507816971
Today, there was a dialog on my computer insisting that I had to upgrade my OS, without an obvious way to dismiss it:
That's fine, I discovered in Activity Monitor that the jamfHelper
was responsible and I could easily kill this.
Edit: The dialog is back after an hour or so after freezing the jamf
daemon & jamfAgent
processes.
Aside: I'm running the latest security patched version of MacOS Sierra and don't have time for a clean build or to test an upgrade to High Sierra right now.
I just want out. It's my machine, but has this software on it.
🚩 How do I remove it without taking out a bunch of stuff which I still need?
I'm concerned about running sudo jamf -removeFramework
as I just don't know what it does.
Killing the jamf*
precesses just launches new versions of them.
Here's what's currently running after some recent kill
s:
$ ps -ef | grep jamf
0 68775 1 0 11:34am ?? 0:00.33 /usr/local/jamf/bin/jamf launchDaemon -enforceRestrictions -monitorNetworkStateChanges
0 68852 1 0 11:34am ?? 0:00.08 /usr/local/jamf/bin/jamfAgent
501 68906 68221 0 11:35am ttys019 0:00.00 grep jamf
🚩 Is there an easy way to prevent the jamf daemon from launching?
macos-sierra
I've used my MacOS Sierra machine to access a client's intranet, but in order to gain access, I had to install jamf.
My current version of jamf is:
$ jamf -version
version=9.101.4-t1507816971
Today, there was a dialog on my computer insisting that I had to upgrade my OS, without an obvious way to dismiss it:
That's fine, I discovered in Activity Monitor that the jamfHelper
was responsible and I could easily kill this.
Edit: The dialog is back after an hour or so after freezing the jamf
daemon & jamfAgent
processes.
Aside: I'm running the latest security patched version of MacOS Sierra and don't have time for a clean build or to test an upgrade to High Sierra right now.
I just want out. It's my machine, but has this software on it.
🚩 How do I remove it without taking out a bunch of stuff which I still need?
I'm concerned about running sudo jamf -removeFramework
as I just don't know what it does.
Killing the jamf*
precesses just launches new versions of them.
Here's what's currently running after some recent kill
s:
$ ps -ef | grep jamf
0 68775 1 0 11:34am ?? 0:00.33 /usr/local/jamf/bin/jamf launchDaemon -enforceRestrictions -monitorNetworkStateChanges
0 68852 1 0 11:34am ?? 0:00.08 /usr/local/jamf/bin/jamfAgent
501 68906 68221 0 11:35am ttys019 0:00.00 grep jamf
🚩 Is there an easy way to prevent the jamf daemon from launching?
macos-sierra
macos-sierra
edited Oct 1 '18 at 9:41
dvdsmpsn
asked Mar 2 '18 at 11:54
dvdsmpsndvdsmpsn
29139
29139
1
Why not run the uninstall command as you're already running the rest of their code? Nevertheless, have you tried freezing the processes instead of killing them?
– dsstorefile1
Mar 2 '18 at 11:58
Sounds good. How do I freeze the processes though? Is thatkill -STOP ${PID}
?
– dvdsmpsn
Mar 2 '18 at 12:07
1
Yes, try that and see if jamf is smart enough to thaw itself.
– dsstorefile1
Mar 2 '18 at 12:09
No 😥 the upgrade modal is back again. The daemon & jamfAgent are still frozen though, so I think something else is running
– dvdsmpsn
Mar 2 '18 at 13:23
related: jamf.com/jamf-nation/discussions/27335/…
– Cœur
Sep 28 '18 at 9:22
add a comment |
1
Why not run the uninstall command as you're already running the rest of their code? Nevertheless, have you tried freezing the processes instead of killing them?
– dsstorefile1
Mar 2 '18 at 11:58
Sounds good. How do I freeze the processes though? Is thatkill -STOP ${PID}
?
– dvdsmpsn
Mar 2 '18 at 12:07
1
Yes, try that and see if jamf is smart enough to thaw itself.
– dsstorefile1
Mar 2 '18 at 12:09
No 😥 the upgrade modal is back again. The daemon & jamfAgent are still frozen though, so I think something else is running
– dvdsmpsn
Mar 2 '18 at 13:23
related: jamf.com/jamf-nation/discussions/27335/…
– Cœur
Sep 28 '18 at 9:22
1
1
Why not run the uninstall command as you're already running the rest of their code? Nevertheless, have you tried freezing the processes instead of killing them?
– dsstorefile1
Mar 2 '18 at 11:58
Why not run the uninstall command as you're already running the rest of their code? Nevertheless, have you tried freezing the processes instead of killing them?
– dsstorefile1
Mar 2 '18 at 11:58
Sounds good. How do I freeze the processes though? Is that
kill -STOP ${PID}
?– dvdsmpsn
Mar 2 '18 at 12:07
Sounds good. How do I freeze the processes though? Is that
kill -STOP ${PID}
?– dvdsmpsn
Mar 2 '18 at 12:07
1
1
Yes, try that and see if jamf is smart enough to thaw itself.
– dsstorefile1
Mar 2 '18 at 12:09
Yes, try that and see if jamf is smart enough to thaw itself.
– dsstorefile1
Mar 2 '18 at 12:09
No 😥 the upgrade modal is back again. The daemon & jamfAgent are still frozen though, so I think something else is running
– dvdsmpsn
Mar 2 '18 at 13:23
No 😥 the upgrade modal is back again. The daemon & jamfAgent are still frozen though, so I think something else is running
– dvdsmpsn
Mar 2 '18 at 13:23
related: jamf.com/jamf-nation/discussions/27335/…
– Cœur
Sep 28 '18 at 9:22
related: jamf.com/jamf-nation/discussions/27335/…
– Cœur
Sep 28 '18 at 9:22
add a comment |
1 Answer
1
active
oldest
votes
You enrolled your personal device in a client's management system? I would be very careful - many companies have policies about enrolling non-corporate owned devices in their MDMs. Some even have EULA language that states if you enroll a personal device in their MDM that they will consider the device their property. Unless there's a BYOD program, this is common.
If you remove the JAMF framework via sudo jamf removeFramework
any profiles that were installed by the MDM will be uninstalled. Chances are that your access to the client network is controlled via profile. I would recommend contacting the client's Helpdesk, Mac support, or MDM support immediately. It's entirely possible they'll be willing to provide you with the means to get on the network without enrolling in the MDM system.
Or not, some places have strict controls over just who and what device can connect to their network. If this is required by your contract to have network access they should either accommodate your personal device or issue you a corporate device.
By unenrolling (removing the Framework) you won't be subject to the policies from their MDM. I'm still somewhat in shock that enrolling personal devices would ever be OK as there are usually policies that install software with corporate licenses.
There was little choice at the time - I needed access to something which required that. The "easy" answer was backup, wipe and start again. Not a quick win, but a clean slate is best.
– dvdsmpsn
May 3 '18 at 19:57
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1299814%2fhow-to-uninstall-jamf-software-or-prevent-the-daemon-from-running%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You enrolled your personal device in a client's management system? I would be very careful - many companies have policies about enrolling non-corporate owned devices in their MDMs. Some even have EULA language that states if you enroll a personal device in their MDM that they will consider the device their property. Unless there's a BYOD program, this is common.
If you remove the JAMF framework via sudo jamf removeFramework
any profiles that were installed by the MDM will be uninstalled. Chances are that your access to the client network is controlled via profile. I would recommend contacting the client's Helpdesk, Mac support, or MDM support immediately. It's entirely possible they'll be willing to provide you with the means to get on the network without enrolling in the MDM system.
Or not, some places have strict controls over just who and what device can connect to their network. If this is required by your contract to have network access they should either accommodate your personal device or issue you a corporate device.
By unenrolling (removing the Framework) you won't be subject to the policies from their MDM. I'm still somewhat in shock that enrolling personal devices would ever be OK as there are usually policies that install software with corporate licenses.
There was little choice at the time - I needed access to something which required that. The "easy" answer was backup, wipe and start again. Not a quick win, but a clean slate is best.
– dvdsmpsn
May 3 '18 at 19:57
add a comment |
You enrolled your personal device in a client's management system? I would be very careful - many companies have policies about enrolling non-corporate owned devices in their MDMs. Some even have EULA language that states if you enroll a personal device in their MDM that they will consider the device their property. Unless there's a BYOD program, this is common.
If you remove the JAMF framework via sudo jamf removeFramework
any profiles that were installed by the MDM will be uninstalled. Chances are that your access to the client network is controlled via profile. I would recommend contacting the client's Helpdesk, Mac support, or MDM support immediately. It's entirely possible they'll be willing to provide you with the means to get on the network without enrolling in the MDM system.
Or not, some places have strict controls over just who and what device can connect to their network. If this is required by your contract to have network access they should either accommodate your personal device or issue you a corporate device.
By unenrolling (removing the Framework) you won't be subject to the policies from their MDM. I'm still somewhat in shock that enrolling personal devices would ever be OK as there are usually policies that install software with corporate licenses.
There was little choice at the time - I needed access to something which required that. The "easy" answer was backup, wipe and start again. Not a quick win, but a clean slate is best.
– dvdsmpsn
May 3 '18 at 19:57
add a comment |
You enrolled your personal device in a client's management system? I would be very careful - many companies have policies about enrolling non-corporate owned devices in their MDMs. Some even have EULA language that states if you enroll a personal device in their MDM that they will consider the device their property. Unless there's a BYOD program, this is common.
If you remove the JAMF framework via sudo jamf removeFramework
any profiles that were installed by the MDM will be uninstalled. Chances are that your access to the client network is controlled via profile. I would recommend contacting the client's Helpdesk, Mac support, or MDM support immediately. It's entirely possible they'll be willing to provide you with the means to get on the network without enrolling in the MDM system.
Or not, some places have strict controls over just who and what device can connect to their network. If this is required by your contract to have network access they should either accommodate your personal device or issue you a corporate device.
By unenrolling (removing the Framework) you won't be subject to the policies from their MDM. I'm still somewhat in shock that enrolling personal devices would ever be OK as there are usually policies that install software with corporate licenses.
You enrolled your personal device in a client's management system? I would be very careful - many companies have policies about enrolling non-corporate owned devices in their MDMs. Some even have EULA language that states if you enroll a personal device in their MDM that they will consider the device their property. Unless there's a BYOD program, this is common.
If you remove the JAMF framework via sudo jamf removeFramework
any profiles that were installed by the MDM will be uninstalled. Chances are that your access to the client network is controlled via profile. I would recommend contacting the client's Helpdesk, Mac support, or MDM support immediately. It's entirely possible they'll be willing to provide you with the means to get on the network without enrolling in the MDM system.
Or not, some places have strict controls over just who and what device can connect to their network. If this is required by your contract to have network access they should either accommodate your personal device or issue you a corporate device.
By unenrolling (removing the Framework) you won't be subject to the policies from their MDM. I'm still somewhat in shock that enrolling personal devices would ever be OK as there are usually policies that install software with corporate licenses.
answered May 3 '18 at 13:38
MrCleanMrClean
1
1
There was little choice at the time - I needed access to something which required that. The "easy" answer was backup, wipe and start again. Not a quick win, but a clean slate is best.
– dvdsmpsn
May 3 '18 at 19:57
add a comment |
There was little choice at the time - I needed access to something which required that. The "easy" answer was backup, wipe and start again. Not a quick win, but a clean slate is best.
– dvdsmpsn
May 3 '18 at 19:57
There was little choice at the time - I needed access to something which required that. The "easy" answer was backup, wipe and start again. Not a quick win, but a clean slate is best.
– dvdsmpsn
May 3 '18 at 19:57
There was little choice at the time - I needed access to something which required that. The "easy" answer was backup, wipe and start again. Not a quick win, but a clean slate is best.
– dvdsmpsn
May 3 '18 at 19:57
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1299814%2fhow-to-uninstall-jamf-software-or-prevent-the-daemon-from-running%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Why not run the uninstall command as you're already running the rest of their code? Nevertheless, have you tried freezing the processes instead of killing them?
– dsstorefile1
Mar 2 '18 at 11:58
Sounds good. How do I freeze the processes though? Is that
kill -STOP ${PID}
?– dvdsmpsn
Mar 2 '18 at 12:07
1
Yes, try that and see if jamf is smart enough to thaw itself.
– dsstorefile1
Mar 2 '18 at 12:09
No 😥 the upgrade modal is back again. The daemon & jamfAgent are still frozen though, so I think something else is running
– dvdsmpsn
Mar 2 '18 at 13:23
related: jamf.com/jamf-nation/discussions/27335/…
– Cœur
Sep 28 '18 at 9:22