Jump to content

Steeltown

Members
  • Posts

    3
  • Joined

  • Last visited

About Steeltown

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    Canada
  1. Hello Eset community, I've been toying around with the best way to get my WFH users to grab ESET updates and keep visibility in the ESET console for the machines. We have a couple of sites where we will be using our ESET, but they are not joined to our network in anyway, And also with the Covid rush to WFH, some users have ended up with their desktops at home for an extended period of time. C level has put a hard no on giving everyone at home a VPN to connect and get updates. Is this an ok approach to take? I have been looking at the known networks profiles, and having it fall back to a WAN address for updates with a whole punched int he firewall to the ESET management server. does it need more then just 2222 for the updates AND reporting? On top of that, any articles that clearly lay out the steps of creating a new update profile that point to the WAN address? As always, thanks in advance!
  2. Thanks MartinK! Then my understanding is the file security component is competently separate from the ESMC console even though they are on the same server. In that case it i can feel free to deactivate the file security and then re-activate with the group license without any worry of blowing up the ESMC correct??
  3. Hello ESET forum people! I have taken over the ESET management in my environment, we had to renew licenses for January 6th 2020, Did that, added some, things went well for the most part. ESMC is installed on our file server, not what I would have done, but it's there and here I am. This server also has Eset File Security installed on it. All the endpoints picked up the new license and are good for a few more years, however the File Security that is installed on the ESMC expired on the 6th. looking in the console it shows the license was not activated by ESMC, I assume this is because this is in fact the ESMC. Maybe it cannot activate itself? OR perhaps this machine is activated differently because it is the ESMC? The public license ID is a much different looking set of characters then our regular license that shows on all the other devices. Product Name ESET File Security for Microsoft Windows Server Expiration Date 2020 Jan 6 07:00:00 Activated by ESMC No Managed by ESMC No License Type PaidBusiness Our ESET license shows as "ESET Endpoint Security + File Security" with a normal 9 digit public ID. Shouldn't this license be able to activate the software? When I right click the alert, and create an activate product task on it, select my license (with open seats) it fails. I get the trace message "Task Failed in the security product" under the executions report. It's running in a grace period at the moment. Any help would be appreciated! Thanks,
×
×
  • Create New...