Jump to content

Sameer

Members
  • Posts

    19
  • Joined

  • Last visited

About Sameer

  • Rank
    Newbie
    Newbie

Profile Information

  • Gender
    Male
  • Location
    Nepal
  1. create a run command with the following : net start "ESET Service" and apply the run task to the effected machine seems to be working in my case.
  2. Create a "Deploy Agent first (Agent script installer)" - under Agent Configuration select the working agent policy that uses the correct EP Certificate and IP / Hostname (preferred for such scenario) and using GPO deploy the .bat to your endpoint - this script will uninstall and then reinstall the agent.
  3. Third party email gateway (on-prem) huge email Q with deferred message 451 4.7.1 ------ > MS Exchange 2016 (running on-prem Windows Server 2016) -----> ESET for Exchange 7.3.10011.0 (default setup) : any suggestion as to how to resolve this issue as am new to emsx
  4. run services.msc - stop ESMC Management Server and set it to manual - execute the ESET Protect 8 setup
  5. Download the .iso for the new version https://download.eset.com/com/eset/apps/business/era/allinone/latest/all_in_one_iso.iso - set esmc service to manual from services.msc - restart the machine - upgrade esmc using the downloaded .iso
  6. prepare v7 esmc and deploy agent to all v5 endpoint that can communicate with the v7 esmc (good to move to v7 as v5 is only covered under basic support, however if you want to continue to with v5 ( which i have not tired as yet) then creating custom package instruction is attached) create a shared read only folder accessable to all the endpoint download the fixer from and save it to the above shared folder (replace eea with ess and 32bit with 64bit were necessary) hxxp://repository.eset.com/v1/com/eset/tools/certfix/v1/latest/eea_nt32_enu.exe hxxp://repository.eset.com/v1/com/eset/tools/certfix/v1/latest/eea_nt64_enu.exe from the v7 esmc - task - client task - operating software - run command - new client task - setting - type the following "powershell -command "& {(Copy-item -Path '\\shared folder\v5fix\eea_nt64_enu.exe' -Destination '%temp%\eea_nt64_enu.exe');(Start-process '%temp%\eea_nt64_enu.exe' -NoNewWindow)}" > C:\ees_fixer.log" with double hyphe removed and choose target command above will copy the eea_nt64_enu.exe from the shared folder to local c:\windows\temp and the ees_fixer.log under c:\ ack : Rhesa from Indonesia for providing input for the test and the v5 custom package instruction how-to-push-v5-rev-1.1.pdf
  7. As suggested by Marcos - download the esetuninstaller.exe and copy it to c:\ > start the machine in safe mode with command > then at c:\ execute as follows > c:\esetuninstaller.exe /force (will uninstall everything ESET) OR c:\esetuninstaller.exe (will give option to choose what to uninstall - reboot in norma mode
  8. Since Anti-Theft is not part of the new Internet Security which was included in smart security earlier, so customer wanting to continue using anti-theft after the expiry of there current smart security does not want to go for new smart security premium and continue to use new internet security - what then ?
  9. C:\\Windows\\SysWOW64\\config\\systemprofile\\AppData\\Local\\ESET\\ESET Mail Security\\Quarantine - is it safe to manually delete the content under this folder ? its about 10GB +, deleting it from within the EMSX GUI does not make any difference.
  10. Product - ESET NOD32 Antivirus 9.0.318.0 Signature 12499 Disable SSl/TLS Procotol Filtering - Restart - Enable SSl/TLS Procotol Filtering So far no Protocol Filtering Problem. NOTE : Message back again
  11. Download ESET AV Removal Tool - hxxp://support.eset.com/kb146/ Boot into Safe Mode and run the downloaded executable
  12. If you can push a no password for client setup xml from the ERA to the client then you should be able to remove the client setup password
  13. I have always appreciated ESET design of install, configure and work perfectly behind the scene approach and i hope this will continue. My only wishlist is as follows with ref to consumers series : 1. Activation from within the software to provide message like those when using the ESET online activation form if the activation process fails 2. ESET SysRescue to do away with Windows AIK / AID and come up with a different and simpler approach 3. Disable Auto-run during installation and then an option to enable later if required
  14. Could anyone from ESET please confirm if this is recommended and safe workaround for servers running EFSW v6? This is only my workaround based on my test with slow file opening issue on a EFSW v6 running on a WFS and not a recommend solution. I did try the disable network drive options but there was no improvement and waiting for ESET to resolve the issue.
×
×
  • Create New...