mac microsoft autoupdate freezing on installing

#MAC MICROSOFT AUTOUPDATE FREEZING ON INSTALLING HOW TO#
#MAC MICROSOFT AUTOUPDATE FREEZING ON INSTALLING UPDATE#
#MAC MICROSOFT AUTOUPDATE FREEZING ON INSTALLING FULL#
#MAC MICROSOFT AUTOUPDATE FREEZING ON INSTALLING PRO#

If you deploy this Kernel extension to your machines BEFORE you deploy the MDATP application, users will not get this warning. In the meantime Apple will give a user facing “Legacy System Extension” warning.

#MAC MICROSOFT AUTOUPDATE FREEZING ON INSTALLING UPDATE#

Microsoft are preparing a Microsoft Defender ATP for macOS update that leverages system extensions instead of kernel extensions. The complete configuration file with payload is to be found at github MDATP Kernel Extensions Update frequence is set to 180 minutes (default is 720), 9. keep the check for updates button enabled, 8. I have set the configuration in my file to 4.

#MAC MICROSOFT AUTOUPDATE FREEZING ON INSTALLING PRO#

This also applies to Office Pro Plus and other Microsoft applications in addition to MDATP. This will allow you to control what rings your machines are on and also the frequence of checking for updates. Microsoft AutoUpdate (MAU) ConfigurationĮven though this setting is optional, I really recommend you configure these settings. The same story here, you will find the configuration file on same page as above, and the file is available on github. This one is a bit simpler to to, as Microsoft has published the config of this file for us (tcc.xml ) on, and I have also published this in XML format for you do download on github.

#MAC MICROSOFT AUTOUPDATE FREEZING ON INSTALLING HOW TO#

We will return back to how to deploy this settings a bit later on the blogpost. I have published the complete configuration file on github. This concludes the configuration of the settingsfile. diagnostic level is set to required and 7. Under Cloud Service Settings we define how to handle cloud delivered protection, diagnostics level and automatic sample submissions. not allowing users to define their own settings for threat types. restricted users from allowing threats or removing threats from quarantine, threat type settings set to 37.block unwanted applications and 43.

excluded “/var/log/system.log”, 27.disabled users from creating their own exceptions, 30/31. I have configured this with the following: 3. The keys is antivirusEngine, cloudService, edr and userInterface.

#MAC MICROSOFT AUTOUPDATE FREEZING ON INSTALLING FULL#

In the full configuration file you have keys and you have underlying settings. I recommend you to start by downloading a recommended configuration file from, at the same place you will also find a full configuration version.

Threat Type settings with actions to take.

Exclusion Merge to restrict local users from adding their own exclusions.

Some of the things we would like to configure is the following: The configuration profile is basically a XML file containing all your configuration settings for Defender ATP.

This is part of the on-boarding package and is required for MDATP to work.

If you want to enforce update ring or change behavior this must be configured.

To update MDATP on macOS this program is used.

Microsoft AutoUpdate (MAU) Configuration (optional).

We need to white-list Defender ATP and Autoupdate for displaying notifications in UI on macOS Catalina.

On macOS Catalina we need to allow MDATP to have full access to all files on the machine with a specific configuration.

This is where we decide how MDATP is behaving on your devices like enabling real-time protection.

I recommend the following configurations to be deployed before deploying the Defender ATP application to our machines: To make MDATP work as we want it to we need to have some additional settings in addition to the ones in the on-boarding package. Required configuration for MDATP to work on macOS Catalina But before we go into the details of this let us have a look of what else is needed. We have kext.xml which is for configuring kernel extensions on your macOS devices, and the WindowsDefenderATPOnboarding.xml that contains your tenant on-boarding information. Delete the jamf folder as we are using Intune to do this. In this folder you find a folder for Jamf and a folder for Intune. You will now get a file called WindowsDefenderATPOnboardingPackage.zip in your Downloads folder.

Mac microsoft autoupdate freezing on installing