VIPRE® Endpoint Security 10.0 Release Notes

An UPDATE refers to moving from an older software version to a newer software version. For example, an update from VIPRE 7.5 > VIPRE 10.0.

An UPGRADE refers to moving from one edition of VIPRE to a more enhanced edition. For example, an upgrade from VIPRE Antivirus Business > VIPRE Endpoint Security.

IMPORTANT:When upgrading agents, you must create an EXE installer package instead of an MSI installer package. Using the MSI installer package to upgrade an agent will cause the upgrade to fail. See Possible Issues During Update/Upgrade below (this also applies to updating an agent during the upgrade).

CONTENTS

New features in version 10.0

System requirements

Upgrade notes

Bugs fixed

Known issues and workarounds

Helpful articles

Product changes

Download product

1. New features in version 10.0

VIPRE Endpoint Security

NEW! Health Summary Report - A special report that provides an at-a-glance overview of your site's 'vital stats'. This report has a new look and feel with engaging, clean visuals. The main content of the report is an embedded HTML for instant viewing in your email. A PDF is also attached for forwarding on to other parties within your organization. This also provides a quick notification to the Console administrator regarding agents that are outdated and need to be updated.

NEW! Stealth Mode - Admins can now enable Stealth Mode on agents, which blocks outgoing ICMP unreachable and TCP reset messages for a port when no application is listening on that port.

Upgraded Device Control - New version of Device Control library offers better stability.

NEW! Color coding on agent version - Console admins now have quick visibility to which agent versions are out of date.

Various performance and bug fixes

2. System requirements

Management Console and VIPRE Site Service

Windows Server 2016

Windows Server 2012 (excluding Server 2012 Core)

Windows Server 2008 SP2 and 2008 R2 (excluding Server 2008 Core)

Windows 10 All editions (32- & 64-bit)

Windows 8 (32- & 64-bit)

Windows 7 (32- & 64-bit)

Windows Vista SP2 (32- & 64-bit)

Note:Embedded operating systems are not supported

HARDWARE

Dual core processor or higher

1 GB free disk space(up to 20 GB could be required for Endpoint Security versions for caching of patches)

3. Upgrade notes

IMPORTANT:

When upgrading agents, you must create an EXE installer package instead of an MSI installer package. Using the MSI installer package to upgrade an agent will cause the upgrade to fail. See Possible Issues During Update/Upgrade below (this also applies to updating an agent during the upgrade).

If you DO NOT wish to automatically update your existing agents, you can temporarily change your policies by doing the following prior to installation:

Open the Management Console.

Locate the policy for a set of agents you do not want to be updated, and select the properties for that policy.

Navigate to Updates.

Uncheck Check for agent software updates periodicity in hours.

Repeat as necessary for each additional agent group and associated policy.

Wait 24 hours after the policy change before performing the console update.

The agents that use the modified policies will retrieve the policy update and cache it locally, thereby preventing them from attempting to automatically update. The final step above ensures the edited policy propagates to all agents before the console is updated.

• VIPRE Business or VIPRE Business Premium agents on version 9.3 or earlier that are scheduled to upgrade to VIPRE Endpoint Security will not fully upgrade on the initial install.

VIPRE has added multiple driver updates that are included with this release. Depending on the version of the drivers on your system and which features are enabled in your policies (e.g. Device Control), installation may require two or more reboots to complete the agent upgrade.

Make sure any required reboots are completed: For the corresponding agent, check the Console > Agent Details > Agent Environment tab and verify the "Needs Reboot" column is not marked with an "X".

• Color coding of agent version in console does not appear to be consistent for all out of date agents

In the Protected Computers tab of the console, the agent version field is shaded orange for those agents that need to be updated to the latest agent software version. However, some agents that appear to be out-of-date are not shaded. Those agents include VIPRE Business or VIPRE Business Premium agents that do not have the highest build available. Agents that are not actively communicating are also not shaded but may be out of date.

Workaround: The agents will update with the correct status upon the next communication. You may note VIPRE Business or VIPRE Business Premium agents reporting incorrectly. We recommend these agents be upgraded to VIPRE Endpoint Security to match your VIPRE Endpoint Security 10 console. This will give you our best protection for these devices and correct the reporting issue. If you are not currently licensed for VIPRE Endpoint Security, please contact your sales representative (+1 855-885-5566 or Contact Sales) for more information on how you can upgrade.

• .NET error when version 10 console connects to VSS version 9.6 (or prior) and accessing Site or Policy properties

Due to changes introduced with VIPRE Business Endpoint Security version 10, including the update to .NET version 4.6, accessing version 10 consoles and resources from an older version of VIPRE Business is not supported. Likewise, using a version 10 console to access older consoles and resources is not supported.

• When changing Active Protection settings within a VM environment, the changes take up to 15 minutes to apply.

This is normal, as communication between the Console > VM takes some time to propagate.

• When VIPRE scans an email archive, files are not quarantined properly.

Workaround: Through your email client, perform a manual cleanup of the email archive containing the infected email. Once the infected email has been removed, re-scan the endpoint to confirm removal.

• When managing over 500 agents, a full SQL database should be implemented.

It is recommended that when managing over 500 agents, a full SQL database (versus SQLite) will provide the best performance.

The software limitations of these older platforms do not provide the resources necessary for some more robust agent features. VIPRE Endpoint Security requires a minimum OS version of Windows Vista or Windows Server 2008.

• Attempting to launch more than one instance of the administration Console (via terminal services) causes agent > Console communication to fail.

This is a product design safeguard that prevents one administrator from overwriting a different administrator's settings without notification. Only one instance of the admin Console should be running at a time.

Due to some of the constraints that Device Guard puts on running processes, Advanced Active Protection cannot provide its detailed and comprehensive monitoring of potentially malicious processes on platforms with Device Guard enabled.

• Using a Remote Admin Console running VIPRE Business 9.3 in conjunction with a VIPRE Business 9.6 Console can overwrite the VIPRE Business 9.6 Console settings.

If your primary VIPRE Business Console is running version 9.6, policy changes made on a Remote Console running version 9.3 could potentially overwrite the "Use VIPRE for Updates" setting on the 9.6 Console.

Workaround: Discontinue policy updates on the 9.3 Remote Console until it is updated to version 9.6.

or

Workaround: After each policy change made from the 9.3 Remote Console, select the "Use VIPRE as Update Server" setting on the 9.6 Console after any 9.3 Remote Console policy changes (below).

To use VIPRE as a (non-local) update server:

In the Policy Properties, open Agent > Communication

Check Use VIPRE as Update Server for definitions and software updates

Click OK.

• Device Control policy changes may require an agent restart before they take effect.

On Consoles upgraded to 9.6 or earlier, policy changes will not be applied until the agent is restarted.

Workaround: Manually restart the agent to apply policy changes.

To manually restart an agent:

Right-click on the agent in the grid

Select Issue Remote Restart Command

• The Database Migration Utility may crash if the SQL Database has any spaces in the database name.

The Database Migration Utility for VIPRE 9.6 or earlier may crash during the migration process if your SQL Database has spaces in the name of the database.

Workaround: Resolution is under development. When created, database names should contain no spaces, no symbols, and no carriage returns.

• Definition updates fail to load properly.

When running VIPRE 9.3.4.3 and performing a definition update from the Console, the VSS stops updating definitions and reaches an indefinite updating state.

Workaround: Shut down VIPRE and delete the definition folder. This will force a full update.

•Anti-Phishing does not work if Outlook is open during agent install.

If Outlook is running when enabling Anti-Phishing in the VIPRE Console before pushing an agent installation, it will not function properly until Outlook is restarted.

Workaround: Shut down Outlook during agent installation when enabling Anti-Phishing.

After updating to agent version 6032 for Windows 10 Anniversary support, some users have reported Windows 10 blue screen crashes. We have identified the cause of some of these occurrences and believe they are fixed with this release.

Workaround: As these crashes are difficult to reproduce, we cannot guarantee all are resolved. Occurrences should be rare. If they should happen, please contact Support so we can work with you to identify the cause and resolve the issue. As other causes are corrected, we will publish an agent hot fix to address.

• Outdated Citrix drivers may cause BSOD on Windows 7 agents

Updating a Windows 7 agent to VIPRE Endpoint Security 9.6 or earlier can cause a blue screen state on systems with older versions of Citrix drivers on them.