Product release information for VIPRE Endpoint Security Server v12.3, released on September 16, 2021. This article was updated on November 30, 2021.
What's New
Update
12/14/2021: The VIPRE Mac Agent now supports macOS Monterey (12.1).
11/30/2021: The VIPRE Windows Agent v12.2 and 12.3 now support Windows 11.
We are releasing an updated Patch Management engine that allows VIPRE to support automatic updates to more products and improve the frequency of monitoring for recent software releases. This update replaces the patch management engine in any existing VIPRE Windows Agent installation that is communicating with VIPRE Console 12.3.
With this update also comes an update to Device Control. Our new Device Control no longer supports encryption and any encrypted drive will have "Read-Only" access.
IMPORTANT! A reboot may be required for devices that have device control enabled. See the topic Will I need to reboot my devices? (below).
The following policy options have changed in the new version:
- The ability to create exclusions based on user/group has been removed
- The option Force devices to use password-protected encryption has been removed
- The option Recover User Password has been renamed as Legacy Media Password Recovery
Finally, we've also fixed several issues. Specific details can be found in the Fixed Issues section below.
Device Control
You may have some questions about how the latest Device Control update will affect your systems. Here, we attempt to answer them.
What will happen to policies that have Device Control enabled?
- All exclusions set with Allow Other Permissions (Read, Write, Encrypt, Decrypt, Export to Media, Import) are retained after upgrade
- All exclusions set with Block All Access are retained after upgrade
- All exclusions that are not specifically set to Read and Write access will be set to Block All Access after upgrade
- All exclusions set as Both for Encryption (this is the default setting) are retained after upgrade; only exclusions with Self-contained encryption, Unencrypted/Unknown type of encryption are removed after upgrade
- All exclusions with User or User groups are removed after upgrade
- All exclusions setting connections such as All, USB, FireWire, ATA/IDE, SCSI, PCMCIA are retained after upgrade
- All exclusions setting drivers such as Both drive types, Hard drives, Non-hard drives are retained after upgrade
Will I need to reboot my devices?
The following scenarios will help you determine whether or not your devices will need a reboot before upgrading to VIPRE Agent v12.3.
A reboot is not required if:
- If your devices with VIPRE Agent v12.2 or older have Device Control disabled
- If you're performing a clean install of VIPRE Agent v12.3 with Device Control disabled
- If you're performing a clean install of VIPRE Agent v12.3 with Device Control enabled
- If you've enabled Device Control within a policy that has existing agents v12.3
- If you've disabled Device Control within a policy that has existing agents v12.3
A reboot is required if:
- If your devices with VIPRE Agent v12.2 or older with Device Control enabled
- If you've enabled Device Control within a policy that has existing agents v12.2 or older
- If Device Control was previously disabled and the agent machine(s) haven't rebooted since Device Control was disabled
- If you've disabled Device Control within a policy that has existing agents v12.2 or older
Patch Management
Below are the ever-evolving lists of applications that have been certified to work with our new patch management engine and the list of applications that are not currently supported.
Certified Applications
The following list of applications has been certified by our Software Development team as being supported by patch management within VIPRE.
- Adobe Acrobat Reader DC Classic 2017
- Adobe Acrobat Reader DC Classic 2020
- Adobe Acrobat Reader DC Continuous
- Apple Software Update
- Audacity
- Beyond Compare
- Calibre
- CCleaner
- CDBurnerXP
- Citrix Receiver
- Citrix Workspace
- Core FTP LE
- Dropbox
- Filezilla
- Foxit Reader
- GIMP
- Git
- Google Chrome
- Google Drive
- Google Earth Pro
- iCloud
- IrfanView
- iTunes
- Jabra Direct
- Java
- KeePass 1.x
- KeePass 2.x
- LibreOffice
- Lightshot
- Mozilla Firefox
- Mozilla Firefox ESR
- Nitro Pro
- Node.js Current
- Notepad++
- Open Office
- OpenVPN
- Origin
- PDFCreator
- pgAdmin 4
- Pidgin
- PuTTY
- QuickTime
- RealPlayer
- Recuva
- SeaMonkey
- ShareX
- Skype
- Sublime Text
- Thunderbird
- TightVNC
- TortoiseGit
- TortoiseSVN
- Total Commander
- VirtualBox
- VLC media player
- VMware Tools
- VNC Server
- VNC Viewer
- Winamp
- WinMerge
- WinRAR
- WinZip
- Wireshark
- XnView
- Zoom
Unsupported Applications
The following applications are no longer supported by patch management within VIPRE.
- 7-Zip
- Adobe AIR
- Adobe Bridge
- Adobe Digital Editions
- Adobe Flash Player
- Adobe Flash Player ActiveX
- Adobe Flash Player NPAPI
- Adobe Flash Player PPAPI
- Adobe Flash Player Plugin
- Adobe InDesign CS6
- Adobe Illustrator
- Adobe Photoshop
- Adobe Reader
- Adobe RoboHelp
- Adobe Shockwave Player
- Apple Mobile Device Support
- AutoFirma
- Bonjour
- Cisco Jabber
- Google Drive File Stream
- Google Earth
- Google Picasa
- VMware Horizon Client
- VMware Player
- VMware Workstation 16 Player
- VMware Workstation 16 Pro
- Citrix Receiver Enterprise
- Citrix XenApp
- Evernote
- Foxit Enterprise PDF Reader
- Foxit Enterprise Reader
- Foxit PDF Editor
- Foxit PDF Reader
- Foxit PhantomPDF
- GoToMeeting
- Amazon Corretto
- AutoCAD 2017 SP1
- Box Sync
- Classic Shell
- Client for Open Enterprise Server 2 SP5
- DameWare Mini Remote Control Service
- Greenshot
- HPE System Management Homepage
- Inkscape
- MindManager
- Opera
- PKWARE PKZIP
- Paint.NET
- RealTimes (with RealPlayer)
- Slack Machine-Wide
- TechSmith Snagit
- Telegram
- TightVNC Server
- UltraVNC Server
- UltraVNC Viewer
- Webex Productivity Tools
- Webex Teams
- WinPcap
- Yahoo Messenger
Special Instructions
Update Endpoint Server Console & Agents
There are some things to keep in mind when updating the Endpoint Server Console a...
There are some things to keep in mind when updating the Endpoint Server Console and Agents.
Important
- It is recommended to create a backup of the VIPRE database prior to updating. Refer to Related Articles for details on how to accomplish this.
- Database migration can take some time depending on the size of the DB. Canceling the wizard can result in data loss.
- If updating the Endpoint Server console from any version lower than v10.0, you will need to plan for a possible reboot. Updating the VIPRE Endpoint Security console to the newest version will require Microsoft .NET Framework 4.6 to be installed. If .NET Framework 4.6 is not already on your system, the installer may reboot the server to finalize the installation.
Step 1: Update VIPRE Console
Ensure the VIPRE Console is closed prior to updating.
- Download and run VIPRE Endpoint Security (Key starts with 443)
- Proceed with the installation prompts to complete the update
- If necessary, read up on what is required to update and how to troubleshoot
- Proceed to Step 2: Update the VIPRE Agents
Step 2: Update VIPRE Agents
There are three ways to update agents:
Automatic agent updates
- Open the policy properties
- Navigate to Updates > Software Updates
- Check the box and set the time to how often VIPRE should check for updates
Manual agent updates
- Open the VIPRE Business console and select Windows Policies
- Click on the Protected Computers tab
- Right-click the Agent(s) and select Agent Updates > Check for Agent Software Updates
Scheduled agent updates
- Open the VIPRE Business console and select Windows Policies
- Click on the Protected Computers tab
- Right-click the agent(s) and select Agent Updates > Schedule Agent Upgrade
- Select the time and date you wish to schedule updates for and click OK
System Requirements
| Product or Component | Minimum Requirement |
| Management Console (VSS) |
OPERATING SYSTEMS
NOTE: Embedded operating systems are not supported HARDWARE
MISCELLANEOUS
|
| VIPRE Agent for Windows |
OPERATING SYSTEMS
† Supported for legacy agent only, not available for Cloud
HARDWARE
SUPPORTED WEB BROWSERS FOR HTTPS URL PROTECTION
SUPPORTED EMAIL APPLICATIONS
|
| VIPRE Agent for Mac |
OPERATING SYSTEMS
|
| VIPRE Business Mobile Security Agent |
OPERATING SYSTEMS
|
Fixed Issues
- VIPREBIS-7563: When enabling VIPRE Chrome extension, applications managed by Google Workspace are removed
- VIPREBIS-7791: Patch Management doesn't have the latest Chrome and Adobe Reader DC security patches available
- VIPREBIS-7741: CARL server doesn't handle X-Forwarded-For header from reverse proxy
- VIPREBIS-7750: MAC agents are assigned to Windows policies
- VIPREBIS-7766: Web Exploit Protection interfering with Blackbaud sign-in
- VIPREBIS-7733: Active Protection blocking upload of Amazon WorkDocs
- VIPREBIS-7837: VIPRE URL Filtering extension causing Chrome-based apps to launch as a Chrome tab rather than a standalone window
- VIPREBIS-7720: Device Control fails to install
- VPBAGENT-7803, VPBAGENT- 8001: Web Exploit detection is interfering with some websites
Known Issues
| Ticket | Description |
|---|---|
| VPBAGENT-7351 |
VipreNis stuck in STOP_PENDING state when disabling network protections Workaround: Stop the VIPRE agent then restart it |
| VPBAGENT-7492 | Failed to save the event to the log for Malicious Process Blocking |
| VPBAGENT-7760 | Email Protection - Anti-Phishing feature causing slowness in Outlook Workaround: Temporarily disable the Anti-Phishing feature, or use a different email client, until the slowness issue is resolved |
| VPBAGENT-7857 | Unable to use AXIS Companion Camera software when Malicious URL Content Blocking for HTTPS feature is enabled Workaround: Temporarily disable Malicious URL Content Blocking for HTTPS when you need to access AXIS Companion Camera software |
| VIPREBIS-7662 | New installs of VIPRE Business Mobile Android via Google Play are blocked Workaround: Sideloading the VIPRE Android Agent |
| VIPRMDMIOS-16 | Missing information such as device model, OS version, the product name for the agent for iOS. |
Known Issues from Previous Versions
Agents running Windows Server 2019 do not reboot when clicking "Reboot Now" on a VIPRE Reboot Required condition [VPBAGENT-3920]
This is a condition that occurs due to changes in Windows Server 2019 security settings.
Endpoint devices running Windows Server 2019 will not reboot when the "Reboot Now" button is selected unless the user account is added to a specific Windows Local Security Policy. The default "Administrators" group cannot restart the Agent using this method.
Workaround 1: Add the user to the "Shut down the system" policy
To add a user account to the "Shut down the system" policy
- On the Agent machine, open the Windows Local Security Policy
- Add the required user account to the "Local Policies" > "User Rights Assignment" > "Shut down the system" policy
- Sign Out and Sign In to the machine (or reboot) for the policy change to apply
The next time VIPRE requires a reboot, the modified user will be able to reboot the machine using the "Reboot Now" button.
Workaround 2: Restart the Agent manually
Instead of using the Reboot Now button, users can manually restart the Agent through the Windows Start menu.
Firewall trusted zones defined with IPv6 address ranges do not work [VBAGENT-3187]
The VIPRE Agent does not recognize IPv6 trusted zone ranges and treats any IPv6 traffic as non-trusted. Therefore, any firewall rules for non-trusted traffic will still apply.
There is no known workaround at this time.
Logging into a Citrix device with Active Protection enabled fails [VBAGENT-275]
This is a known conflict between VIPRE Active Protection and Citrix User Profile Management (UPM). Attempting to login to a Citrix device with both services enabled causes the login to hang and eventually fail.
Workaround: Temporarily disable Active Protection for Agents that need to access Citrix devices.
Microsoft Windows Defender continues to run even if policy has Disable selected
For policies applying to machines running Windows Server 2016 or higher, selecting "Disable Windows Defender" does not actually disable Windows Defender.
Workaround: You may manually disable Windows Defender on these machines. Refer to these articles for more information:
- Disabling Windows Defender Antivirus on Windows Server 2016
- Microsoft TechNet article: Windows Defender Overview for Windows Server
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.
Workaround: 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 11 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.
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.
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.
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
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.
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 1: Shut down Outlook during agent installation when enabling Anti-Phishing
Workaround 2: Restart Outlook after agent install when enabling Anti-Phishing
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.
Workaround: Updating the Citrix driver should resolve the issue.
On some systems, Windows Defender's Smart Screen blocks the agent installer
Select More Info from the Windows Defender popup and then select Run Anyway.