BitDefender - Latest Support Articles

EPS / BEST default Windows exclusions

BitDefender RSS (pr@bitdefender.com) — 2016-07-12T14:29:51+01:00

By default, the below Windows applications are excluded by EPS / BEST:

Exchange

Microsoft Exchange 2000
Microsoft Exchange 2003
Microsoft Exchange 2007
Microsoft Exchange 2010
Microsoft Exchange 2013

SharePoint

Microsoft SharePoint 12
Microsoft SharePoint 14
Microsoft SharePoint 15

SQL

SQL Server 2005
SQL Server 2008
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Citrix

Citrix XenApp
Citrix Provisioning Services
Citrix Virtual Desktop Agent

Microsoft Windows

WSUS Service
Microsoft Retail Management System
Microsoft Dynamics - Point of Sale

Other

Microsoft Cluster
Microsoft Forefront
Microsoft System Center Operations Manager 2007
Microsoft Config Manager 2007
Microsoft Configuration Manager
Microsoft ISA
Microsoft Forefront Threat Management Gateway
Microsoft Forefront Unified Access Gateway
Microsoft Data Protection Manager
Microsoft Team Foundation Server
Microsoft Operations Manager 2012 - 2012R2
Microsoft Lync server 2010
Microsoft Lync server 2013
Microsoft Dynamics CRM
Microsoft Hyper-V Manager Console
Microsoft System Center Configuration Manager
Intelligent Application Gateway
VMware ViewAgent

More details can be found in this Microsoft article.

How to uninstall the New Bitdefender Antivirus for Mac

BitDefender RSS (pr@bitdefender.com) — 2016-07-09T16:26:36+01:00

To remove Bitdefender Antivirus for Mac, please proceed with the following steps:

IMPORTANT: These steps apply for the New Bitdefender Antivirus for Mac. If you have the 2015 edition (the one with the grey interface) or a previous version, go to this article, here.

1. Minimize any open windows and click on an empty space on Desktop

2. Click on Go from the menu bar and select Utilities or press Shift-Command-U or open Finder and go to Applications>Utilities and run the BitdefenderUninstaller.

Alternatively, click on Go from the menu bar and select Computer. Go to Macintosh HD > Library > Bitdefender > Central > Agent and run the BitdefenderUninstaller.

3. A new window will pop-up. Click on Uninstall.

4. Confirm the process by entering the administrator password. The uninstalling will begin.

5. When the process is complete click on Close. A web page will open asking you to complete a survey. Your feedback would be much appreciated. If you don’t have the time, simply close the page.

6. Go to Macintosh HD > Library and move the Bitdefender folder to Trash. You will be asked for the administrator password again.

7. If you still have the Bitdefender icon in Dock, right-click on it, select Options > Remove from Dock

NOTE: The scan logs and the Quarantine will be remain at Macintosh HD > Library > Application Support > Antivirus for Mac. If you have important files that have been quarantined, it is necessary to reinstall Bitdefender in order to get them back. Otherwise, you may move to Trash the entire Antivirus for Mac folder.

NOTE: The uninstaller will also remove Bitdefender Virus Scanner Plus or Bitdefender Virus Scanner if they are installed on your Mac along with Antivirus for Mac.

Bitdefender Security for MSP Kaseya Version 1.0.3.15 Release Notes

BitDefender RSS (pr@bitdefender.com) — 2016-06-27T10:10:37+01:00

Release date: 2016-06-21

New Features and Improvements

Changes have been made to agent check-in mechanism, relying on Recurring Refresh and Data Refresh agent procedures execution history. The Endpoints view now displays only agent check-in information provided by Kaseya and no longer updates the endpoints table in the database.
Made several improvements and changes to FileWatcher service, in order to ensure database consistency and to provide better options for debug and test scenarios.

Resolved Issues

Fixed an issue where License Update task kept on running when encountering errors.
Fixed Kaseya server slowdowns caused by Bitdefender Kaseya Plugin.
Fixed an issue where an empty confirmation window was displayed when deleting a task from an endpoint information window.
Fixed an issue where, in rare cases, machines with Bitdefender Endpoint Security were restarting due to some updating errors.

Remote deploy BEST Linux on Oracle - SAP

BitDefender RSS (pr@bitdefender.com) — 2016-06-22T10:47:34+01:00

On Linux Oracle remote deployment via SSH is not possible due to the SFTP service. The same issue occurs on Unbreakable Oracle systems.

Resolution:

1. Edit sshd_config
2. Search for the line starting with: Subsystem
3. Comment and add the following line: Subsystem sftp internal-sftp

Incompatibility between BEST and Citrix EdgeSight

BitDefender RSS (pr@bitdefender.com) — 2016-06-24T07:07:24+01:00

Currently the only viable workaround for the BEST - Citrix EdgeSight incompatibility can be found below:

If both the Bitdefender Advanced Threat Control module (ATC) and Citrix Edgesight are installed on the same machine, Citrix Edgesight injection needs to be disabled by means of whitelisting. Access the following link for more information: http://support.citrix.com/article/CTX203185

To monitor only specific processes:

1. Add a list of processes to be monitored by EdgeSight (separate the processes by a semi-colon; do not include any leading spaces in process names) to the UviProcessList registry key.
2. Set the UviProcessIsExcluded registry key to 0 to include the processes in the list:

HKEY_LOCAL_MACHINE>SYSTEM>CurrentControlSet>Services>rskcore
Name: UviProcessList
Type: REG_SZ
Data: < semi-colon separated list of processes to monitor> - in your case, you would leave this empty

HKEY_LOCAL_MACHINE>SYSTEM>CurrentControlSet>Services>rskcore
Name: UviProcessIsExcluded
Type: REG_DWORD
Data: 0 (to include the listed processes to be monitored)

Installing BEST with Exchange in a VMware vShield environment

BitDefender RSS (pr@bitdefender.com) — 2016-06-22T09:31:07+01:00

In a VMware vShield environment integrated with GravityZone, protection is ensured via vShield. If an admin configures and installs a BEST package with vShield agent option selected and additional modules (i.e. Exchange Protection), only the Bitdefender agent for vShield gets installed.

In order to install BEST with Exchange in a VMware vShield environment:

1. When creating a BEST package, disable the Deploy endpoint with vShield when a VMware environment integrated with vShield is detected checkbox.
2. On the Exchange Server VM, disable the vShield driver in VMware Tools to prevent conflicts between the vShield protection and the BEST antimalware engine.

How to clean malware from an e-mail archive when using BEST

BitDefender RSS (pr@bitdefender.com) — 2016-06-22T08:54:49+01:00

Bitdefender can identify viruses in e-mail databases and e-mail archives stored on disk.
Sometimes it is necessary to identify the infected message using the information provided in the scan report, and delete it manually.

Here is how you can clean a virus stored in an e-mail archive:

1. Scan the e-mail database with BEST.

2. Turn OFF the Bitdefender On-access antivirus protection:

Open the BEST using Power User mode or modify the policy currently applied on the machine.
Under Antimalware > On-access, disable the On-access Scanning by unselecting the checkbox
Save.

3. Open the scan report and use the identification information (Subject, From, To) of the infected messages to locate them in the e-mail client.

4. Delete the infected messages. Most e-mail clients also move the deleted message to a recovery folder, from which it can be recovered. You should make sure the message is deleted also from this recovery folder.

5. Compact the folder storing the infected message.

In Outlook Express: On the File menu, click Folder, then Compact All Folders.
In Microsoft Outlook 2007: On the File menu, click Data File Management. Select the personal folders (.pst) files you intend to compact, and click Settings. Click Compact Now.
In Microsoft Outlook 2010 / 2013: On the File menu, click Info and then Account settings (Add and remove accounts or change existing connection settings). Then click Data File, select the personal folders (.pst) files you intend to compact, and click Settings. Click Compact Now.

6. Turn ON the Bitdefender On-access antivirus protection.

Bitdefender Endpoint Security Tools 6.2.9.775 Release Notes

BitDefender RSS (pr@bitdefender.com) — 2016-06-14T13:21:26+01:00

Release date: 2016.06.09

New Features and Improvements
Resolved Issues

New Features and Improvements

Windows & Linux

Integrated OpenSSL versions 1.0.1t and 1.0.2h in the security components of the product. For more information, refer to OpenSSL Security Advisory (English only).

Windows

Added support for uninstalling the incompatible security product Vipre Business Agent 7.0.5711.

Resolved Issues

Windows & Linux

Fixed OpenSSL vulnerability CVE-2016-2017.

Windows

Fixed an issue where Data Protection module incorrectly blocked web pages based on partial word match.
Fixed the installation error code 234 which occurred in some situations when installing the Firewall module.
Fixed an issue where XenDesktop agent did not run correctly after Content Control module was installed.
Fixed update server error code 1460.
Fixed some graphical user interface issues after updating Bitdefender Endpoint Security Tools to version 6.2.9.751.
Fixed an issue where some machines with Device Control enabled got BSOD when trying to connect an encrypted virtual hard-disk drive using VeraCrypt utility.
In some situations, websites with self-signed certificates did not load using Advanced option in Google Chrome when Scan SSL was enabled. The issue is now fixed.
Fixed an issue where some machines with Content Control module installed failed to connect using Telenium Network Management Software.
Fixed an issue where COALA finance software crashed on machines with Content Control module installed.
In some situations, the Power User module and language options were not displayed correctly in the contextual menu after updating Bitdefender Endpoint Security Tools to version 6.2.9.742. The issue is now fixed.
Fixed an issue where Device Control reports contained false blocked events on devices that were not used at the time.
Fixed an issue where the browser toolbar was still displayed on client machines despite being deactivated in policy or in the Power User settings.

Linux

On rare occasions, Linux machines were freezing when using an updated version of Bitdefender Endpoint Security Tools with an older version of Control Center.
Fixed an issue where on-demand scan tasks using Central Scan started without the endpoint being connected to Security Server.

Note:
During this product update, the Microsoft Exchange Transport service will be stopped.

Endpoint Security by Bitdefender Version 5.3.30.767 Release Notes

BitDefender RSS (pr@bitdefender.com) — 2016-06-03T13:57:38+01:00

Release date: 2016.06.01

New Features and Improvements
Resolved Issues

New Features and Improvements

Integrated the OpenSSL version 1.0.1t in the security components of the product. For more information, refer to OpenSSL Security Advisory (English only).
Added exclusions for System Center Configuration Manager 2012 (SCCM 2012) following Microsoft recommendations.
Added support for uninstalling the incompatible security product F-Secure Client Security 12.

Resolved Issues

In some cases, Endpoint Security could not be installed on machines running Wyse TCX. The issue is now fixed.
When installing Endpoint Security with Advanced Threat Control (ATC) on Windows 10 x64 systems, some machines entered recovery mode. The issue is now resolved.
Fixed OpenSSL vulnerability CVE-2016-2107.
Fixed an issue which affected the scan process on Windows 10 machines, when Offline Files feature was enabled.
In some situations, after updating Windows Server 2012 R2 machines with Endpoint Security installed, a slight slowdown was experienced at boot time. The issue is now resolved.
Fixed the installation error code 234 which occurred in some situations when installing the Firewall module.
In some situations, Endpoint Security prevented web pages from loading in Google Chrome version 38.0.2125.101. The issue is now resolved.
Fixed an issue which caused On-Demand scan to display error code 1460.
In some situations, machines with Endpoint Security failed to connect using Telenium Network Management Software, while having Content Control installed. The issue is now resolved.
Fixed an issue which affected Windows 8.1 and Windows 10 machines with Endpoint Security installed, while trying to connect to a specific network.
Fixed an issue where Endpoint Security with Content Control module installed caused COALA software to crash.
Fixed an issue with Advanced Threat Control (ATC) that was causing backups to fail when using VSS and Veeam 8.
Fixed an issue where Endpoint Security with Content Control enabled prevented access to an intranet address which was loading camera feeds.
Fixed an issue where Endpoint Security incorrectly displayed a notification of not having Cloud connectivity, when using a proxy with authentication.
Fixed an issue where Data Protection module incorrectly blocked web pages based on partial word match.
Fixed an incompatibility between Endpoint Security and the Sales Assistant for Windows 8 application.
Fixed update server error code 1460.

Bitdefender GravityZone 5.1.25-487 Release Notes

BitDefender RSS (pr@bitdefender.com) — 2016-05-31T12:57:55+01:00

GravityZone is a business security solution built from ground-up for virtualization and cloud to deliver security services to physical endpoints, mobile devices, virtual machines in private, public cloud and Exchange mail servers.

This article provides information on the changes delivered with the Bitdefender GravityZone version 5.1.25-487, released on May 31st, 2016.

New Features and Improvements

Computers and Virtual Machines Protection

As an administrator, you will be able to configure on-access scanning to take no action on infected files detected by Security Server in VMware environments integrated with vShield. Other security agents having this option set in the assigned policy will deny access to these files.

Resolved Issues

Computers and Virtual Machines Protection

Fixed an issue where endpoints could not connect to a custom port on the Communication Server.