The Deployment with a different MDM system article left a lot to be desired. Also, neither article made mention of the other as a complete "story" for managing the client.ĭon't forget to grant Terminal.app permissions in the Security & Privacy preferences to validate the ist in one of the two Managed Preferences locations.
Initially, I found it odd that the Defender client would be reading TWO separate preference domains. As such, you'll usually find the payloadType relates to a ist file somewhere in /Library/Managed Preferences (or `~/Library/Managed Preferences). This specific profile looks geared towards licensing and linking the Defender ATP to your specific tenant in the threat protection cloud for telemetry.įor anyone uninitiated, the payloadType in a configuration profile is essentially the key that tells macOS to which preference domain the key-value pairs apply. This "MDM Deployment" specific article only mentions the profile downloaded as part of the Onboarding package. The second article, JAMF-based deployment for Microsoft Defender ATP for Mac, referenced a payloadType of. In other words, it controls what changes can be made in the UI if opened by the end-user. These preferences seem related to the UI and various configuration settings. The first article, Set Preferences for Microsoft Defender ATP referenced a payloadType of. The initial problem I found was some confusion generated by Microsoft's documentation. We recently published this guide to the EUC Samples GitHub Repository. Once I was able to parse through the Jamf/InTune documentation, we were able to put together some guidance. We got it working, but it came down to 2 issues: conflicting documentation and Jamf/inTune specific templates. I had a few folks recently approach me on the MacAdmins slack asking for help with deploying Microsoft Defender ATP for Mac.
0 kommentar(er)
