Jump to content

offbyone

Members
  • Content Count

    96
  • Joined

  • Last visited

Profile Information

  • Location
    Germany
  1. Hello. We have the problem that the confirmation e-mail for the EBA account was not delivered correctly due to a typo within our e-mail systems. Meanwhile we have corrected the typo however there is no way to trigger a resent of the confirmation e-mail. When trying to login to EBA we get the message: Account not activated Your account has not been activated yet. When trying to do the "Forgotten password" procedure no e-mail is sent, Trying to recreate the account with similar username (e-mail) is possible however also there is no confirmation e-mail sent. Catch22.
  2. We have successfully implemented haproxy in front of ESMC in a test environment. Our first attempt to run in http mode failed, as we found that ESMC agent does not seem to send back valid HTTP responses which comply to http standards. But we further found that this is not a problem with what we want to achieve (checking validity of the client cert on the reverse proxy side), as TLS bridging with haproxy also works in TCP mode. Following is the relevant part of the haproxy config: frontend esmcAgentFE mode tcp option tcplog bind *:2222 ssl crt /etc/haproxy/ssl/crt/es
  3. No its not a sysprep image, its the default image. It is deployed via autounattend.xml by WDS. The OOBE phase is running of course on first logon but it's automated.
  4. @FRiC THX for confirmation. I wasn't sure if it is something special to our environments. Till now we deployed about 100 new clients in 3 different customer environments and its the same with all of them.
  5. I suspect that not many customers will be faced by this problem, as there are not many which do a fully automated deployment of computers including os and apps. In most cases a user has logged on at least one time before ESET is installed.
  6. All clients are installed unattended via offline installer which include Agent and AV. The installation is done via GP script.
  7. Hi. Is this a known issue that after deploying ESET AV on a newly deployed computer, "Real-time file system protection is non-functional" error is present until a user logs in for the very first time on that machine. Rebooting does not fix it, someone has to login first. We have this on all newly deployed machines. Regards.
  8. Simple question. What is the recommended product to install on Windows Terminal Servers (Remote Desktop Session Hosts)?
  9. Will this ever be fixed? On every customer we implement ESET which uses Deutsche Telekom as provider it is a mess to get an offline repo, as it nearly always fails with errors. Sometimes you need about 20 attempts to get a repo which is complete. Cheers.
  10. Changing FF policy to "Certificates" : { "ImportEnterpriseRoots" : true, "#Comment" : "Don't use OS certificate store" } seems to solve the problem.
  11. @itman THX for sharing the link to Mozilla website.
  12. I wanted to say that we started with 7.3.2036.0 and are still on that version. So I wonder why the ESET CA is present in FF store. When we started with ESET we were on FF ESR 68.06. and are now on FF ESR 68.10. Cheers.
  13. Ok thing getting clearer now. In this file you enable FF to use Windows cert store but we set "Certificates" : { "ImportEnterpriseRoots" : false, "#Comment" : "Don't use OS certificate store" } in policy file to disable cert store of Windows. Maybe this is conflicting. Any idea why ESET CA was also present in FF cert store before? We are still using the initial version and did not upgrade ESET so far.
  14. Browsing a https site in IE and inspecting the site cert shows that it was signed by ESET CA. Browsing the same https site in FF and inspecting the site cert shows that it was not signed by ESET CA Cheers.
  15. @itman We use latest ESET version and found ESET CA to be present in FF cert store. However after removing it is not re-added to FF cert store. Is this expected behaviour?
×
×
  • Create New...