Jump to content

Topher

Members
  • Posts

    11
  • Joined

  • Last visited

Posts posted by Topher

  1. Tried 2 other browsers besides Firefox, where I normally run it, same issue. I cannot add a scheduled custom task to any existing policy, without it defaulting name to Automatic update after dial-up connection, which is greyed out.

     

    ESET Security Management Center (Server), Version 7.1 (7.1.717.0)
    ESET Security Management Center (Web Console), Version 7.1 (7.1.393.0)
    Copyright (c) 1992-2019 ESET, spol. s r.o. All Rights Reserved.

    Microsoft Windows Server 2016 Standard (64-bit), Version 10.0.14393.3750

    Connected Clients: 162
    Active Licenses: 1

    Installed Components:

     
       

     

     

    Update module

    1021 (20200218)

    Translation support module

    1805 (20200619)

    SysInspector module

    1278 (20200609)

    SSL module

    1048 (20200608)

    Push Notification Service module

    1061 (20200402)

    Configuration module

    1822.3 (20200122)

    ESET hotfix.jpg

  2. Yes, I am not messing with the default tasks. Only trying to add back the Scheduled task I had in my policies, before it went haywire on last update. I open/edit an existing policy, go to Settings, Tools, expand Scheduler, click Edit, Add, choose the option from drop down "On-demand computer scan", and Task name remains greyed out, and says "Automatic update after dial-up connection" under task name, and you cannot change it.

  3. Due to the issues with previous release shutting down endpoints, after a scheduled scan in a policy, we upgraded the "hotfix" to 7.3.2036.0. I decided to create a Test Policy with a Scheduled Scan, Take no action after scan, and it WILL NOT let you name the task...it defaults the task name to Automatic update after dial-up connection, and it does not initiate a scan, nor does it let you create the task name, as it is greyed out.

    Anyone else seeing this?

     

     

  4. 18 minutes ago, Campbell IT said:

    I just experienced this on my machine. Fortunately, I was in the office today, so I was able to stop it from rebooting. My big concern is that we have had a few computers automatically upgrade themselves without any intervention on our part. Is there a way I can prevent any other machines from automatically upgrading? I currently have 3 machines on 7.3 and would like to keep it that way until this issue is fixed. I have a lot of people working remotely and not much manpower available to turn machines back on.

    In your policy, navigate to Update>Settings>Updates>Program Component Update....Update mode should be set to Never Update

×
×
  • Create New...