Jump to content


  • Posts

  • Joined

  • Last visited

About Mr.Gains

  • Rank

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. 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?
  2. We're experiencing an issue where a client installed another drive on their machine, and it's not recognizing the disk for encryption. If we disable this disk we can do the encryption. I made sure it was unencrypted, and it's empty and tested with a test file (to have some sort of size to recognize it's unencrypted). Disk with issue: SHGP31-1000GM-2 ESET products: ESET Management Agent 8.0.1238.0 ESET Endpoint Security 8.0.2028.0 ESET Full Disk Encryption Errors: When turning back on the Disk after installing EFDE : "Unable to start the system due to a problem accessing vital encryption data. Reason Code: 2 Meta Data is incorrect" When enable all drives then install EFDE, the system just sits there "not encrypted, data is not protected" after the first restart (before setting password which is where we're trying to get to). Only error I see is the recovery data is not in sync with server in the status, which I uninstall/install EFDE and the error shows up after (I waited for alerts to clear before the first restart). Logs show that it retrieve the license and that all disks are supported. Did I miss something or is the new disk not compatible with EFDE? Thanks,
  3. Thank you Marcos for trying to reproduce the problem, we think it's something on IIS install end now. We resolved the issue by creating a sub-directory manually, for some reason the path wasn't created initially. We'll check on this again on the next machine that we install ESET on.
  4. We're experiencing an issue where trying to install IIS after ESET Endpoint Security v8.0.2028.0 on new clients. The only way around is to uninstall ESET then install IIS, but we're not experiencing this issue on our servers ( File Security v7.3). Is this a known issue? It has recently start occurring where we have to uninstall ESET, Install IIS then re-install ESET.
  5. 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.
  6. 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
  7. 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?
  8. 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,
  9. 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.
  10. 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 console, so I tried the Agent live installer with no results. We've tried creating a new certificate, re-installing the all-in-one installer, and tried local, remote, and website deployment with no results. Both the client and the console can ping each other. What are the other possibilities or areas do I need to look at in resolving my issue? It seems this issue occurred after upgrading to ESET Protect from ESMC. Thanks,
  11. 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 ESET Full Disk Encryption ESET Management Agent 7.2.1266.0
  12. 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
  13. Are there ways I could have more visibility of these machines with EFDE in the console?
  14. 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,
  15. 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,
  • Create New...