Jump to content

ThatOneGirl

Members
  • Content Count

    23
  • Joined

  • Last visited

About ThatOneGirl

  • Rank
    New Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Indeed. I read/tried it on ONE machine when I read the documentation, but it didn't work; I know better - I should have tried it on multiple machines.
  2. Running this elevated command on each Windows 10 box did it. netsh firewall set service RemoteAdmin enable
  3. my client definitely will not want to renew/buy this product again since I cannot get it loaded on Windows 10 Pro machines.
  4. I need help still. Is there anyone at Malwarebytes technical support that can remote in and help me? I am going unprotected for a month now......not good.
  5. Ports 135, 137, 445 are indeed open and WMI & PRC are enabled/open -- all on the server, router and the Windows 10 Pro workstations.
  6. Good point! When I installed 20 workstations, they were all Windows 7 Professional. If you could please send me current lints to the Admin Guide, the ports information I need to re-check to make sure are open on the server, ports needed open on the workstations, Services that I need Started. I appreciate it in advance...
  7. The other error I am getting is "Installation failed. The RPC server is unavailable. Please allow WMI through Windows Firewall."
  8. I use the Malwarebytes Management Console. Trying to install Endpoint Security anti-malware and anti-exploit via Client Push Install on 7 new computers that are Windows 10 Professional 64 bit. The error I receive is "the RPC server is unavailable. Please allow WMI through Windows Firewall." I have indeed already allowed WMI through Windows Firewall. I've installed 20 other machines. Ideas? I need to get these installed asap.
  9. 2nd question --- and if you want me to open a new thread, I can. So, you know how I opted to not automatically remove PUPs? Well, I am not seeing in the Console a method to remove them via the Console. Do I have to go into each computer and remove them? Here's a screen shot of the options I do have within the Console...
  10. That would be good! Please do...what do I need to do so that you can do that? 2nd question --- and if you want me to open a new thread, I can. So, you know how I opted to not automatically remove PUPs? Well, I am not seeing in the Console a method to remove them via the Console. Do I have to go into each computer and remove them? Here's a screen shot of the options I do have within the Console...
  11. @djacobson Hi there...did I need to do anything? I've been logging into the Windows 2016 Server and into Malwarebytes Console with the master network administrator account...
  12. I just PM'd you the Server's CollectSErve3rLog.exe. However, on that specific machine 1BCY etc, it gave me errors when I ran it: No process is associated with this object. And. Program Compatibility Assistant Windows Detected that this Program Did not Run Correctly. So, I went to a different machine that was giving the same info about .26 THUS, I ran it from a different machine HPPRODESK2 so that you'd have the report Thank you in advance for looking into this :)
  13. p.s. just looked at System tab and saw that the Description says it's trying to set Server Address to the bogus .26 IP address...is that a left over/bad message from the .XML I wonder? It looks like things are working, so that's my guess. But if you could let me know what you think...t it
  14. Thank you Dyllon Jacobson for your assistance in figuring out what was wrong with my system today! THANK YOU! For posterity sake: for some reason, it was pulling a bogus IP address (192.168.123.26) --- which is an IP we've never used/assigned to a server (nor anything else.) No clue where this .26 IP address came from. The correct IP is 192.168.123.25. Dyllon looked at one of the workstations that was not connecting, specifically in it's c:\ProgramData\SCCOMM\logs\sccomm.txt and immediately we saw the bogus .26 IP address. Changed the XML in the C:\Program Files (x86)\Malwarebytes Management Server\PackageTemplate\SCComm.xml to the CORRECT IP, and ALL IS WELL WORKING GREAT!!!!!
  15. Update - I realize I did not mention that I did indeed do this: GPMC, under Computer Configuration > Policies > Administrative Templates > Network > Network Connections > Windows Firewall > Domain Profile> the Windows Firewall settings you suggested, and then did a gpupdate /force. Side things to mention: I am logging is as the domain administrator when I work on MWB Console. The workstations have Microsoft Security Essentials, but no other antivirus/spy software.
×
×
  • 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.