Release Notes for Endpoint Server Device Control - Apr 11, 2023

Written By Marissa Fegan (Super Administrator)

Updated at April 11th, 2023

Product release information for VIPRE Endpoint Security Server Device Control v50, released on April 11, 2023

What's New

This release provides an update to Device Control to version 50 as part of VIPRE Endpoint Security Server, including several bug fixes. 

VIPRE Recommends

It's critical to keep all software in your environment as up-to-date as possible. New software releases often fix issues with older versions of the product that, unless addressed, could leave you vulnerable. As such, VIPRE recommends updating to the most recent version as soon as possible.

Check the current status of older product versions on the VIPRE Product Lifecycle Matrix to learn when support for specific product versions may end.

 

 

Special Instructions

This Device Control release will be automatically deployed in your environment if:

  • Software updates are enabled within site properties, and
  • Software updates are enabled within the agents' policy

If software updates are disabled within site properties, you will need to manually check for updates for the Console to obtain the new packages. After the console has the updated packages, if software updates are disabled within the agents' policy, you will need to manually check for software updates

To confirm that you have received the Device Control update, in the Console, view the Supplemental software packages. You should see two entries for Device Control, version 50.

To verify your settings or enable software updates, read this Software Update Settings guidance.

System Requirements

Product or Component Minimum Requirement

Management Console (VSS)

OPERATING SYSTEMS

  • Windows Server 2019 (excluding Server Core)
  • Windows Server 2016 (excluding Server Core)
  • Windows Server 2012 (excluding Server Core)
  • Windows Server 2008 SP2 or R2 (excluding Server Core)
  • Windows 10 (32- & 64-bit, all versions)
  • Windows 8.1 (32- & 64-bit)

NOTE: Embedded operating systems are not supported

HARDWARE

  • Dual-core processor or higher
  • 2GB free disk space(up to 20 GB could be required for Endpoint Security versions for caching of patches)
  • 2GB RAM
  • 1024 x 768 monitor resolution

MISCELLANEOUS

  • MDAC 2.6 SP2 or later
  • Microsoft .NET Framework 4.6 (if not already installed, .NET will automatically install during installation)

VIPRE Agent for Windows

OPERATING SYSTEMS

  • Windows Server 2019 (64-bit, excluding Server Core) 
  • Windows Server 2016 (excluding Server Core) 
  • Windows Server 2012 R2 (excluding Server Core) 
  • Windows Server 2008 R2 SP1 (excluding Server Core) 
  • Windows Small Business Server 2011 
  • Windows Small Business Server 2008 †
  • Windows 11 (64-bit)
  • Windows 10 (32- & 64-bit, all versions)
  • Windows 8.1 (32 & 64-bit)
  • Windows 7 SP1 (32- & 64-bit)
  • Windows Vista SP2 (32 & 64-bit) †
  • Windows XP (32-bit) †

† Supported for legacy agent only, not available for Cloud

 HARDWARE

  • Dual-core processor recommended
  • 2GB free disk space
  • 2GB RAM or better recommended

SUPPORTED WEB BROWSERS FOR HTTPS URL PROTECTION

  • Mozilla Firefox v68 or later
  • Google Chrome v72 or later
  • Microsoft Edge v79 or later

SUPPORTED EMAIL APPLICATIONS

  • Microsoft Outlook 2003+
  • SMTP/POP3 (Thunderbird, IncrediMail, Eudora, etc.)
  • SSL supported in Outlook only
VIPRE Agent for Mac

OPERATING SYSTEMS

  • macOS Sierra (10.12)
  • OS X El Capitan (10.11)
  • OS X Yosemite (10.10)
  • OS X Mavericks (10.9)
  • OS X Mountain Lion (10.8)

VIPRE Business Mobile Security Agent

OPERATING SYSTEMS

  • Android 4.1 (Jelly Bean) or later
  • iOS 5.1.1 or later

 

 

Bugs Fixed in this Release

  • VPBAGENT-8782: Volume Shadow Copy was failing when Device Control was enabled
  • VPBAGENT-41131: Synology File Backups were being blocked by Device Control 

Known Issues and Workarounds

This section lists issues that are known at the time of release. In some cases, these are bugs that we are working to resolve with a subsequent release. Other items may be due to causes outside of our control, such as bugs with other vendors' software. In all cases, we have tried to provide a workaround for you to consider should you experience an issue.

If you have questions about a specific issue, please provide the ticket number found below (if applicable) when contacting our Technical Support team.

Issues from Previous Versions

Ticket Number Description
VPBAGENT-7492 Malicious Process Blocking Events may not save to MPB.xml log
VPBAGENT-8261  Patch Management sometimes misidentifies the installed application versions when both x86 and x64 versions of the same app are installed
VPBAGENT-8267  Application view of both Vulnerability and Patch Management reports 0% of devices are using the latest version of an application when the site contains up-to-date devices