I was asked to deploy the keyboard shortcut “command options control +
L” to lock the screen. I tried running Composer but i didn't see
anything useful... unless i accidentally missed it, that was also my
last ditch effort to created it since i know ...
Yeah... that is the same thing that the Jamf support team told me. It's
not always ideal since you have to redo your variables and stuff, update
the script the policy is using and what not... It's just messy if you're
testing or deploying a new scrip...
** I have been using Jamf for close to 7 years now and this is a new
issue for me... Also wanted to add that I was able to save the script
when I removed the Custom Funtions and the API calls for that script.
I am currently seeing the same issues... My guess is that there is some
sort of Script validation process that happens on jamf... Try saving
chucks of code at a time to find the problematic code.. For me custom
functions and API calls. This seems to ...
So far no direct "clashes" with jamf unless you try removing it. The
uninstaller doesn't restore the device permissions so Jamf and other
admin accounts end up broken. Even for troubleshooting purposes removing
it is a tedious and painful task.
Honestly I just install the entire pkg and just selectively uninstall
what i don't want to keep... seemed easier at the time. #!/bin/sh
#Uninstall Web Security Module
/opt/cisco/anyconnect/bin/websecurity_uninstall.sh # #Uninstall Network