Note:  For the context of this article, the following terms apply:

  • An UPDATE refers to moving from an older software version to a newer software version. For example, an update from VIPRE 7.5 > VIPRE 9.5.
  • 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


  1. NEW FEATURES IN VERSION 9.6
  2. SYSTEM REQUIREMENTS
  3. UPGRADE NOTES
  4. KNOWN ISSUES AND WORKAROUNDS
  5. ADDITIONAL KNOWLEDGE BASE ARTICLES


1. NEW FEATURES IN VERSION 9.6


VIPRE Endpoint Security 

  • Device Control Installed & Configured As Per Policy - Device Control will now be installed and configured based on policy information instead of by default.  Device Control does require a reboot when enabled and disabled.
 


2. SYSTEM REQUIREMENTS


Management Console and VIPRE Site Service


  • Windows Server 2016
  • Windows Server 2012 (excluding Server 2012 Core)
  • Windows Small Business Server 2011, 2008 and 2003
  • Windows Server 2008 SP2 and 2008 R2 (excluding Server 2008 Core)
  • Windows Server 2003 SP1+ (32- & 64-bit)
  • Windows 10 and Windows 10 Anniversary Edition (32- & 64-bit)
  • Windows 8 (32- & 64-bit)
  • Windows 7 (32- & 64-bit)
  • Windows Vista SP2 (32- & 64-bit)
  • Windows XP Professional SP3 (32- & 64-bit) – Fully patched system


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 Premium and Endpoint Security versions for caching of patches)
  • 2 GB RAM
  • 1024 x 768 monitor resolution


MISCELLANEOUS


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


VIPRE Business Mobile Security


OPERATING SYSTEMS

  • Android 2.2 and above

  • iOS 5.1.1 and above


VIPRE Agent for Mac


OPERATING SYSTEMS

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

VIPRE Agent for Windows


OPERATING SYSTEMS

  • Windows 10 and Windows 10 Anniversary Edition (32- & 64-bit)**
  • Windows 8 (32- & 64-bit)
  • Windows 7 (32- & 64-bit)
  • Windows Vista, Vista SP1+ (32- & 64-bit)
  • Windows XP Professional SP3 (32- & 64-bit)*
  • Windows Server 2016**/***
  • Windows Server 2012 and R2(excluding Server 2012 Core)
  • Windows Small Business Server 2011, 2008 and 2003
  • Windows Server 2008 and 2008 R2 (excluding Server 2008 Core)
  • Windows Server 2003 SP1+ (32- & 64-bit)*
  • Windows Embedded for Point of Service (WEPOS) platforms
* VIPRE Endpoint Security is not supported on Windows XP or Server 2003.

** VIPRE Endpoint Security is not supported on these Operating Systems with Device Guard enabled. See this article for more information.

*** Windows Server 2016 currently does not support policies using VIPRE's Device Control feature.

 

HARDWARE

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


MISCELLANEOUS

  • Internet Explorer 8 or later


SUPPORTED EMAIL APPLICATIONS

  • Outlook 2003+
  • Outlook Express 5.0+
  • Windows Mail on Vista
  • SMTP/POP3 (Thunderbird, IncrediMail, Eudora, etc.)
  • SSL supported in Outlook and Outlook Express only

Product and company names are trademarks and registered trademarks of their respective owners.



3. UPGRADE NOTES


IMPORTANT :
  • If you deploy this console update without taking precautions, your console may automatically update your existing VIPRE Windows agent software. Read below for more information.
  • 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:

  1. Open the Management Console.
  2. Locate the policy for a set of agents you do not want to be updated, and select the properties for that policy.
  3. Navigate to Updates.
  4. Uncheck Check for agent software updates periodicity in hours.
  5. Repeat as necessary for each additional agent group and associated policy.
  6. 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.


Upgrading the VIPRE Business Console

See the following Support article: How to upgrade the VIPRE Business Console


Upgrading VIPRE Business Agents

The following support article has been updated to include special instructions for this release, and is highly recommended: How to configure agent software updates for VIPRE Business


4. KNOWN ISSUES AND WORKAROUNDS



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

This is normal, as communication between the Console > Hyper-V agent, followed by communication between the Hyper-V agent > VM takes some time to propagate. 

 • 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 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. 


See the following support article: Recommended SQL Server settings for a VIPRE Business Database
 • VIPRE Endpoint Security agents cannot run on Windows XP or Windows Server 2003.

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.

• Advanced Active Protection cannot operate on machines with Device Guard enabled (VPBAGENT-2325).

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.


See the following support article: Does VIPRE’s Advanced Active Protection work in conjunction with Microsoft’s Device Guard feature?
 • Push agent installations do not work if Simple File Sharing is enabled.
Simple File Sharing prevents installation through the push option. You must manually create the MSI installer package and deploy the installer to the workstation. 

See the following support article: Minimum Requirements for Agent Push Deployment
 • Without proper firewall configuration, agents are unable to contact the Console.
An incorrectly configured firewall can prevent communication between the agent and the console.


See the following support article: Minimum Requirements for Agent Push Deployment
 Using a Remote Admin Console running VIPRE Business 9.3 in conjunction with a VIPRE Business 9.5 Console can overwrite the VIPRE Business 9.5 Console settings (VIPREBIS-5501).


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


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

or

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


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

  1. In the Policy Properties, open Agent > Communication
  2. Check Use ThreatTrack as Update Server for definitions and software updates
  3. Click OK.
• Windows Defender continues to run despite enabling policy change (VPBAGENT-2403).

For policies applying to machines running Windows Server 2016, selecting "Disable Windows Defender" does not actually disable Windows Defender.


Workaround: You must manually disable Windows Defender on these machines. 

See the following Microsoft TechNet article: Windows Defender Overview for Windows Server
• Device Control policy changes may require an agent restart before they take effect.

On Consoles upgraded to 9.5.2.5 from any beta Console and agents upgraded to 9.5.6154 from 9.5.6150, 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:

  1. Right-click on the agent in the grid
  2. Select Issue Remote Restart Command.
• The Database Migration Utility may crash if the SQL Database has any spaces in the database name (VIPREBIS-5494).

The Database Migration Utility for VIPRE 9.5.2.5 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 (VIPREBIS-5498).

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 (VPBAGENT-2435).

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.

or

Workaround: Restart Outlook after agent install when enabling Anti-Phishing.

• Windows 10 agents may BSOD after updating to agent version 6032 (VPBAGENT-2423).

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 can not 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.5 or later can cause a blue screen state on systems with older versions of Citrix drivers on them.
 
Workaround: Updating the Citrix driver should resolve the issue.



5. ADDITIONAL KNOWLEDGE BASE ARTICLES


Advanced Active Protection & Device Guard

How to setup a VIPRE Business Agent for multiple environments

What is required for VIPRE Business Console to update properly?

Minimum Requirements for Agent Push Deployment

How to configure your Windows Firewall for VIPRE Business

What are Roaming Agents and how do they work?

How to confirm connectivity between a VIPRE Agent & Console

How to setup VIPRE Business Agents for different environment types

Copyright © 2008–2017 ThreatTrack Security, Inc. All Rights Reserved. ThreatTrack Security, VIPRE and the VIPRE Logo are trademarks or registered trademarks of ThreatTrack Security, Inc. in the U.S. and other countries. Other names may be trademarks of their respective owners.