Jump to content

FRiC

Members
  • Posts

    83
  • Joined

  • Last visited

About FRiC

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    Thailand

Recent Profile Visitors

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

  1. And if a password is set, you should use the /qb switch to add the password. MsiExec.exe /qn /norestart /X{GUID} /qb password="your_password"
  2. I had the same experience. Upgrading to 11.0.2044 by selecting computers to upgrade, and selecting Restart when needed. The install finishes but clients don't reboot, as if Restart when needed was not selected. I didn't check if there was a countdown screen though. This is both Windows 10 and 11, latest CU. Edit: I'm using Endpoint Security.
  3. Just upgraded to ESET PROTECT on-prem 11, and the single Windows 7 computer in my domain retained the versions as previously: ESET Endpoint Security 9.1.2063.0, and ESET Management Agent 10.1.1292.0. Other computers are already on EES 11.0.2032.0 and Agent got upgraded to 11.0.503.0. Hope this helps.
  4. Thanks, I think it was a general Internet issue. The normal update also goes on forever. If this continues I'll have to check which server/route the updates are taking.
  5. From the ESET PROTECT Dashboard I click on Update installed ESET products in the Component version status panel, then select clients from there, and whether to reboot or not after the update is finished, and a software install task is created. There are two tasks in my screen shot, one is to reboot and one not. They've been running all day today and thankfully are almost done now.
  6. Sorry, forgot to mention we're using PROTECT On-Premises. Yeah, normally I just click on Update installed ESET products and it automatically creates a task. Well, I've been at this the whole day and it's taking anywhere between 1 to 8 hours for the task finish and reboot the computer. Some are still running right now.
  7. Hi, whenever a new ESET version is released we always manually create upgrade tasks so we can control the upgrades. It usually takes a few minutes for the task to finish and for the clients to reboot, but this time it's taking literally hours and hours for the task to finish. Is there something special about this upgrade, or it's just some random slow Internet issue? Thanks. ESET Endpoint Security and a mix of Windows 10 and 11 Pro. Latest CU.
  8. We were having issues with printer sharing which seemed to be fixed by using the pre-release channel, but when it automatically upgraded to 1.0.2050 the problem came back. Still working with the users to track the issue down. Our non-pre-release channel systems still have not gotten the newer firewall module.
  9. I tried enabling pre-release and it works for me. I notice the firwall module is now 1439 7/18/2023. Previously it was 1438.2 7/13/2023.
  10. For me, users are having issues printing to shared USB printers. Symptom is that the client machine shows the print job spooling for a long time but eventually (5-10 minutes) does print out. Workaround is to turn off printer spooling on the host machine. Not even sure if this is related to ESET 10.1 yet but we've had no other changes this week.
  11. Yeah it's happened twice this month, I have scheduled scans set at noon so it shouldn't try to start another scan, and it doesn't happen every time either. Thanks, I'll raise a support ticket.
  12. I forgot to write that this is ESET Endpoint Security 10.0.2045.0 running on Windows 10 Pro, latest update.
  13. I've been having a small issue recently. I have scheduled scans for every Tuesday and Friday at noon and it's been running fine, but once a while as the image shows, it completes, but another entry says Scan did not run. On the computer itself ESET also says scan is completed, but the icon is still spinning and the tooltip says "Scan is running...". Is this a known issue or am I missing something obvious? Thanks in advance for any help or insights.
  14. Thanks Marcos, yeah after a while everything was back to normal. Unfortunately later in the day I'm showing 20+ EPNS unreachable again.
  15. Do you actually have to reboot? Previously I was showing 40+ computers with the issue, now everything is back to normal on the management console and in the application, but I notice the tray icon is still showing the orange exclamation mark.
×
×
  • Create New...