Jump to content

Zdenko Rendic

Members
  • Posts

    23
  • Joined

Posts posted by Zdenko Rendic

  1. Thank you for your Help, We are using MSP Licence and after creating an ESET Bussiness Account for the Customer, this was not a Solution to create offline license. The Clients dont have Internet but some Destination Ip-s and Ports are open, and it seems that after Version 10 from ESET Endpoint Antivirus, some new IP-s for Activation are required. We had to open some new IP-s from this list, for example this one: 

    13.91.140.245

     

    https://support.eset.com/en/kb332-ports-and-addresses-required-to-use-your-eset-product-with-a-third-party-firewall

    The Offline Mirror Clients are now active again. Case Closed.

    Best regards

    Zdenko

     

  2. Hello, We are using an offline Mirror Policy for around 12 Clients, that are in the same Network, but do not have any Internet Access.

    The Mirror is fine, same Version and can be connected.

    Until Version 9 of ESET Endpoint Antivirus, everything was fine. With the new Version 10.1.2046, all the Clients give the Message:

    your license has expired

     

    I Pushed a new Package where the License is included, also tryed the Activation Task, but it does not Activate the Offline Clients.

    Customer has 109 from 120 Clients activated, all Other Clients are ok, everything is pushed from ESET Protect Server (Vm on Vmware), Version: 10.0.2133 

    What can I do ?  Best Regards, Zdenko Rendic

     

    image.png.a35f36bc93c611306a27031e86f57453.png

     

    image.png.38d45d9fd546bd87e4e3b8af8dda2d99.png

     

     

    image.thumb.png.5e3a02ccdb74f9f6bf6db15adc0eb97e.png

  3. The Past 2 Weeks I saw a Problem with ESET Licensing, somehow it changed from allone by 3 Customers.

    Customer has License : 3AA-CFJ-KUP on the MSP portal, had all 20 Units active, 20/20.. Today i saw it was 03/20 Active, and at the Customers Clients a Msg, that ESET can not Update the Signature. then I saw at Clients ESET Endpoint Antivirus and ESET Filesecurity an another License, unknown to me: 3AA-MJK-DKP

    I pushed a new Activation from the ESET Protect, after that the Clients License changed back to the correct 3AA-CFJ-KUP, and ESET can Update the Signature again. 

    Why did that happen ? I did not Update the ESET Protect Server, version 10.0.2133.0,  also not Updatet the Clients Software.  Filesecurity ist version  7.3.12002.0 and Clients are all version ESET Endpoint Antivirus 10.0.2045.0

     

    Best Regards, Zdenko Rendic

  4. Hello

    Strange things in the last 2 days.
    I have Eset Endpointvirus 8 on my Business HP Laptop on Win10 2004 and ESET Nod32 latest version on Win10 Home on Private Gaming pc.
    Latest Win Updates were made on the Windows PC's and in the last 2 Days i could not work with the devices.

     

    On the Business Laptop Browser could not open, they just had a white window, Outlook had 30 sek to open, "run as admin" needs also around 30 sek to ask me for the Password. The device had 3-5% CPU, free RAM and has an SSD. Deactivating HIPS did not help, I had to deactivate ESET for the device to work again normaly. after that, everything was fast again. 

     

    Home Pc allmost the same, Playing Diablo 3 was not possible, eather I could not Log in the Game or the change from one Map lvl to another took around 40-60 seconds. Other games the same, VERY VERY slow, but CPU ist not at 100%. Deactivating ESET resolves the Issue.

    Any ideas ?

  5. Ok, I found the solution.

    After upgrading ERA 6.x to 7.x I rebootet it once, and I had this Error with the Cert. 
    I rebootet the ERA one more time, and had the Problem that I could not log in, error: "Not connected".
    I used following solution to fix the log in Problem: https://support.eset.com/kb6760/
    Note: this Login problem happens only if you update all the Packages over the Webadmin Console (https://xxx.xxx.xxx.xxx:10000)

    Now the the Cert error was gone and I could Push ESET Agent and Products to the Clients.

  6. Ok thx, I just started one for the test, and it scohuld upgrade to version 7.

     

    But the Problem is that I cant push ESET Agent to a NEW Client, because it gives me the same error, that the Cert or the Cert password is wrong.

    In that case I cant use the component upgrade task, because it is a new client, right ?

     

    image.png.09f2663baa1426ed95d28a242319ca6a.png

     

    The German Error tells me, the the Certificate is wrong or has a wrong passwort....

     

     

  7. Hello

    I Sucessfully Upgradet ESET ERA 6.4.304.0 with the Upgrade task to ESET SMCS 7.0.471.0.  (cent OS)

    After that I wanted to push the new Agent to the clients, but now it needs a Cert-passwort to do so.

    I never used any Password for the certifiacate in the old Version, but now I need one?

     

    image.png.1a892cc1200f90f9e361f8f8bedfb6f9.png

    my Question is:

     -> Is there some standard Password that ERA 6.x uses for its Certs, and what is it ?

     -> or can I just write a new password new for the Cert ?

     

    Best regards

    Zdenko Rendic

  8. Hello

    In last few Weeks I came a long a strange problem: New and fresh installed Windows 10 Clients, with the last March 2018 Windows updates, deactivated Firewall, all working shares, FQDN and so on, the ERA fails to push the agent. ERA is version 6.5.417.0, ESXi VM.

    The error in the logfiles says:
    + mount -t cifs -o domain=*replaced*,username=Admin '//*replaced*/ADMIN$' /tmp/era_remote_deploy_wn_y6OOsPH64GoN6CJP/cifs
    mount error(112): Host is down
    Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
    * [Exit code = 32]
    + LANG=

     

    I noticed that the Windows 10 client with this problem has somehow removed the support for SMB 1.0/CIFS Datashare under the windows features, maybe via Windows update.

     

    image.png.997c60a5fd6a9a5716059eae68b0c535.png

     

     

    After I enable it again and reboot the windows 10 System , the agent push works again:

     

    image.png.8aae91977c81c2fcadc0e4cf301bfc98.png

     

     

    My question is:

    is there a way to fix this problem from ESET ERA side?
    maybe by changing the hightest protocol or something ?

    image.thumb.png.13c370e53a16268941cde3711814f82f.png

     

    I found this older Post from Dimitris Bastas:

    "
    I am running the latest version of ERA (version 6.5.31.0)
    Following MartinK suggestions I changed a line in the file

    /var/opt/eset/RemoteAdministrator/Server/Scripts/UnixWindowsNetworkRemoteInstall.sh

    Specifically the line

    LANG= mount -t cifs -o "${mount_domain_option}username=$ERA_RD_WN_USERNAME" "$remote_cifs_share" "$local_cifs_mount"

    becomes

    LANG= mount -t cifs -o "${mount_domain_option}username=$ERA_RD_WN_USERNAME,vers=2.0" "$remote_cifs_share" "$local_cifs_mount"

    After that i run the command

    /sbin/restorecon -F -R -v /var/opt/eset/RemoteAdministrator/Server

    and I tried to deploy the agent to one of the Windows 7 machines.
    This workaround worked for me and I wish that a change will be made to the ERA webconsole interface, so that a user can tell that a windows computer has SMB version 2, before the agent can be installed remotely.

    Thank you very much for the help.

    "

    I edited this UnixWindowsNetworkRemoteInstall.sh file, and it also working for me, but this is not the fine English art to fix this Problem.
    for exampl,e what happes with this manual edit after an ERA update?

  9. On 24.1.2018 at 7:12 PM, Marcos said:

    Probably there are some "zombie" computers that no longer connect to ERAS. You can use a "Delete not connecting computers" server task to remove them or deactivate them via the ELA portal.

    Hello

    A BIIG Question about "deactivate them via the ELA portal"

    I did this, deactivated the double licenes that were older, after that the ESET Endpoint Antivirus on the client that had the double license was deactivated.

    For me it is not clear which entries I can delete.

     

    Can you tell me which I could deactive on this picture ?
    I deactivated the one with the exclamation mark and the ESET was also deactivated on his client.
    1.thumb.jpg.5dca9601c6a0502097021f5938c61f2f.jpg

     

    Its a Dell XPS 13 Notebook, and it pop-ups every few days double in the ELA portal using 2 Licenses, why is this happening?
    I allready deleted both of them, and Activated his Endpoint Antivirus over ERA, 2-3 days later they are double again.
    The Person takes this laptop from the Office where the ERA is installed to his Home office every day. 

     

    This is not the only Client, there are 3-4 more that show up double, allways the same Clients.

    I also De-installed the whole Eset Antivirus from this CHMOEI02 Notebook, and pushed it again from the ERA, again it shows double.

     

     

     

  10. So for people that have same issue, do the following:
     
    Start VM in recovery Windows Mode, press F8 and look that you get into the CMD
    Launch regedit
    Load Hive SYSTEM (D:\Windows\System32\Config\SYSTEM), give him some random name you want
    ADD following: HKEY_LOCAL_MACHINE\{Loaded_Hive_Name}\ControlSet001\Control\SessionManager\BootExecute
    and HKEY_LOCAL_MACHINE\{Loaded_Hive_Name}\ControlSet002\Control\SessionManager\BootExecute to value autocheck autochk * 

    PvsVmBoot


    Unload hive
    Restart VM

    Update Eset to the newest version

     

    The BootExecute Value is probably there  buz its missing the line under "PvsVmBoot"1.thumb.jpg.c2960c08257bf275e629b4bacf3257f4.jpg

  11. Hello

    I created an offline All-in-one Setup File inclunding the Endpoint Antivirus (6.6.2049.0),  License, ERA Certificate, Parent Group, Agent and self created Policy.

    After that we deploy the File with PDQ Deployment, everything works fine, the client appears in the Eset ERA, has the Product and Agent Installed.

    But the Clients does not get the Policy, I have to log inside the Eset Era to manualy assign the Policy, even if I defined the policy creating the offline setup.
    Why ist that not working ?

    2017-09-06 16_30_46-ESET Remote Administrator.png

  12. Thank you for your answer.

    The Initial Network was Static IP including gateway.
    after a dns change ( and reboot) the gateway was gone...if you dont touch anything in the webadmin under networking, the problem wount happen) 

    My Solutions was following:

    Inside the Webadmin Console ( over port 10000)  I did several things

    - Webadmin -> Networking ->Network Configuration -> Routing and gateways -> Boot time configuration
    I dont know why I had to set this, and why this isnt set automaticly with the Initial Setup, but I put here my default Route on the interface Eth0 with the customer Gateway, and saved. ( Picture 1)
     

    - Webadmin -> Networking ->Network Configuration -> Routing and gateways -> Network Interfaces -> Activated at Boot
    also here, Activated at boot was not set with the IP from the initial Setup, it was only found under "active now"
    I editet eth0 with the same Config from eth0 under "active now" and saved  ( Picture 2 )

    -DNS was allready corretly set

    - Now I Pressed " Apply configuration" under Webadmin -> Networking ->Network Configuration  ( Picture 3)
    and from now on, the gateway was set corretly after an reboot 

    Picture 1.png

    Picture 2.png

    Picture 3.png

  13. After Installation of ESET ERA ( Server Version 6.5.417.0) on Vmware ESXi, everything was fine, Agent and ESET Product Push works.

    I had to change the DNS Server and add Search domains afterwards ( in Webadmin "https://ip-of-era:10000"), and after reboot of the network ( or of the whole Virtual Mashine), I could not deploy the agent anymore. I noticed that for some reason, I am missing the Default Route in the Webadmin -> Networking -> Network Configuration -> Routing and Gateways -> Active Configuration"

    Without the Default Route with the Gateway IP, the VM has no Internet and cant find the Agent Repository. right after setting the Gateway, I have internet with the ESET ERA VM and can deploy Agent again.

    I can Add the default route Manualy, but after a reboot, its missing again.

     

    My Question: How do I configure the Default gateway FIX so it doesnt remove it self after reboot of the network or vm reboot?

     

     

    2017-03-22 14_47_04-Remote Desktop Manager [vmw-veeam01].png

×
×
  • Create New...