We deploy the same config for defender, it mostly works. My hunch is,
where it doesn't something else has gone wrong with the Mac processing
config profiles. If you are a jamf customer, ask them to run a report
looking for RemoveProfile loops, you ca...
In more detail;If the Mac is still checking in with jamf then you can
create a policy to run the command I mentioned above, you can even force
a logout.Create a new policy - give it a name like lock login session,
set trigger to Recurring Check-in, F...
Unfortunatly I have no experience of any of these apps outside of
Defender... What I will say is if the app is closing on launch, there
may be a crash log or an entry in the system log to try and find the
cause.
If the mac has a local account, by definition it isn't using your domain
services, so unfortunately yes you would need to lock the machine or use
code: "pwpolicy -u $username disableuser"
If it isn't showing in the menu bar then the one of two ways it can
start on login must not be in-place...It either needs a launchagent in
/Library/LaunchAgentsor it needs a login item, say generated with code
like: "/usr/bin/osascript <
