Detection Failed. The RPC server is unavailable. Please all WMI through...

[fyang]

Detection Failed. The RPC server is unavailable. Please all WMI through Windows Firewall.

We  have 1 server that Management Console cannot connect to. I've checked Services to ensure RPC and WMI are enabled and running. Checked .net framework and all versions are installed. Also tried the following commands via an elevated cmd prompt:

netsh advfirewall firewall set rule group="remote administration" new enable=yes

and got "No rules match the specified criteria"

netsh advfirewall firewall set rule group="Windows Remote Management" new enable=yes
netsh advfirewall firewall set rule group="windows management instrumentation (wmi)" new enable=yes

These two were successful, however, I am still getting the same error. This push install is on a Windows Server 2019 box. We have over 400 endpoints (end users) and 60 other servers that have been pushed out successfully. This is the only one that is giving me this issue. The built-in Windows Firewall is disabled because all of our machines are managed by Symantec Endpoint Protection. Again, all of our other machines installed fine. So it cannot be Symantec or the ports on the backend. I also believe all of our other servers are on older versions of Windows Server (2012, 2016). So either MBMC is not compatible with Server 2019, or there is something that I am missing. 

Thoughts? 

Thank you.

[exile360]

Greetings,

I don't know if this helps at all, I know you mentioned you already looked at WMI and checked the firewall etc.  I also found the Malwarebytes Management Console Administration Guide here which indicates the following:

Management Server / Primary Console

Malwarebytes Management Console provides all system functionality via its Management Server. It provides all necessary Windows
services, and communicates directly with the Primary Console and the managed endpoint. It runs strictly in the background.
Equipment Specifications
The following specifications are provided as minimum requirements which must be met to provide Management Server
functionality.
• Hardware
• CPU: 1 GHz minimal, dual core 1.6 GHz recommended
• RAM: 1 GB minimal, 2 GB recommended
• Disk space: 2 GB minimal, 10 GB recommended
• 1024x768 screen resolution
• Software
• Windows Installer 4.5
• .NET Framework 4
• Supported Operating Systems
• Windows Server 2016 (excludes Server Core installation option)
• Windows Server 2012/2012 R2 (excludes Server Core installation option)
• Windows Server 2008/2008 R2 (excludes Server Core installation option)
• Windows Small Business Server 2011
• Supported Microsoft SQL Servers
• Database embedded: Microsoft SQL Server 2008, 2012, 2014, 2016 Express (10 GB maximum size limitation)
• Database supported: Microsoft SQL Server 2008/2008 R2, Microsoft SQL Server 2012/2012 R2, Microsoft SQL
Server 2014/2014 R2
Secondary Console
All interaction with the Management Server is effected through the Primary and/or Secondary Console. The Management Server
then interacts with the endpoints(managed clients). Specifications listed below are for a Secondary Console. The Primary Console
is typically installed on the same computer as the Management Server.
Equipment Specifications
The following specifications must be met in order to provide Console functionality.
• Hardware
• CPU: Core Duo 1.6 GHz
• RAM: 1 GB
• 1024x768 screen resolution
• Software
• .NET Framework 3.5 or higher
• Windows Installer 4.5
Management Console Administrator Guide 4
• Supported Operating Systems
• Windows Server 2016 (excludes Server Core installation option)
• Windows Server 2012/2012 R2 (excludes Server Core installation option)
• Windows Server 2008/2008 R2 (excludes Server Core installation option)
• Windows Small Business Server 2011
• Windows 10
• Windows 8.1
• Windows 8
• Windows 7
• Windows Vista
• Windows XP Pro with SP3

[fyang]

Apologies for the duplicate thread, but yes went through it. As of now, I'm pretty confident it doesn't support Server 2019. Now that I think about it, we just spun up another VM on Server 2019 and that one failed and is giving me the same error message as well. 

[fyang]

I was hoping MBMC would push out to Server 2019, but looks like it's not supported. Can't believe I missed that portion. Thanks for pointing that out! 

[fyang]

Now to the Dev team, will 2019 be supported anytime soon? 

[exile360]

Yes, it definitely sounds like a compatibility problem with Server 2019.  I don't know what the current roadmap looks like, however I'm sure that they do plan to support it eventually unless they are transitioning to a different product/platform, though I would have to leave it to a member of the Malwarebytes staff to provide a definitive answer on that.

With that said, I will provide your feedback to the Product team with regards to requesting Windows Server 2019 support so that they are aware of it in case incompatibility is the reason for the issue, though hopefully a member of the staff will be able to assist you in getting it working in the meantime.  They should be online tomorrow and will be able to assist here.

Please let us know if there are any further issues.

Thanks

[N33dful]

Hi @fyang,

Although server 2019 may not be officially supported, I suspect it should run fine. To add to the insights @exile360 provided, there may be further requirements you're missing to perform a push installation, refer to the Managed client deployment prerequisites. If you haven't tried disabling or temporarily uninstalling Symantec, I'd suggest giving that a shot. We do see frequently where 3rd party endpoint protection programs interfere with our deployments or installations on only a few machines. Another alternative to try is manually installing from a package rather than a push install: Create an installation package for Malwarebytes Endpoint Security Let us know if you have any questions, or any further trouble!