Condividi tramite

Don’t forget to License your SCOM 2016 deployments

  • Articolo

<!--[if lt IE 9]>

<![endif]-->

Comments

  • Anonymous
    June 29, 2017
    The comment has been removed
    • Anonymous
      June 29, 2017
      I am VERY concerned about this when I saw the new MP's.MANY customer environments have TONS of 18456 errors where something is trying to access a DB and gets denied. Having this NEWLY ADDED rule enabled by default seems like a concern to me initially, I read this in the "what's new" section and that immediately stood out to me. I figured we'd get a lot of customer noise on this one. The good news it - it is a new rule, so simply disable it, if you don't care about this situation. It technically should be "fixed" but I see this all the time and most DBA's just don't care. The best reason to "fix" it - is because it floods your application event logs in many cases. The bad news is now we are flooding SCOM. :-(
      • Anonymous
        June 29, 2017
        Ah, thank you Kevin for the lightning response. Disabled the rule across our SQL engines...Love this kind of feedback, right from the horse! ;)Michael