# Mac Configuration Enhanced Workflow

Apple introduced macOS BigSur in November 2020 and as the newest version of Apple's operating system, it brought about many upgrades in terms of security and privacy. Because of these upgrades, changes have been introduced in [Mac Management](https://www.manageengine.com/products/desktop-central/mac-management.html).

## Table of Contents

- [How does this impact you?](#how-does-this-impact-you)
- [How can you overcome this?](#how-can-you-overcome-this)
- [What steps should you undertake?](#what-steps-should-you-undertake)
- [What happens when your MDM Profile dependent Configurations are Moved to Trash?](#what-happens-when-your-mdm-profile-dependent-configurations-are-moved-to-trash)

## How does this impact you?

There are certain Mac Configurations which will become **non-functional** (till the build 10.0.648), if the target machines contain BigSur.

For now, System preferences Mac based User configurations will function in target machines with macOS Catalina or below only.

## How can you overcome this?

Endpoint Central has introduced MDM Profile. By doing so, certain Mac Configuration workflows have been enhanced and this will circumvent any problems in Mac Management. The computer based configurations that require the introduction of [MDM Profile](https://www.manageengine.com/products/desktop-central/help/mac_configurations/mdm-profile-configuration-for-mac.html) are as follows -

1. AirPrint
2. App Notifications
3. Background Service Management
4. Custom Configuration
5. Energy Saver
6. Extensible SSO
7. Firewall
8. Fonts
9. Gatekeeper
10. Global HTTP Proxy
11. Login Window
12. Login Items
13. Passcode
14. Restrictions
15. PPPC
16. Per-App VPN
17. System Extensions
18. System Preferences
19. VPN
20. Web Content Filter
21. Wi-Fi

## What steps should you undertake?

The steps you must take vary in the context of whether your target machine possesses macOS BigSur or whether MDM Profile has been installed on the machine or not. The table below will guide you for any of the different cases based on your network.

**Note:** MDM Profile dependent configurations that were deployed before the build 10.0.648 will only not function in target machines with BigSur.

| macOS Bigsur & above versions? | MDM Profile? | Steps to do |
|---|---|---|
| Not present | Not installed | After configuring the required prerequisites, MDM Profile needs to be installed on the Mac Computers. Prior to this, any MDM profile dependent configuration **will not** be deployed. Learn more [about MDM Profile and its prerequisites](https://www.manageengine.com/products/desktop-central/help/mac_configurations/mdm-profile-configuration-for-mac.html). |
| Not present | Installed | If the end user has not approved MDM Profile, they have to install it manually through [the notification window](https://www.manageengine.com/products/desktop-central/help/mac_configurations/mdm-profile-configuration-for-mac.html). |
| Present | Not Installed | After configuring the required prerequisites, MDM Profile needs to be installed on the Mac Computers. Prior to this, any MDM profile dependent configuration **will not** be deployed. Learn more [about MDM Profile and its prerequisites](https://www.manageengine.com/products/desktop-central/help/mac_configurations/mdm-profile-configuration-for-mac.html). **Note:** MDM profile dependent configurations that are deployed before build 10.0.648 can be reused for target machines running on any macOS **except Bigsur**. |
| Present | Installed | If the end user has not approved MDM Profile, they have to install it manually through [the notification window](https://www.manageengine.com/products/desktop-central/help/mac_configurations/mdm-profile-configuration-for-mac.html). |

## What happens when your MDM Profile dependent Configurations are Moved to Trash?

If you perform the action **"Move to trash"** from the **Configurations** tab for the relevant MDM Profile Support configuration, then the configuration will be revoked from the agent machine.

**Note**: MDM Profile Supported Configurations **will not** be moved to trash automatically by configuring **"Configuration Settings"**