SolarWinds RMM: Managed Antivirus – Bitdefender v6 GA Upgrade Advance Notice

Advance Notice: Upgrade to RMM Managed Antivirus – Bitdefender (MAV-BD) v6.6.4.68 and v6.4.2.79 scheduled to begin Wednesday, September 26, 2018.

Please be advised we will be publishing an upgrade to all MAV-BD devices starting on Wednesday, September 26, 2018.  This will be a staggered upgrade with the APAC region on September 26th,  EU region on September 27th and US region on September 28th. This is a major version upgrade from MAV-BD v5 to MAV-BD v6 and a reboot will be required.  The Release Candidate (RC) option to “Enable Bitdefender v6” from the Managed Antivirus menu has been removed.  New installations of MAV-BD will continue to install MAV-BD v6.  We will post another update once this upgrade has been published.

The MAV-BD v6.6 and v6.4 update introduces a split version for RMM users, based on the operating system of the device.  Post the v6 upgrade, MAV-BD installations will receive the version corresponding to their operating system.

  • MAV-BD v6.6.x for Windows Modern Operating Systems: designed for Windows 7/Windows Server 2008 R2 and higher, this version no longer installs on legacy operating systems.
  • MAV-BD v6.4.x for Windows Legacy Operating Systems: designed for Windows XP and Windows Vista families, including corresponding embedded and server versions, this version does not install on modern operating systems.

MAV-BD Version 6.6.4.68

Enhancements

  • New installations automatically receive the latest version of Advanced Threat Control (ATC 4.0)
    • Under-the-hood improvements deliver better proactive heuristics and allow faster response to new threats or false positives
    • Better detection of script-based and PowerShell attacks
    • ATC4 groups related processes and evaluates actions for improved efficacy
    • Improved mechanism for detecting potential Process Doppelgänging attacks
    • Added support for the system variable %AllUsersProfile% to specify paths for product modules

The following issues were fixed in this build:

  • An issue that prevented quarantined files from being restored on network paths when using the local user interface
  • Advanced Threat Control causing a critical error (BSOD) when using CodeSoft
  • An issue with Advanced Threat Control that prevented CCH Prosystems Tax from being installed on endpoints
  • Fixed an issue that caused explorer.exe system errors with the message “txmlutil.dll is missing” on some servers.
  • Fixed an incompatibility issue with MsSenseS.exe that was causing the product folder bdcore_tmp to grow in size during on-demand scanning, until the disk space was consumed.
  • Fixed an issue that caused Bitdefender Endpoint Protected Service to stop in particular conditions.

MAV-BD Version 6.4.2.79

Enhancements

  • Improved mechanism for detecting potential Process Doppelgänging attacks
  • Added support for the system variable %AllUsersProfile% to specify paths for product modules

The following issues were fixed in this build: 

  • An issue that prevented quarantined files from being restored on network paths when using the local user interface

Handling MAV-BD Reboots

  • A reboot is expected with this upgrade.  A reboot notification is shown as a blue dot within the North Pane of the RMM Dashboard.
  • Reboots can be automatically enabled for the upgrade process by selecting an option in the MAV-BD policy. 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 in 5 minutes.

reboot

The version of the MAV-BD agent and engine can be found in the Managed Antivirus Check or the Managed Antivirus Protection Report in the RMM Dashboard.  To see the version of the engine and agent within the Managed Antivirus Check, navigate to the South Pane of the device and select the “More Information” link.  The agent and engine version can be seen on the “Check Info” tab.  To see the version deployed across all devices, run the Managed Antivirus Protection Report.  Ensure that the Agent Version and Engine Version columns are selected from the Column drop down.

 

This entry was posted in N-sight. Bookmark the permalink.