Jump to content

ScottWStewart

Members
  • Posts

    71
  • Joined

  • Last visited

Posts posted by ScottWStewart

  1. I updated all my client machines to ESET Endpoint Security 7.3.2044.0 this morning and need to restart the workstations to complete the installations. It's right in the middle of the day and I can't reboot the users workstations until tonight when they go home. Will my users computers still be protected until the task I created to reboot at 11pm runs? I really don't have any other choice.

    Thanks

  2. Solved. Somehow the Apache HTTP Server disappeared from the server with the last Windows 10 update to version 2004. Tech support downloaded the all-in-one installer and installed it. I figured it was odd when I looked in the services and Apache was gone. I tried to fix the issue by installing Apache but that didn't work. I figure I installed the wrong version, version 8. The version in the all-in-one package is 7. Thanks to Tech Support! I would have figured it out, but it would have taken me a lot longer than it did for support to fix it.

    Windows updates can do some strange things to PCs. I am thinking about installing the server on Linux. Any advice on that?

  3. Windows did an update on the Workstation that the ESET Remote Web Admin Console is hosted on and now I get the error:

    This site can’t be reached "IP Address" took too long to respond.

    ERR_CONNECTION_TIMED_OUT

    The windows update is:

    Windows 10 Pro

    Version 2004

    Installed on 7/9/2020

    Experience:  WIndows Feature Experience Pack 120.2202.130.0

    How can I access the server app to enable the web console?

     

    Thanks in advance!

    Scott

  4. On 1/29/2020 at 8:16 PM, Cp3p0 said:

    Hi Scott,

    Just my 2c...

    If you've got sometime to trouble shoot I would recommend giving the Manual Uninstaller tool a shot.
    https://support.eset.com/en/kb2289-uninstall-eset-manually-using-the-eset-uninstaller-tool

    You'll need to reboot your computer in Safe-mode then try again. 

    This occasionally works for me.

    I successfully uninstalled ESET using the uninstaller tool, rebooted and ran the installer again and I didn't have any Malware issues preventing the fresh installation of ESET Endpoint Security 7.2.2055.0! All is well now and running up to speed. Thanks for all the responses guys. Cp3p0 thanks for the solution.

  5. On 2/3/2020 at 2:41 AM, Marcos said:

    Yes, it will work with msi installers. In case of home products, Live installer generates install logs automatically and they are also collected by ESET Log Collector for further perusal by ESET staff.

    Marcos,

    I've been very busy with doing some hardware updates on the desktops here, but hope to follow the procedure you laid out for me this afternoon. Again, thanks for the help!

  6. 18 hours ago, Marcos said:

    Please carry on as follows:

    1, Configure installation logging as per https://support.eset.com/en/kb406-how-do-i-generate-an-installation-error-log-for-windows-eset-products
    2, Start logging with Procmon prior to launching the installer and stop logging when the installation fails
    3, Save the Procmon log and compress it.
    4, Collect logs with ESET Log Collector.

    Finally upload all 3 logs (the install log, Procmon log, ESET Log Collector logs) here.

    Will this logging program work with the business version of the ESET client?

  7. I am trying to install ESET Endpoint Security on a workstation running Windows 7 Pro, I am going to upgrade the OS to Windows 10 Pro after the ESET update however when I go to install ESET I get the error that it failed to install, this could be because your system possibly is infected with Malware. Then it gives me the option to scan for malware and it says it found malware and cleaned it. But when I go to install ESET again it gives me the same message. I am updating from ESET Endpoint Security 7.0.2091.0 to ESET Endpoint security 7.2.2055.0

  8. On 12/26/2019 at 11:44 AM, MartinK said:

    In case just hostname or IP address is changed, following ESMC documentation for migration might help. As a prerequisite, connectivity of AGENTs must be restored prior to migration steps (for example by restoring original DNS record), otherwise whole process will be much more complicated as re-deployment of whole network will be required. That is why all changes, especially those related to certificates and affecting AGENTs must be made with extra caution.

    It appears like I am going to have to reinstall the software on all the clients. I made a standalone installer which points to the new name of the ESMC server. It works, but I have 60+ clients to re-install the client software on. However I'm thinking about going into the host file and entering a pointer to with like this: 102.54.94.97     rhino.acme.com          # source server
    the IP being the current ip and the new server name.

    It might work, but it will be just as easy to go to each workstation and make the changes.

  9. The off-site IT team that helps with various issues with our technology recently decided to change the names of our computers. All computers were changed to new names including the ESET server. Since they did this none of the clients and communicating with the server. What do I  need to do to re-establish the connections between the server and the clients?

    The clients are running the most recent software versions and these are Windows 10 workstations.

    The server is running the following software:

    ESET Management Agent 7.1.717.0 Up-to-date version
    ESET Security Management Center Server 7.1.717.0 Up-to-date version
    ESET Endpoint Security 7.2.2055.0 Up-to-date version
    ESET Rogue Detection Sensor 1.1.693.0

    Up-to-date version

     

  10. 4 minutes ago, BaldNerd said:

    The ESET rogue scanner must be picking up each device that connects. It'd be tough to walk you through here in the forum, so perhaps a call to ESET support would be helpful if you're stumped, but I have a feeling you may have a networking issue if those devices are meant to be entirely separated from your LAN. Key point: those "rogue" devices are indeed devices which ESET Security Management has seen on your network. Personally I'd want to find out why the network is allowing cross-talk like that, since I'd dread the thought of BYOD having any amount of access to the corporate network without admin approval.

    Hope you figure it out!!

    Robbie // The Bald Nerd

    Thanks BaldNerd, that's probably what I'll do. Hopefully they can  help me clear this issue up. Have a good weekend!

  11. Just now, BaldNerd said:

    Hi @ScottWStewart

    Is there any chance you share your WiFi access or otherwise allow people to temporarily connect to your network?

    Cheers,
    Robbie // The Bald Nerd

    we have a customer wifi hotspot that probably has 20-30 customers log-in to it daily, but it is on a different network segment. Also we have 2 Meraki Access Points used by 10 devices. All are locked down and nobody can access unless they have the SSID.

  12. ESET Security Management Center (Server), Version 7.0 (7.0.577.0)
    ESET Security Management Center (Web Console), Version 7.0 (7.0.429.0)
    Microsoft Windows 10 Pro (64-bit), Version 10.0.17763
    Connected Clients: 86
    Active Licenses: 1

    ESET Security Management Center is reporting 442 Rogue Devices on my domain. There isn't even that many computers, printers or servers on my domain. What can I do to correct this.

     

    Thanks in advance

     
  13. On 11/7/2018 at 2:04 PM, Marcos said:

    Here:
    C:\ProgramData\ESET\RemoteAdministrator\Agent\EraAgentApplicationData\Logs\status.html
    and here:
    C:\ProgramData\ESET\RemoteAdministrator\Agent\EraAgentApplicationData\Logs\trace.log .

    Thank you for your help Marcos. Hopefully this issue can be resolved easily. 

     

    Here are the logs from one of the endpoints that isn't connecting:

     

    trace.log

    Status log.pdf

  14. Thanks for the reply Martin. Our network was being managed off-site and all the client computers had static addresses. But now we have a domain controller onsite and it hands out the IP addresses via DHCP. So my computers on this new domain do not have a static IP address anymore. The company that installed the domain didn't join all of the computers to the it and the ESET server still sees them. The hostname of the ERA server was not changed. As far as the server, it is not part of the domain yet. 

    Where do I go to look at the client logs?

    Thanks,

    Scott

  15. We just switched over to a in house domain and now none of the clients are connecting to the server which is running:

    ESET Remote Administrator (Server), Version 6.5 (6.5.522.0)
    ESET Remote Administrator (Web Console), Version 6.5 (6.5.388.0)

    The Clients are mostly running:

    6.6.2078.5

    I haven't moved the server over to the domain, but the clients and server are on the same IP scheme.

    If I move the server over to the domain will I have to re-install the server components?

    Thanks in Advance!

  16. We just switched over to a in house domain and now none of the clients are connecting to the server which is running:

    ESET Remote Administrator (Server), Version 6.5 (6.5.522.0)
    ESET Remote Administrator (Web Console), Version 6.5 (6.5.388.0)

    The Clients are mostly running:

    6.6.2078.5

    I haven't moved the server over to the domain, but the clients and server are on the same IP scheme.

    If I move the server over to the domain will I have to re-install the server components?

    Thanks in Advance!

     

     

×
×
  • Create New...