Jump to content


  • Content Count

  • Joined

  • Last visited

Profile Information

  • Gender
  • Location
  • Interests
    All about the gains

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. We're using an installer that include both Endpoint Security (v8.0.2028.0) and Full Disk Encryption (v1.2.4.12). After the successful install of both products, we cannot see any EFDE policy set under "applied policy". I was able to find out that our custom EFDE policy was applied by requesting configuration and verify the details that match our custom EFDE policy. Is there a fix coming? We can request configuration, but if a machine is offline then obvious we can't see what policy is applied at that given moment.
  2. 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
  3. Sorry for the confusion, basically I was trying to say that I set a policy in the installer but it doesn't show in computer details (configuration-applied policies) in ESET PROTECT. We have encrypted multiple computers in last couple of days, and none of them are showing any EFDE policy after installing/encrypting with our Endpoint+FDE package. Is there a way to force the computer to show it's EFDE policy in ESET PROTECT, just a bit confuse on why it wouldn't show the policy in the first place?
  4. We're using an installer that include both Endpoint Security (v8.0.2028.0) and Full Disk Encryption (v1.2.4.12). I included our custom EFDE policy in the installer but it's not applying to the machines, therefore I had to manually apply the policies after the machines get encrypted. Is there any issues in applying our encryption policy after the system gets encrypted? My thoughts is that the default policy will override my policy that I applied after the system gets encrypted, or will the policy change as long the system checks in? Thanks,
  5. I appreciate the response. I ended up calling support, and we figured out the hostname in the certificate was the issue. The issue was for some reason is the hostname had to be change to work (hostname was correct initially), but we just opt to use the IP address instead for simplicity. There's too many variables to say what caused the issue since our environment has drastically changed within the last few months.
  6. Console: CentOS7 ESET Management Agent 8.0.2216.0 ESET PROTECT Server 8.0.2216.0 ESET Rogue Detection Sensor 1.0.1079.0 Client: Windows 2016 ESET File Security 7.3.12002.0, ESET Management Agent 8.0.2216.0 Errors: Error: VerifyDnsSubjectAltName: Hostname does not match any supported record in certificate SubjectAltName extension Enabled:0, EnabledFallback:1, failed with error code: 14, error message: Connect Failed, and error details: The client data isn't showing in the cons
  7. Hello I have a client computer that's running the current updated version products below. I removed the EFDE policy, then applied a decryption policy (disable encryption). The client is showing the decryption policy as actual, and encryption is active. I had the client reboot to just be sure, and still no changes. Only thing I can think of doing using registry editor for 'ESET FDE AIS Service'. Reason for this change is because we're migrating to a new console, so we have to decrypt the systems then encrypt them again on the new console. ESET Endpoint Security 7.3.2044.0
  8. 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
  9. Are there ways I could have more visibility of these machines with EFDE in the console?
  10. 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
  11. I'm not sure if these things are in the works, but there's not really any visibility on EFDE in ESMC. Could we have some way of monitoring these clients with EFDE in the dashboard/reports such as password uses left on each machine, general information to show during audit? Thanks,
  12. I'm looking to perform a server migration using same IP (https://help.eset.com/era_install/65/en-US/migrated_database_same_ip.html) while upgrading the server OS and ESMC version from 7.1 to the latest 7.2 . The current ESMC is on CentOS 7, and I was wondering if there's any issues if I go CentOS 8? Keep the ODBC driver v5.3.10 and MySQL v5.7, and is there any other recommendations? This is my first time performing this task.
  13. We only have one EFDE policy currently applied to the clients, and "apply" flag is set to all fields in the policy.
  14. I made changes to the FD Encryption policy almost a week ago, then test the password recovery on a client machine and it still has the old settings. I double checked the client machine is assign to the policy. The policy is "actual" on the client machine, but it acting like there's no changes made. I've made multiple changes to the password policy, and I've tested all the changes made with all resulted under old settings. ESET Full Disk Encryption version
  15. Looking back in the trace logs, it looks like "No detected log filter or realm change" started to occur a couple months ago after we Update Product ESMC to v7.1.503.0 . I'm noticing these same trace logs in multiple machines when trying to upgrade the agents/applications even the ones that were successful and currently connected. On some machines, I tried to push out the tasks but it fails and that's when I checked the trace logs to find out I'm having the same errors across multiple machines. I saw error 14 and connection fail in one of the trace logs right before it was getting the "No
  • Create New...