Jump to content

fyang

Members
  • Content Count

    16
  • Joined

  • Last visited

Community Reputation

0 Neutral

About fyang

  • Rank
    New Member

Recent Profile Visitors

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

  1. @zgerber08 good question! @AlexSmith ticket has been submitted along with dbug logs. In our instance, we are not running O365 but Office 2019. Not only are our end users getting these crashes, but all of our end users who are on VDI's are experiencing extreme performance issues. So far, to mitigate this, I've moved all of them to the default policy in which I've disabled all of the Asset Management options, along with disabling Scan Rootkits, Exploit Protection, and Behavior Protection. No calls has been reported since moving them to this policy. A solution would be much appreciated. Thanks!
  2. Hello, Nebula has recently caused Excel to crash on some of our endpoints. Our current solution is to uninstall Malwarebytes. Is there a solution to this? Thank you.
  3. Hello, It seems Nebula is automatically enabling Windows Firewall on our machines and is impacting business operations. Is there a way to disable this? Ticket 3346202 has been opened. Thank you.
  4. Yes I agree. We've migrated to Nebula and we're having the same issue! It does NOT support servers. Is there a resolution to this?
  5. I did not receive a ticket yesterday when I opened a case, but 2 tickets have been emailed to me this morning. 3317683 and 3318465. The issue is that Nebula will not allow any of us: SuperAdmins to log into the application.
  6. What is up with Malwarebytes? I've tried calling yesterday and this morning during normal business hours but all I get is a machine!! Are you still in business? What is going on? We need immediate support at our site! This is unacceptable!!!! A support ticket has already been opened yesterday!
  7. 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!
  8. 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.
  9. 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.
  10. 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 firewa
  11. 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 firewa
  12. 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!!!
  13. 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
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.