You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just starting looking into using this, and unfortunately it seems to no longer work.
I tested it on a couple machines going from Monterey > Ventura 13.3.1.
Computers have NoMAD 1.3.0 and NoMADLogin 1.4.0 + NoMAD-LaunchAgent.
Initially when I run a policy with the script attached in Jamf Pro, I was getting:
Script result: cat: /var/db/.loginwindow_authdb_bkp.xml: No such file or directory
/Library/Application Support/JAMF/tmp/NoMADLogin_UpgradeHook.sh: line 40: /var/db/.loginwindow_authdb_bkp.xml: No such file or directory
rm: /var/db/.loginwindow_authdb_bkp.xml: No such file or directory
So I thought maybe it has to run locally on the computer, no big deal. Package to copy the script to the computer, and then one liner to trigger it. When running locally the script exits with 0.
Had it run locally on a couple computers, exit code 0, looks fine. Did an erase-install upgrade on both, and they came back to the regular login screen instead of our NoMAD Login screen.
I saw some guy in #MacAdmins Slack say he's used it on Monterey > Ventura, so it seems like it is/was possible? I'm not sure how else I would trigger the script or run it. Saw another guy say he never got it to work.
I realize it's been three years since you touched this, so not expecting anything. There are still a fair amount of NoMAD users out there.
The text was updated successfully, but these errors were encountered:
Hello,
I just starting looking into using this, and unfortunately it seems to no longer work.
I tested it on a couple machines going from Monterey > Ventura 13.3.1.
Computers have NoMAD 1.3.0 and NoMADLogin 1.4.0 + NoMAD-LaunchAgent.
Initially when I run a policy with the script attached in Jamf Pro, I was getting:
So I thought maybe it has to run locally on the computer, no big deal. Package to copy the script to the computer, and then one liner to trigger it. When running locally the script exits with 0.
Had it run locally on a couple computers, exit code 0, looks fine. Did an erase-install upgrade on both, and they came back to the regular login screen instead of our NoMAD Login screen.
I saw some guy in #MacAdmins Slack say he's used it on Monterey > Ventura, so it seems like it is/was possible? I'm not sure how else I would trigger the script or run it. Saw another guy say he never got it to work.
I realize it's been three years since you touched this, so not expecting anything. There are still a fair amount of NoMAD users out there.
The text was updated successfully, but these errors were encountered: