Jump to content

LesRMed

Members
  • Posts

    184
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by LesRMed

  1. There is no policy that disables the notification. I had the warnings showing before I started all of this, and I still have two laptops that are showing the warnings (that I haven't tackled yet).
  2. If that's the case, why am I no longer receiving the warning in the console that says "Missing support for Azure code signing"? And if I'm reading the log correctly that I attached earlier, it's failing because it doesn't have ACS support.
  3. Well, after further research, it appears that KB5006728 can no longer be installed. The error message from the failed install shows that the failure is expected "If you are installing this update on a device that is running an edition that is not supported for ESU" and references KB4497181. So, unless you paid for ESU support AND installed KB5006728 prior to 1/10/23 (when ESU support ended for 2008R2), you're pretty much screwed. The funny thing is, I'm no longer receiving the "Missing support for Azure code signing" warning in the console for any of these servers. @Marcos Any idea why?
  4. Well ! I installed that on all of them on Friday, but it's not showing up any of them now. I just did it again on one of them and it looks like when it's installing after the reboot, it fails and the changes are reverted. Back to the drawing board. Thanks @itman.
  5. I'm trying to update ESET Server Security on five 2008R2 servers, and they're all failing; it doesn't matter if I do a security product update task from the cloud or if I try to manually run it from the server. They all fail with: "SoftwareInstallation: Installation failed with Fatal error during installation. Error code 0x643 (0x643), The app that you are trying to run is not supported on this version of Windows. See https://go.eset.com/acs23, see software-install.log for more..." I have verified that KB4474419 and KB4490628 have been installed. Any help would be greatly appreciated. software-install.log
  6. Just out of curiosity, is there a reason you don't want to update to 22H2? It's still Windows 10.
  7. I sent @Marcos a pm on Friday about this.
  8. You can post the logs here. Attachments are only viewable by ESET staff.
  9. Just FYI, it doesn't trigger anything when I access it or even add it to the shopping cart.
  10. I'm not sure what the size limit is on the forum, but anything uploaded here can only be seen by ESET staff. The other option is to upload it to a file sharing service and drop @Marcos a PM with access instructions.
  11. Run the ESET uninstaller in safe mode. https://support.eset.com/en/kb2289-uninstall-eset-manually-using-the-eset-uninstaller-tool Keep running it until it finds nothing. Then reinstall.
  12. You might want to verify that 64 bit Office is installed. From what I've seen, 32 bit is the default version that's installed unless you specify 64 bit. You can verify it by opening up an Office product, say Word, click on File-->Account and then click About Word (or Excel or whatever you opened). The top line will show if you're running 32 or 64 bit.
  13. I guess I missed a word...we NOW have one license number...
  14. I believe that is correct. I did the same thing and upgraded from onsite to Entry. We have one license number and just have to adjust the quantity up or down as needed.
  15. I'm also in the US, but I just noticed that it redirects me to ESET Home.
  16. I'm not having any problems with the MSP Admin portal.
×
×
  • Create New...