Jump to content

Glitch

Members
  • Content Count

    29
  • Joined

  • Last visited

Profile Information

  • Location
    Netherlands
  1. It is because a large majority of the clients we manage is still using windows XP, they also use the NANO updates as it is not a single network. We are an MSP. Our new installs are 7.1 or 7.2. As ESET is also terible in managing high latency connections we can't use the ESMC as there are too many timeouts. I already explained this a couple of times on calls with ESET HQ in Bratislava and also when I visited the HQ. So are we planning to stay on 6.5 , no but upgrades will take time and will cost time and need to be planned we can't force our clients at this moment as their connections don't allow it to receive large amounts of data such we need months. Next to that the new updates are larger than the old updates. Yes yes we know the latest the greatest, for customers we do 24/7 SOC services we only have the latest versions install and so but we are in a specific sector that it is not possible. And yes I agree updating is better and so one but that is all for another time. At this time it is important that we can: 1. Rectify all machines back 2. Start protection again. 3. Get them updated.
  2. @Marcos What about the endpoints that request a username and password when you go to advanced settings after applying the patch? Also any update if we NEED to update after applying the 6.5 patch? Like 10000+ workstations updaten without any era would take a few months.
  3. EES: hxxp://repository.eset.com/v1/com/eset/apps/business/ees/windows/v6/6.5.2132.5/ees_nt32_enu.msi hxxp://repository.eset.com/v1/com/eset/apps/business/ees/windows/v6/6.5.2132.5/ees_nt64_enu.msi EEA: hxxp://repository.eset.com/v1/com/eset/apps/business/eea/windows/v6/6.5.2132.5/eea_nt32_enu.msi hxxp://repository.eset.com/v1/com/eset/apps/business/eea/windows/v6/6.5.2132.5/eea_nt64_enu.msi
  4. Indeed some clients not all also ask for a password when entering in to advanced settings! after applying the patch. How to solve this?
  5. can you explain what you mean with this that they NEED to upgrade??? We have already applied the certfix on Monday and that is working and are using it on a couple of thousand endpoints to bring them back. What do you mean that we need to upgrade???
  6. I understand just trying to assist in this matter we have issues and thousands of endpoints. Although we had a version that was able to fix with certfix they create but still a lot of manual operations.
  7. Workaround is to set back the system date of that machine to February 6th, after that ESET will be alive again and you can upgrade via the console. Keep in mind that database applications sometimes can't handle date changes. Other options is to set back the date, ESET will recover, press Update now and the fixed will be installed, reset the date back and upgrade.
  8. Yes there is you patch that you need to run depending on the network you can push it via a gpo for example.
  9. In that case make a user with admin rights and run it via a batch script same result.
  10. you can deploy it via gpo using powershell to run it.
  11. We have been testing the fix since this morning and seems to work. Run it as an administrator and it will instantly fix the ESET instance.
  12. I would really recommend to ESET to stop saying please upgrade to version 7 etc etc yes yes we know the latest and greatest but it is frustrating as it does not help us at this moment. You are saying that with version 7 this could never happen although version 7 also has bugs. Just keep to the facts and release fixes. for example please upgrade how? Via the era does not work! Because 6.5 is not working so you need to set back the system date first which causes a database crash if you have such programs so please keep the facts make a fix we will loose business due to this.
×
×
  • Create New...