Rendekovic

Hi @Mr.Gains,
Thank you for getting in touch, may I suggest you contact your local ESET Support office via the following link: https://www.eset.com/us/about/contact/ as this will need investigating further, which I cannot provide over our forum due to the complexity behind some of these issues. When getting in touch with your local ESET Support office, could you provide the following logs from your machine: https://support.eset.com/en/kb7123-eset-endpoint-encryption-diagnostics-utility
Thank you,
Kieran

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!

Hi @Simon Simon,
File type is not limited, however File size can be, please see here for more information: https://support.eset.com/en/kb7584-file-size-limitations-in-eset-endpoint-encryption
Thank you,
Kieran

Hello @Kostadin_k,
EFDE for mac utilizes FileVault because there is no other way to FDE macOS. Apple prevents its system to use FDE from 3rd party vendors.
EFDE for win is a different story. Microsoft allows for vendor´s proprietary encryption and we have this covered.
So we are pretty much covered on both macOS and Windows. But yes, adding Bitlocker management to ESET Protect (Cloud) is an option, but even if we go this direction in the future, it will not work as seamlessly as you described. Taking over management of an already encrypted machine is more than complicated because of recovery password that belongs to a particular encrypted system. Migration of these recovery passwords from Active Directory (where Bitlocker stores them)  to our console followed by a seamless "takeover" of the machines by the console is very complicated (if even possible).
At this moment, adding management of Bitlocker to our EFDE/EP(C) solution is not on our roadmap.
Ervin Rendek
PM for Encryption solutions

Hello @Kostadin_k,
EFDE for mac utilizes FileVault because there is no other way to FDE macOS. Apple prevents its system to use FDE from 3rd party vendors.
EFDE for win is a different story. Microsoft allows for vendor´s proprietary encryption and we have this covered.
So we are pretty much covered on both macOS and Windows. But yes, adding Bitlocker management to ESET Protect (Cloud) is an option, but even if we go this direction in the future, it will not work as seamlessly as you described. Taking over management of an already encrypted machine is more than complicated because of recovery password that belongs to a particular encrypted system. Migration of these recovery passwords from Active Directory (where Bitlocker stores them)  to our console followed by a seamless "takeover" of the machines by the console is very complicated (if even possible).
At this moment, adding management of Bitlocker to our EFDE/EP(C) solution is not on our roadmap.
Ervin Rendek
PM for Encryption solutions

Hello @Kostadin_k,
EFDE for mac utilizes FileVault because there is no other way to FDE macOS. Apple prevents its system to use FDE from 3rd party vendors.
EFDE for win is a different story. Microsoft allows for vendor´s proprietary encryption and we have this covered.
So we are pretty much covered on both macOS and Windows. But yes, adding Bitlocker management to ESET Protect (Cloud) is an option, but even if we go this direction in the future, it will not work as seamlessly as you described. Taking over management of an already encrypted machine is more than complicated because of recovery password that belongs to a particular encrypted system. Migration of these recovery passwords from Active Directory (where Bitlocker stores them)  to our console followed by a seamless "takeover" of the machines by the console is very complicated (if even possible).
At this moment, adding management of Bitlocker to our EFDE/EP(C) solution is not on our roadmap.
Ervin Rendek
PM for Encryption solutions

Problem fixed. Windows server updates had reactivated a couple of services which had nabbed port 80. Simply disabling them negated the issue. I'm now planning on moving the EEE server onto a different port to resolve the issue permanently during the downtime over the weekend.

I'm pleased to hear that has resolved your issue.
Have a nice evening 🙂
-JP

Hi @GPennarun,
I am sorry that your tickets are not responded to. Please could you provide us with the ticket number? I will in turn check what happened to it.
Especially for #2 , I would like to get more details on this problem and to see what is the cause! 
Best regards,
Ervin Rendek, PM

Hello @GPennarun,
Sorry to hear that your tickets are not being responded to, may I ask where you are submitting them? 
In regards to your issues, the ECA issue does indeed sound like a permission problem, I'm afraid I am only familiar with EFDE, so it is difficult for me to assist you with issues in ECA itself.
Unfortunately I do not know why the machines are not showing as encrypted in the server. However, I may be able to suggest another way to obtain the recovery password for your machines. 
Please try to obtain the recovery information via this method.
If you click Help along the banner and select Encryption Recovery as shown on screenshot below.

Once the windows opens, you will be prompted to enter Workstation ID, please fill this field in and continue.

Good afternoon,
I'm sorry to hear about this issue. 
I suspect you are encountering a known issue with the latest version of Windows 10 2004 (OS build 19042).  You can check what Windows version you are running by typing 'winver' into the Run dialog. I have attached an example:
 
 
If your computer IS running Windows 10 2004 (OS build 19042), then please check to see if you are missing the UseNullDerivedOwnerAuth registry value found in:
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TPM\WMI
If it is missing, then you can create it manually by opening an elevated command prompt and entering the following command:
reg add hklm\system\currentcontrolset\services\tpm\wmi -v UseNullDerivedOwnerAuth -t REG_DWORD -d 0x01 -f
After running this command, reboot your computer before trying FDE again. This should allow the TPM to be used for encryption. 
Let me know how you get on.
- JP

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

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

Hello @Mr.Gains, thank you for your post,
to resolve the issue you describe (I believe I understood correctly) I suggest to do the following in an EFDE Policy:
set "Maximum uses" under "Recovery Password Uses" to 2 AND "Automatically generate new recovery password" under "Recovery Password Uses" to YES AND "Generate when (uses remain)" under "Recovery Password Uses" to 1 This way you will restrict use of one recovery password to 2 uses, and after the 1st use a new one will be generated and will become a valid recovery password AFTER EFDE connects with ESMC.
 
With more attempts than set in a policy, it sounds like a bug. Could you please raise a tech. support ticket for this issue? we will investigate
 

Hey Lockbits,
Thanks for your interest. Of course SSO is a very useful feature. As of now, it is not strictly in our roadmap since not many customers has asked for it yet. We are constantly monitoring and prioritizing the requirements from the market and based on them additional development is scheduled. I would say this feature will be added later, but I cannot commit to a specific delivery time 
Best regards
Ervin

Hi ADS82,
Thank you for contacting us.
Could you please be more specific and let us know what exactly would you like to achieve in as much detail as possible?
Unfortunately, your request is very concise and I cannot really imagine what is your usecase.
Best regards,
Ervin

MDM Core is activated (although it does not consume license seat, activation is done only for the purpose of getting the valid update credentials for receiving module updates). Each mobile device needs to be activated separately, using the "product activation task" targeted towards the particular mobile device entry. 

Hi N1Md4,
I appologize for my late reply.
Yes we are working on finishing the missing pieces of communication/ documentation.
Sorry for this incovenience.
Best regards,

Hi N1Md4,
I appologize for my late reply.
Yes we are working on finishing the missing pieces of communication/ documentation.
Sorry for this incovenience.
Best regards,

Hello ET_31,
The issue is known to us and we will work on it at the beginning of March 2019, thanks for heads-up!
 

Hello ET_31,
The issue is known to us and we will work on it at the beginning of March 2019, thanks for heads-up!