Jump to content

bbraunstein

Members
  • Posts

    135
  • Joined

  • Last visited

  • Days Won

    5

Posts posted by bbraunstein

  1. I've got a really weird problem. I wanted to upgrade a Windows 10 client with EEA from 6.3 to 6.4 but I'm recieved an error that says "the product cannot be uninstalled, try uninstalling manually."

     

    So I log into the computer and attempt a manual uninstall by going to Programs and Features and removing the app. Halfway through it fails with:

     

    "SoftwareInstallation: Installation failed with: (0x643), Fatal error during installation (0x643), Could not delete key \Software\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\ekrn.exe. Verify that you have sufficient access to that..."

     

    The account I'm logged into is a Domain Admin, so I found it odd to have permission errors. So I open up RegEdit (with Administrator privileges) and navigate to the key and attempt to delete it manually. Error pops up saying I'm not allowed to to modify the key. I open up the key's properties and forcibly add myself with full permissions, but when I try to apply, it says I'm not allowed to make changes to the key, again.

     

    I tried repeating the above steps but logged in as the local Administrator account and yielded the same results. I also tried opening a command prompt with Administrator privileges and deleting the key with the force flag, but it still says I am unable to modify.

     

     

    Anyone have other ideas on how to remove it ? 

  2. Yeahh 6.2.7 does NOT resolve the Web Access Protection for my users. Members of my engineering team are unable to hit their QA or Prod site for testing. We troubleshooted a bunch of different things, but as soon as I disabled WAP, they were able to access the sites instantly. 

     

    This is kind of disappointing really. The 6.2.3 beta actually functioned better. I'm going to try deploying the beta to one of the engineers to see if it is replicated on that version.

     

    Who do I need to contact to get this resolved? 

  3. If you login to ELA you can deactivate that license for that computer.

    That's what I've been doing, but it keeps respawning back in ELA. I'm not seeing this device in ERA Web Console, most likely because its a consumer version without an Agent. I've been given the contact number to ESET Support, but I have not seen Charles-PC since Friday. If it shows up once more, I'm calling. This is baffling that someone can use MY license to install other ESET products I was not licensed to install.. There are multiple layers of issues with this problem.

  4. In ELA there is an unknown/unauthorized computer using a seat on my license, CHARLES-PC. I do not have any Charles, Charlie, Chuck, or any variation of the name working at my company. The only people that have access to activate and deploy ESET in my company are myself and my supervisor, who has no knowledge of this CHARLES-PC either.

     

    My license is for 80 seats for EEA + File Security Products. Charles-pc is using NOD32 Antivirus.

    All of my devices in ELA are listed as 'Managed', whereas Charles-pc is listed as 'Standalone'.

     

    This has happened three times already. I've deactivated the seat in ELA each time the computer has reappeared. Originally, I gave Charles the benefit of the doubt that he may have possibly entered his license key incorrectly (albeit a valid one). However, he is not taking the hint and realizing the error or this is malicious.

     

     

  5. Just to give you a short heads-up. As of today, we have released the new Configuration Engine Module for ESET Remote Administrator, that brings support for the new settings needed to configure new options in the OS X build.

    OS X build testing continues, and based on the quick discussion with the head of OS X developers and my colleague from PM, it seems realistic, that the build will be released within the first two weeks of May.

     

    Sweet. How do we get the new Configuration Engine Module and what changes come with it ?

  6. You know I did find that KB a few weeks ago, but it did absolutely nothing because there is no compile and install directions on the webkit link. Unless there's something that I missed, I don't see it anywhere under 'Wiki' or any other page.

     

    Not trying to sound like a typical end-user but if you can provide more specific instructions or a more direct link other than https://trac.webkit.org, that'd be helpful.

  7. A new service release should be available soon. We are still in the process of fixing bugs and subsequent re-testing by the QA department. For users with home version, we've prepared a fixed esets_proxy, however, it can only be used with ECS 6.0.12.

     

    Thanks, Marcos. Appreciate all the time and effort you guys are putting into it. Have you considered some kind of mailing list to alert clients of new releases/patches ? I usually meticulously check the forums for any relevant information about new updates. It usually kills about 10-15 minutes of my day scrolling through different forums looking at specific topics. I know I can subscribe to topics, but that means I'll get notifications of ALL posts in that topic. 

  8. How do I determine if they share the same HW fingerprint? If there are multiple devices nestled under a '+' dropdown menu ? I do have one device that has a dual partition of OSX and Windows on it that has its own individual ERA Agent + EEA installed on each OS. Even though physically, it is one device but with two logical OSes, does that mean it is utilizing only seat ?

     

    I really appreciate the clarification and transparency.

  9. Alright, thanks MartinK. My whole use-case for this is because I have a mismatch of "Activated Seats" vs. the total number of connected clients I truly have. For whatever reason, my number of activated seats is shown as 70, but I have a total of 74 connected devices to my ERAS. All of them are reporting fine so I'm just a little confused why I have three less activated seats than I should have. I managed to correct a couple of devices that were not "activated by ERAS" but there are a handful of computers listed with a much older name. As a result, it's harder to figure out what's missing or duplicated.

  10. I'm curious how ELA gets it client information. I have a handful of client devices that have been renamed over time due to employee departures and/or hires. The FQDN that ELA is reporting does not match the current hostnames of the devices. All these computers are part of a domain and successfully replicate with the DC. 

     

    I've tried deactivating and reactiving the clients, flushing DNS, etc. I've even gone so far as purging the devices from my domain and rejoining them. I'm just trying to rack my brain how the old hostnames keep appearing when I can't find any trace of them anywhere.

  11. You know, I've noticed some performance drops too. Lately whenever I comment, I'll get the green loading bar at the top of the screen for an extended amount of time and then nothing happens. I need to verify my post went through by refreshing the page. I've made a couple of accidental double posts before by hitting the submit button twice.

  12. Fortunately we're an SMB with 200 users.

     

    Assuming that 6.3 has enough broken and missing bits fixed and present..... :ph34r:  

     

    My deployment roll out usually goes as follows:

    1. Day 1, Update the remote Adminstration server [wait 24 hours w/no issues]
    2. 2-3 test machine [wait 48 hours w/no issues]
    3. Myself  [a week min]
    4. My supervisor [a week min]
    5. Deploy out to all new clients or those clients whom have had problems with ESET 5
    6. Official Alpha "The cranky ones" (5 of my most easily agitated software developers) [a week min]
    7. 5 users in "Hardware R&D, have a different tool set and use case than the cranky ones...often cranky in a totally different way" [a week min] 
    8. Official Beta [15 additional Developers] a week min
    9. Deploy out to a different department every 2-3 days if no issues are detected (8 departments)
    10. After all departments have been updated, update Senior Management machines

    The fastest full company deploy possible on the above schedule is 2 months.  If any issues arise all deployments stop until the issue has been resolved.

     

     

    With 6.2 I never made it into alpha deployment.  I think we have 6 machines in the console. 

     

    Usually I like to wait about a week or two before diving into a new release. I was just getting ready to upgrade to 6.2 but then people starting complaining about performance issues. It was some time before WFP was located as the issue. My last upgrade was 6.1.350.0, which I believe was April or May, last year? I've long been awaiting a more polished version of ESET to move up to. 

  13. However, as we are pretty close now, we do anticipate to release ESET Remote Administrator 6.3 in the second half of January - to be more specific, on January 21, 2016 (however, actual release date might differ from country to country, but we will update the download links, download page contents and ERA repository to version 6.3 on this date, if everything works OK).

     

    Concerning the future plans, for the year 2016, we do plan to keep the release pace of two releases per year, one towards the end/beginning, and one towards the mid-year (summer & fall). However, detailed road-map is still a subject of negotiations (and therefore a change), despite the fact, that we are already working on the next version. We will work on improving the way we communicate the progress with you, our customers, as we really appreciate every feedback we receive, either positive, but also the negative one.

     

    Thanks for the information at least. It's more comforting to have a general idea, rather that no information at all. I'll take it with a grain of salt, but I look forward to release.

×
×
  • Create New...