Enabling and Disabling Disk Encryption Manager in the Managed Antivirus Protection Policy

Disk Encryption Manager is enabled and disabled via the MAV-BD Protection Policy.

How to Enable Disk Encryption Manager in the MAV-BD Protection Policy

Once logged into the N-sight RMM dashboard:

  1. Select Settings > Managed Antivirus > Protection Policy
  2. Either create a New policy or Edit an existing one
  3. In the policy dialog, select Disk Encryption Manager in the left-pane
  4. By default, Disk Encryption Manager is disabled, tick the Enable Disk Encryption Manager tick box

  5. An advisory warning appears, read through this so you fully understand the action being taken and then click Enable disk encryption

  6. A new section for Trusted Platform Chip Module will appear in the policy. If required, click to tick the Prompt user for PIN during pre-boot. This is the configuration recommended by Microsoft as per their advice: BitLocker Security FAQ

  7. If you have created a new policy, the remaining settings for the other sections can be configured by following Bitdefender Engine - Protection Policies
  8. Once you have completed the policy configuration, click Save to save the configuration and close the dialog

How to disable Disk Encryption Manager in the MAV-BD Protection Policy with or without Decrypting

  1. Select Settings > Managed Antivirus > Protection Policy
  2. Either double-click the target policy or highlight it and select Edit
  3. In the policy dialog, select Disk Encryption Manager in the left-pane
  4. Untick the Enable Disk Encryption Manager tick box

  5. An advisory warning appears, read through this so you fully understand the action being taken and then click Confirm

  6. A new section for Decrypt Devices will appear in the policy
    1. Tick the Decrypt hard drives option if required. All devices configured with this policy will be set to decrypt and uninstall Disk Encryption Manager when the policy is saved
    2. Leave Decrypt hard drives unticked to disable Disk Encryption Manager and leave the devices encrypted. Control of BitLocker is returned to the device, with its encryption settings set as they were when Disk Encryption Manager was installed. Ensure that the Recovery Key Report has be run and saved securely for these devices. See Disk Encryption Manager Reporting for details

  7. Click Save to save the configuration and close the dialog

Disabling Disk Encryption Manager in the MAV-BDProtection Policy is the only point when the option to decrypt a device is given. As such, care must be taken to ensure only the target devices are using the policy in which Disk Encryption Manager is being disabled. Confirm that there are no other devices, clients or sites using the policy as these will also have Disk Encryption Manager disabled and, if selected, the devices will decrypt. As long as the device remains in the N-sight RMM Dashboard, the Recovery Key information remains available via the Recovery Key Report. If the device is removed from the N-sight RMM dashboard, the last known valid Recovery Key is retained for 90 days only.

Swapping Policies and Moving Devices

Depending on changes to your customer’s requirements and protection needs, you may have to apply a new MAV-BD Protection Policy to their devices or even move devices between Clients and Sites.

Care should be taken when performing these actions, as the devices with policies inherited from the Site or Client level will update to match the MAV-BD Disk Encryption Manager configuration as set in the new policy's settings. The policy will not change when it was set at the individual device level.

  • When you move devices or swap the Protection Policy from where Disk Encryption Manager is disabled to where it is enabled, all devices will install Disk Encryption Manager and encrypt the device
  • When you move devices or swap the Protection Policy from where Disk Encryption Manager is enabled to where it is disabled, all devices will uninstall Disk Encryption Manager and leave the devices encrypted

Where the MAV-BD Protection Policy was set at the individual device level, moving the device to another Client or Site will not change the Protection Policy.