Jump to content

Mr.Gains

Members
  • Content Count

    13
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    USA
  • Interests
    All about the gains

Recent Profile Visitors

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

  1. 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
  2. Are there ways I could have more visibility of these machines with EFDE in the console?
  3. 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
  4. 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,
  5. 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.
  6. We only have one EFDE policy currently applied to the clients, and "apply" flag is set to all fields in the policy.
  7. 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 1.1.0.0
  8. 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
  9. I double checked for duplicate and tasks on the client, and there's none. The status log was last updated over 24 hours ago, so that would mean the ESMC Agent isn't running correctly.
  10. I tried running as admin on ecmd at the following %programfiles%\eset\$ESET product name , but that's where it would pop up then close immediately or not pop up at all.
  11. Authorization method: Advanced setup password. I'm having an issue with a client machine generating "Registration to Windows Security Center was not successful", so I'm trying to use the eCMD for /registerav command since I tried other methods that didn't work.
  12. I'm having an issue where I set the policy in the ESMC to enable advanced ecmd commands for a machine running ESET Endpoint v7.2.2055.0. I try to run eCMD through both file path and CLI, but it would pop up then close immediately.
  13. One of the client isn't connecting to the ESMC, and in trace log is generating errors : "No detected log filter or realm change" right before 4am. Status log shows no errors, modules are being updated regularly, and I checked the event viewer that shows nothing on the server that could be related to the problem I'm having. One thing I noticed is that there are trace log zip files generated every day before it stop connecting to the ESMC. ESET File Security v7.0 is currently on the client machine.
×
×
  • Create New...