Menu
VIPRE Business has an agent that will run on Macintosh. Installation Package will need to be used as the console does not support a Push Deployment to Macs: Installation Package Creation Open the VIPRE Business Console; Right-Click the intended Mac Policy and select 'Properties' Open Communication and confirm the Policy Server's Address. Ultimate protection from today’s sophisticated threats without the unnecessary complexities found in other endpoint solutions. Powered by advanced machine learning, real-time behavioral analysis and a threat intelligence network, VIPRE combines a modern endpoint solution with time-saving efficiencies to keep organizations up and running.
CONTENTS
1. New features in version 10.0
VIPRE Endpoint Security
2. System requirementsManagement Console and VIPRE Site Service
Note:Embedded operating systems are not supported
HARDWARE
MISCELLANEOUS
VIPRE Business Mobile Security
OPERATING SYSTEMS
VIPRE Agent for Mac
OPERATING SYSTEMS
VIPRE Agent for Windows
OPERATING SYSTEMS
** VIPRE Endpoint Security is not supported on these Operating Systems with Microsoft's Device Guard enabled. See this article for more information.
*** Windows Server 2016 currently does not support policies using VIPRE's Device Control feature.
HARDWARE
MISCELLANEOUS
SUPPORTED EMAIL APPLICATIONS
Product and company names are trademarks and registered trademarks of their respective owners.
3. Upgrade notes
If you DO NOT wish to automatically update your existing agents, you can temporarily change your policies by doing the following prior to installation:
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 ConsoleSee the following Support article: How to upgrade the VIPRE Business ConsoleUpgrading 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
Msp_mxf.avx download mac. 4. Bugs fixed
The following issues have been resolved in this release:
VIPRE Console
VIPRE Agent
5. Known issues and workarounds
• Microsoft Windows Defender continues to run even if policy has Disable selected
For policies applying to machines running Windows Server 2016, 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:
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.
• .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.
Vipre Endpoint Security Download Mac Installer
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.
• Advanced Active Protection cannot operate on machines with Device Guard enabled.
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.
• 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.
• Without proper firewall configuration, agents are unable to contact the Console.
An incorrectly configured firewall can prevent communication between the agent and the console.
• 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:
• 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 Mac hoopa wonder card download. : Manually restart the agent to apply policy changes.
To manually restart an agent:
• 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.
or
Workaround: Restart Outlook after agent install when enabling Anti-Phishing.
Download calibre to your mac.
• Windows 10 agents may BSOD after updating to agent version 6032.
Vipre Endpoint Security Server
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, pleasecontact Supportso 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 agentsUpdating 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.
6. Helpful articlesAdvanced Active Protection & Device Guardhttps://businesssupport.vipre.com/support/solutions/articles/1000240571-advanced-active-protection-device-guard Vipre Endpoint Security7. Product changes
8. Download productVipre Endpoint Security Console
To begin the update process, download the installer from here: Download VIPRE Endpoint Security Installer
Vipre Endpoint Security Download Mac High Sierra
Copyright © 2008–2017 VIPRE Security. All Rights Reserved.VIPRE Security, VIPRE and the VIPRE Logo are trademarks or registered trademarks ofVIPRE Securityin the U.S. and other countries. Other names may be trademarks of their respective owners.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |