Jump to content

Glitch

Members
  • Content Count

    35
  • Joined

  • Last visited

Profile Information

  • Location
    Netherlands

Recent Profile Visitors

410 profile views
  1. Correct but it will bring an additional burden. We had written consent of eset that upgrading to the latest version was not directly needed but eventually. Last week you even have updated the KB as you are still dealing with it and now eset is going to send out this notification in times that on-site hands are virtually impossible. It is so hard to convince our customers to stay with eset we have almost 8000 endpoints which will give this warning those 8000 will switch to another solution due this issue.
  2. All people following this topic the show is not over. As per March 26th all certfix version 6.5 clients will go to yellow state that there is a new version available. All endpoints 6.5 which does not had certfix will go to status red! Welcome to ESET in quarantine times they will put us up with more work. Customer friendly as they are.
  3. I think the fix for ESET 6.5 caused another issue: 1. Currently we see the event log of windows be flooded by : Error while updating status to SECURITY_PRODUCT_STATE_ON. which is caused by the windows security center as they don't see a registered product. 2. Registering the product using ecmd.exe /avregister will end in a : execution failed command. 3. Only way to resolve this is to reinstall the complete 6.5 version. Is there another way to force eset to register against windows ?
  4. Hello?? Anyupdate we can’t deploy or can we invoice eset for the costs?
  5. After the Certfix issue of ESET , ESET released a new Endpoint Antivirus version of 6.5 6.5.2132.5 however a new bug was introduced causing automatic roll out to fail. What happens is the following: We install the MSI using a command line script and cfg.xml next to it for all the default settings. It doesn't matter if the install is started via commandline or manually but the following happens: 1. ESET installs with no issues 2. When the software is activated the update failed because no username and password in the license (this is correct because it is a local install and the update mirror is local and the license does not contain the username and password). In the CFG.xml a local mirror location has been designated. 3.You open Advanced Settings and check the update folder which is correctly listed as according to the cfg.xml along with all the other settings (although the profile name is weird). Anyway when you press OK to save the settings 4. press update the system updates from the local mirror. withou any issues. The bug is that when you install ESET with the cfg.xml it sets all the settings as according to the cfg.xml file but it does not activate the settings untill you manually open the settings and press OK! This is an issue as we have 1000 PCs that we need to do manually which is not an option at this time.
  6. 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.
  7. @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.
  8. 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
  9. Indeed some clients not all also ask for a password when entering in to advanced settings! after applying the patch. How to solve this?
  10. 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???
  11. 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.
  12. 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.
  13. Yes there is you patch that you need to run depending on the network you can push it via a gpo for example.
×
×
  • Create New...