Mr.Gains

The virtual appliance based on Rocky Linux 9 is planned to be available soon. As for installation on Linux, this is yet to be evaluated and decided. Would it be ok for you to use the virtual appliance if the database could not be migrated?

Windows firewall allows all outbound communication so no extra rules should be needed for ESET security products to work.

A list of supported MySQL ODBC drivers is available at https://help.eset.com/protect_install/91/en-US/database_requirements.html:
5.1, 5.2 5.3.0-5.3.10 8.0.16, 8.0.17 8.0.27 (Windows only)

Hi @Mr.Gains,
It very much sounds like you are running into an issue we have documented here: https://support.eset.com/en/kb7132-use-eset-endpoint-encryption-with-microsoft-surface-devices#FDE regarding MS Surface Pro 7+ running into a Boot Configuration issue during Safe Start.
Thank you,
Kieran

I would recommend to double-check that WMI works properly on such device, as OS information should indeed update itself automatically after some time, or when change is detected.

From description you provided it seems, that the same license was added into console using two methods:
Added license by it's key, either manually in the console or even during deployment of console itself (indicated by key icon) Added license by EBA accounts (indicated by EBA account and person icon in the list) Solution to this might be to consolidate this list. I would recommend to first:
Add the same license using your EBA account, just to verify it will work Remove original copies of the same license, i.e. the one tied to old/unused EBA account and the one entered by key Correct existing activation, deployment and installer tasks, ad they are most probably referencing licenses that you just removed - tasks and installer will be marked as invalid and won't work until they are updated with proper licenses Removing and re-adding licenses won't have any impact on products functionality (they will remain activated) but new deployments and activation might fails from the console in case tasks won't be updated after license re-adding.

Turns out we had to manually clear the TPM on the device, which then we're able to start the encryption. Something I have to note next time I go through the process, but I thought EFDE clear the TPM when taking over?

Cheers, it doesn't tell me the policy name but it does give me some relief to see the configuration (same custom policy I applied in the installer). Learned something new today, thank you JPritchard

Good afternoon!
The behavior you describe is normal - Policies applied by the installer do not show in the console. However, where EFDE is concerned, you will see the encryption status information on the computer panel here:

If you want to update the Policy details in the ESET Protect console, then you can press the "REQUEST CONFIGURATION" button. Once processed, you will see the currently applied policies. Here's an example:
Before

After

It might be possible to automate this process, however I don't know enough about ESET Protect to assist you further with this. You may want to ask for further help in the ESET Protect forum or contact support.
I hope this helps out!

The issue is with the server certificate being to strict/not matching the hostname used in the agent installer.
First check the server peer certificate which hostnames are allowed (listed in the column HOST).
If you want to allow additional hostnames/IPs you can create a new server certificate containing all allowed hostnames seperated by space, comma, or semicolon. Or you can leave the default (*) to allow all hostnames.
Afterwards you have to assign this new certificate in the server settings and restart the Virtual Appliance (or the eraserver-Service) for the change to take effect.
You can also perform a repair installation and change the hostname. Please be aware that the hostname has to match eaxctly.

Hi,
We're currently reviewing our server protection, we have around 150 on a mix of ESET File Security 7.0 and 7.1 (Windows only) which according to the EOL page is in support (Limited for 7.0, Full for 7.1). 
With ESET Endpoint AV V8 being released for clients is there any rough estimated date/quarter/year on when the next major version for File Security will be released?
I've noticed 7.3 released for ESET File Security last month (EOL page not updated to show that?) but we're reviewing whether we should upgrade all our 7.0/7.1 servers to 7.3 or wait for V8. It be months of work to go to 7.3 only for V8 be released and have to do it all again so be good to know!
Thanks

Awesome, I think those reports would actually cover what we need. If something comes up in what we need to see in reports, I'll come back and let you know.
Thank you

Hi @Mr.Gains
you are right, reports are in the works currently.
we are panning to offer reporting (more or less) in this scope:
Computers not eligible for encryption Computers eligible for encryption  EFDE not installed Computers eligible for encryption. EFDE installed AND disk not encrypted Computers with encryption in progress Computers encrypted  Computers encrypted using TPM chip Computers encrypted using OPAL 2.0 Computers encrypted via FileVault2 (future) Computers with boot disk only encrypted Computers with all disks encrypted Computers recovered in past month... What exactly would you like to see in the reports? Except for "password uses left" you mentioned above...
Thank you for your inputs
Ervin Rendek
PM for Encryption solutions

In the EFDE policy we have total recovery password uses, and the recovery password reset when it reaches a number of uses left. The issue I see with this is that the user can reuse the same recovery password until they reach the auto-generate new password in policy, could we have this to where it could generate a new password after a number of use? For example in policy there's 20 recovery password uses, and it'll auto-generate a new recovery after every 2 recovery password used, and it'll warn the user when there's 4 total recovery password uses available before recovery data needs to be done. Another thing in entering incorrect password at the EFDE login screen, sometimes I get more attempts than I'm allowed and/or system reboot after 3 times. I'm thinking there's a bug in the password attempts, but it would nice for users to see how many more attempts until the current password is disabled.
Thanks,