As mentioned in our previous post, we have now resumed our MAV-BD upgrade from v5 to v6. This is a phased rollout that is slowly deploying across regions and will carry into next week.
Please remember that this is a major MAV-BD engine upgrade and does require a reboot. MAV-BD engine upgrades can also be delayed or scheduled off hours on evenings/weekends by changing the “Force engine upgrades after” option within the “General” tab of the MAV policy. Ensure the delay and reboot settings in your policies are set accordingly for your customers.
Delaying Engine Upgrades
- MAV-BD Engine upgrades can be delayed by up to 10 days in the Managed Antivirus protection policy. Upgrades can also be delayed for weekends and evening hours. Please refer to RMM’s help file for more detail on this feature.
- Reboots can be automatically enabled for the upgrade process by selecting an option in the MAV policy under the “Installation Settings” tab. Automatic reboots occur within 5 minutes of taking the update. Please ensure this option is disabled if you do not want your end user machine to automatically reboot. If the automatic reboot option is not enabled, the reboot will be displayed as a blue dot within the North Pane of the RMM Dashboard, indicating that the machine needs a reboot to complete the installation. Reboot the machine at your earliest convenience.
Determining the version on a device:
The version of the MAV agent, as well as the MAV engine version, can be seen in 2 places – by looking at the Managed Antivirus Check (Bitdefender), or by running the Managed Antivirus Protection Report.
To see the version of the agent within the MAV check, navigate to the South Pane of the device and find the Managed Antivirus Check – Bitdefender and select the “More Information” link. To see across devices, run the Managed Antivirus Protection Report under Reports > Managed Antivirus > Antivirus Protection Report. Ensure that the Agent Version and Engine Version columns are selected from the Column drop down.