Issue
Solution
When an ESET Endpoint Encryption (EEE) client machine is activated with the EEE Server, compatibility checks are performed, and the information is returned to the EEE Server. The compatibility checks ensure the client machine is compatible with Full Disk Encryption (FDE) before encryption is started.
The results of the compatibility checks are displayed in the EEE Server at the beginning of the FDE wizard. Compatibility issues include any incompatible software found, disks already encrypted with other software, warnings, and suggestions for how to proceed.
Figure 1-1
If no incompatibilities are detected, select a Start Mode option and proceed with the encryption.
We recommend using Safe Start mode because it checks for compatibility issues on system startup. You can use Normal start mode which does not require a restart. However, this does not perform additional checks for startup compatibility. For more information about Safe Start mode, visit Full Disk Encryption Safe Start in ESET Endpoint Encryption.
Figure 1-2
If incompatibilities are detected, they will be displayed as shown below. There are three types of compatibility issues:
- Green items contain system information.
- Yellow items contain warnings, including any special conditions or actions to perform to start encryption successfully. In some cases, a warning item will restrict the start mode to Safe Start.
- Red items indicate incompatibilities are present. These include any detected issues that will prevent encryption from working. If an item is red, the FDE will not be able to start until the issue is resolved. Issues may be due to incompatible software being installed or other disk encryption already on the system.
Figure 1-3
List of issues that cause incompatibility
Incompatible Software
If EEE detects incompatible software, you will need to remove the software before continuing. You may also need to decrypt the data encrypted with the incompatible software.
- PGP, including Symantec Endpoint Encryption
- SafeBoot including McAfee Endpoint Encryption and HP ProtectTools
- DriveCrypt
- Securedoc
- Check Point
- SafeGuard
- DiskCryptor
- TrueCrypt
BitLocker
If the system drive is encrypted with BitLocker, then it must be decrypted first.
Boot Loaders
If EEE detects an incompatible system boot loader, you will need to remove this boot loader and use the standard Windows boot loader before continuing.
- GRUB
- LILO
Raid Disk Controllers
Software RAID is not supported, but some hardware RAID and RAID Ready (IRST) do work without issue. Use Safe Start to check for compatibility.
ESET Endpoint Encryption Client System requirements
For the compatibility checks to be reported to the EEE Server and to use Safe Start mode, the workstation must have version 4.7.4 or later of the EEE Client. You will be able to start Full Disk Encryption with previous versions. However, incompatibilities will not be able to be checked by the server, and Safe Start mode will not be available. Client checks will still be performed; however, we recommend that EEE be upgraded to the lasted version.
Figure 2-1
