6/12/2023 0 Comments Defender atp mac' > /Library/LaunchDaemons/.plistĬorrected script with all the other input: ' > /Library/LaunchDaemons/.plistĮcho "Creating Daily Quick Scan plist /Library/LaunchDaemons/.plist" # Create the Defender scheduled scan Launch Daemons using a scriptĮcho "Creating Weekly Full Scan plist /Library/LaunchDaemons/.plist" # Defender-CreateScheduledScanLaunchDaemons.bash Here's the LaunchDaemon script: #!/bin/bash You can check that they are loaded in the command line by typing sudo launchctl list | grep Ĭheck the man page for other commands for launchctl such as load, unload, start, stop etcĪctually I looked at my current workflow and it's all done with scripts. A similar one to do a full scan once a week .plist is below It does a quick scan at 3pm (1500) daily. I made this one called .plist and placed it in /Library/LaunchDaemons with the correct permissions - 644 and ownership root:wheel. I'm just editing this post as I found a couple of issues with the plists I shared Sudo launchctl list shows LastExitStatus = 0 as well but day in and day out the quick scan does not run at 12:30pm as I would like. So I do a sudo launchctl list and find that the PID is "-" and the Status is "0" which sounds like it was executed successfully. Perhaps I am missing something simple someone could point out. I am pretty green to the LaunchDaemons work but I have checked existing ones we utilize and even had one generated to verify i wasn't making a syntax error. Right now I am trying to schedule Quick Scans to occur every day at 12:30pm but am having a bit of an issue. We have recently started testing and deploying MDATP to select people in our org.
0 Comments
Leave a Reply. |