Product release information for VIPRE Cloud Console released on December 12, 2017.
What's new
- Administrators now have the ability to rename their VIPRE Cloud site
- The Help tab has been updated with links to the VIPRE Success portal (Documentation) and VIPRE Business Support (Live Chat, Forums, contact information)
- In a policy's agent settings, you can now select "Show list of incompatible software" to view and search the CART list
- The Dashboard News widget now displays current feeds from both the VIPRE Blog (https://www.vipre.com/blog/) and VIPRE Labs Blog (https://labs.vipre.com/)
- When viewing license information on an expired site, we now provide a link to purchase a license
- Devices which need a reboot are now listed on the Dashboard under Devices Needing Attention. There is also a filter option for these devices on the Devices screen
- Immediate threat notifications are now rate-limited to 10 per hour
- You may now allow end users to configure or disable the firewall, and stop/start all firewall traffic
- When viewing a policy’s summary page, you can now select View Assigned Devices to show a detail list of devices which the current policy is assigned to
- Changes to the default policy settings are as follows:
- Both default policies now have Enable laptop power save mode selected
- The default Windows Server policy has Active Protection set to Execution Only (Performance mode)
- The default Enterprise policy has Enable Anti-Phishing selected
Bugs fixed in this release
- VC-2253: Attempting to add exclusions for an entire drive letter (such as "F:\") was previously rejected as invalid.
- VC-2140: Weekly Device Health Summary emails were missing the VIPRE Cloud site name
- VC-2129: Adding exclusions for folders previously required a trailing slash (such as "c:\folder\")
- VC-2240: Notification emails are no longer sent to expired sites not in use
- VC-2149: Help tab needed to be updated with correct VIPRE Success portal and Support information
- VC-2057: Bulk add of quarantined items to an exclusion list would fail when un-quarantining