Jump to content

Lockbits

Members
  • Content Count

    68
  • Joined

Profile Information

  • Location
    Chile

Recent Profile Visitors

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

  1. Hello guys, We've a customer where we installed the MDM with public IP address. The device is enrolled correctly and reporting to console however some hours later the Android device stops reporting back to console. If we open ESET for Android in the mobile then immediately it report back again but some hours later the same problem occurs again. It's like something in Android is restricting the connection to console when ESET is idle in the background. Re enrolling the device doesn't work because it said it's already connected. How can we avoid this behavior? Thank you.
  2. Hi MartinK, Apparently the problem is because old agent configuration was password protected. We are trying to make a custom bat for deployment but for the moment it's not working. I password protected my agent with the same password so I can test the bat without going to the customer but not luck. I tried to put the password with and without " and it's not working. If I look at the .ini created by the bat I can saw that password is within the file but agent is not reinstalled with new configuration. ESMCAgentInstaller2.1.rar
  3. Hi Martin, I double checked and indeed it's the problematic computer. We didn't found the ra-agent-install.log. We searched all the disk with an administrator account. As you suggested, we created a live installer (the .bat) and ran it in the problematic computer. The result was the same, PC doesn't connect and old settings and certificates are preserved. I deployed the agent using the server task to computers were no agent was installed before and those computers connected right away. Unfortunately this problem persist in 7.1 as configuration and certificates are not overwritten with the new ones. What others options do we have other than uninstall and install the agent manually per computer? Thank you.
  4. Hi guys, The problem is within the certificate and that agent installation using server task is not overwriting the agent and configuration. For example, in task I specified the host name and not the IP and if I see the log I realized that even that parameter wasn't changed. I'm going to try with GPO. Logs.rar
  5. Hello guys, We've a customer that was using and instance of ESMC 7.1 along with 7.1 agents. The server got damaged so we've installed a new instance of ESMC 7.1. The server has the same hostname and IP address but computers are not connecting as the certificate is different (we don't have a backup of original certificate). We tried to deploy agent using a server task and although the task finished successfully, the computers are not connecting to new instance. Which parameter can we use so agent is reconfigured with the new certificate? If we deploy agent using GPO, will installed agent got updated with the new certificate? Thank you.
  6. Lockbits

    EFDE and SSO

    Hello guys, Is there any plan to add SSO feature for EFDE like EEE has? In our experience most companies wants to use the same credentials of AD for pre boot so users doesn’t need to use more than one credentials. Thanks.
×
×
  • Create New...