Jump to content

fyang

Members
  • Content Count

    9
  • Joined

  • Last visited

About fyang

  • Rank
    New Member
  1. 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!
  2. 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.
  3. Also, just another piece of information, I notice in another thread that states Netbios needs to be enabled, however, we have Netbios disabled through GPO because of a known vulnerability that exists and all of the other machines installed fine.
  4. 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.
  5. 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.
  6. Got it figured out! For anyone who might run across this issue. What needs to happen first is to launch the newly created database in Microsoft SQL Server Management Studio. Right-click on the Server\database --> Properties --> click on SQL Server and Windows Authentication mode. Restart the server from Configuration Manager. Next, log into the database through MSSMS using the sa account. Try it again and it should work. Any questions, let me know. Thanks for all the help guys!!!
  7. Hello, the reason for an external database is because in the best practices guide, it states that it is not recommended for more than 200 endpoints. We have close to 400 endpoints. I am an entry level Sys Admin and this is the first project of many that I was assigned. It looks like I have a lot to learn! So I've gotten past that error in my initial post. However, I cannot install because I cannot login. This is my first time configuring SQL Server 2016 from scratch. Maybe someone can help? The server and database is up. I can launch it through Microsoft SQL Server Management Studio using windows authentication on the local machine. I've also registered the server by going to View --> Registered Servers within Management Studio. Under Object Explorer, I've expanded Security --> Logins and I've set the Server Roles on all the domain accounts that are listed there as sysadmin. I've restarted the database under Sql Server Configuration Manager. Rebooted the machine. Attempted to login using all of the domain accounts that I've set to sysadmin. Am I missing something? Any help is greatly appreciated. Thanks!
  8. Hello, So we're having an issue trying to get the managed console to install. We've spun up a new VM and installed MSSQLServer 2017. We've whitelisted the following on our firewall: https://data.service.malwarebytes.org , https://data-cdn.mbamupdates.com, https://hubble.mb-cosmos.com, https://*.mwbsys.com, and https://telemetry.malwarebytes.com, all on port 443. Righ-clicked and ran as admin on the application. We've verified the server and instance name. Triple checked the user name/password, but we keep getting that error message. Any help is much appreciated. Thank you.
×
×
  • 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.