Jump to content

rockshox

Members
  • Content Count

    44
  • Joined

  • Last visited

Profile Information

  • Location
    USA

Recent Profile Visitors

611 profile views
  1. @MichalJ - To answer your questions: - Yes. After I do a synchronize in EP, but EBA and EP show the same thing. Sorry the numbers keep changing, but due to the fact we are rolling out new PC's, I've been juggling removing and adding the PC's so we don't max out at 250 during the swaps. With the shuffle, right now both EP and EBA show 229/250, so they do match each other even though it appears to be the wrong number. - When I view the main dashboard in EP, it shows I have 242 Managed & Protected devices. That is correct. I exported the Computers table to Excel and confirmed 242 de
  2. MichaelJ - To answer your questions: - I checked the "Multiple products" groups in EBA, the devices are all Microsoft Surface Pro or Surface Book devices, there are also two Panasonic tablet devices. All Microsoft Surface devices are using the Surface Dock. In our department, we have a single MS Dock that we use for imaging and deploying software before installing the equipment. We do not normally unbox each and every dock to image our computers which is why multiple machines are imaged and software (ESET is installed after imaging) is installed. While we could unbox each dock and use it
  3. MichalJ - I tried as you suggested. I deleted the computers that comprised the "Multiple prodcuts" group, and confirmed they did not show in EBA any longer. From ESET Protect, I then pushed a "Product Activation" task to each computer. The computers then showed back up in EBA grouped together again. I tried two different groups, 6 different computers that all did the same thing. I know for certain these computers are in different locations, different docks and one computer is being used from home today. They still all went back into EBA and grouped back up automagically. What else can I t
  4. Hello - I can see this question has been asked numerous times, but without a clear way to fix the issue. In reviewing licenses in ELA and now EBA, I have several places where devices are grouped as "Multiple products". Many threads point out this is caused by the same hardware being renamed. However in our case, each computer is a separate hardware device, but the dock used for setup was the same. All the devices that are grouped under "Multiple Products" are mobile Surface or Lenovo products that were all imaged and software installed on the same dock. Due to the dock having the same hardware
  5. MichalJ - Thank you for the info. I was able to find it in the reports as you suggested.
  6. I found that if I trigger a Scan from the ESMC console and then dig into the task, I can see the Execution Details from the Scan which is basically what I was looking for. I don't really need the full log, just the high level metadata, Just so I can see the scan actually ran, how many files were scanned and everything was clean. However, what triggered the question in the first place is the fact that we have a scheduled weekly scan that runs at the same time every week on all computers. Those scans seem to be invisible to ESMC. I can login to a client, check the "Computer Scan" logs
  7. Where do I view computer scan logs in ESMC 7? In ERA 5 it was pretty simple, but I am unable to locate it in ESMC 7. Thanks
  8. Ah ok. Well I'm running a Windows server with standalone install of ESMC so slightly different, but I'm sure the same issue. I believe the Virtual Appliance is running CentOS, so it would require modifying the correct config file and increasing the TimeOut value, but since it's the Virtual Appliance I can't direct you to exactly where that would be. Maybe someone else can chime in here that knows where the config file is for the Apache HTTP Proxy on the virtual appliance.
  9. Are you running the virtual appliance or standalone Windows/Linux server?
  10. FYI - Confirmed the TimeOut value is being used. I pushed the Endpoint client to a very slow T1 link, the task failed with the same error. Checking the debug log showed the timeout occurred after exactly 2 minutes. I changed the TimeOut value to a much larger number and was able to successfully deploy the Endpoint client to the remote location with the slow link.
  11. I checked the httpd.conf for the Apache HTTP Proxy service and found that they already had the ProxyTimeout set to 900 seconds, but that clearly didn't seem to be working. After looking around on Google, I modified httpd.conf and added "TimeOut 120". My thought was to see if the timeout now happened after 2 minutes so that I could confirm which timeout value was being used. Surprisingly after adding "TimeOut 120", I've been able to successfully push the installer multiple times to one remote location. I'm not sure if this is coincidence, or if that was enough time to solve the timeout issue.
  12. Apache HTTP Proxy debug logs show that the proxy times out after exactly 60 seconds. See attached logs. Hopefully that will help with determining the problem. Apache_HTTP_Proxy_debug.txt
  13. So, just to test. I stopped the HTTP Apache Proxy service, deleted the cache and started the service. I then successfully pushed the ESET Endpoint Antivirus client to the workstation. I then turned right around and tried pushing the client to another computer in the exact same remote location, and once again received the "GetFile: Error reading HTTP response data (0x4e33)". Clearly something wrong with the Apache HTTP Proxy service on slower links.
  14. I reviewed the Trace logs on the client workstation along with the Apache HTTP Proxy logs, all of which didn't really show any reason for the problem, other than it doesn't work. The trace logs do show the error. I also noticed the error happens within seconds of the task starting the deployment. It's an almost immediate failure before it would even have a chance to really start downloading the installation package. 2018-12-14 21:42:22 Error: CSystemConnectorModule [Thread 6ac]: Software installation failed: GetFile: Error reading HTTP response data (0x4e33) 2018-12-14 21:44:22 Error: C
  15. Continuing to have a lot of issues with this whole Apache HTTP Proxy cache. After trying to push the ESET Endpoint Antivirus to a location with a 20m connection the other day a dozen times I gave up. I tried again today, and on the first attempt it succeeded and the software is installed. I went ahead and tried another computer at another location with the same 20m connection, and now it's failing over and over again. 6 times in a row with the same error "GetFile: Error reading HTTP response data (0x4e33)". Is there a way to force ESMC 7 to push installation tasks the same way ERA 5 did?
×
×
  • Create New...