Jump to content

JPerez1969

Honorary Members
  • Posts

    22
  • Joined

  • Last visited

Posts posted by JPerez1969

  1. 19 hours ago, Eleanor67 said:

    Is there any updates on this? I'm having the same issue recently.

    Our clients display as "...The client has not been registered". In addition, some of those clients are now not reporting to MMC. But, if you restart the services then it show on MMC

    nope, as of 5/14/2019, still no updated version to resolve the issue. i created a case and the support guy said it wasn't a bug. well, i beg to differ as it's pretty evident, that one day its working then all of a sudden its start acting wonky like this. the tech i spoke to before him took it to the dev team and said they are aware of the problem and will patch it on the next release, So with that said either he was pulling my chain to appease me and move on or there is a bug that will get addressed. by the way :djacobson" offered a suggestion, of which our settings were already set to that with no resolution. i added a second failed restart option with a retry after 4 minutes, just to see. BUt i doubt that will resolve it because i high doubt that all 89 hosts are failing to start the service.

  2. So here's the email i got back from the support case i opened last week regarding this issue as of this morning as of 12/13/18 8:00am PST. Message was truncated.

     

     

    "The issue you reported is: Newer version of Malwarebytes Anti-Exploit was already installed; Managed client software was already installed. The client has not been registered. 


    This issue is a known issue to us and we are working on releasing a fix in the coming update 1.9.1."........"At the moment we don't have an actual ETA for the update date but we believe it should be around the first weeks of 2019.

    As advised previously, This message should be just a wording issue and have no impact on the protection or the scans on your clients."....

     

    so we need to be patient and wait it out until the new release is out, theres nothing we can do at this point from the console or client side. be proactive about it though, keep checking every other week or so for the new release.
     

  3. I recently upgraded my management server console to 1.9.0.3671 for the anti-ransomware deployment feature now supported, but when running an update or a fresh installation install using the Client Push Install method whether i use the scan network or scan network and detect client software method it returns with the message in the Execution Result of the Client Push Install Tab "Managed client software was already installed. The client has not been registered." for all clients that were upgraded or newly installed. The clients use all 3 components MBytes, Exploit and AntiRansomware.

    I have restarted the services on the server and clientside, i  have uninstalled and deleted the logs option, rebooted and reinstalled and also ran a database cleanup with the same message.

    Has anyone found a resolve to this yet? BTW, i started a support chat with mbytes this morning and he wasn't helpful other that stating we cant fix it because we don't have a newer version yet. What's unsettling is if the message is stating this what other functionality may not be operating properly?? i opened a case for this to see id the dev team can get involved to fix and release a bugfix as it may very well lead to that. Unless someone found a fix?? 

    antiransom.JPG

    screenshot.JPG

  4. I recently upgraded my management server console to 1.9.0.3671 for the anti-ransomware deployment feature now supported, but when running an update or a fresh installation install using the Client Push Install method whether i use the scan network or scan network and detect client software method it returns with the message in the Execution Result of the Client Push Install Tab "Managed client software was already installed. The client has not been registered." for all clients that were upgraded or newly installed. 

    I have restarted the services, i  have uninstalled and deleted the logs option, rebooted and reinstalled and also ran a database cleanup with the same message.

     

    Did you find any resolve with your issue, Sumeet?

    screenshot.JPG

Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.