• cluffernut

    cluffernut

    @cluffernut

    Viewing 4 replies - 1 through 4 (of 4 total)
    Author
    Replies
    • in reply to: Symantec Endpoint Protection throwing blue screens #1982222

      Not seeing it *yet*, we’re on 14.2 RU1 MP1 build 14.2.4814.1101, however just noticed IPS sequence number is 191014062 (R62?).

      • This reply was modified 5 years, 5 months ago by cluffernut.
    • in reply to: Missed the September patches – now what? #1978526

      We had patched in September on our servers, seen lots of issues (SQL Data connections timing out, etc…) so we rolled backed.  We’re still seeing intermittent 2012 servers experiencing the black screen issue.  Only patch we didn’t/couldn’t roll back was the SSU (KB4512938).  I haven’t seen people complaining about this recently and there are no known issues on Microsoft’s site. It kinda has me scratching my head a bit.  Surprisingly, we’re not really seeing issues on our 2016 LTSB servers (1609).

    • So I just wanted to send an update.  In our corp. environment, we have about 50/50 Server 2012 R2 and Server 2016 LTSB (1607).  As our Cyber dept insists, we patched last weekend (9/29) and we’ve had a slew of weird issues since, Primarily on the 2012 side.

      MS SQL ODBC errors up the wazoo, any App server jobs making calls to/from SQL blowing up, sometimes reproducible sometimes random.  We’ve also had a couple reports of console black screens.  Our back-up environment (Veritas NetBackup) has experienced many backup failures as well.

      Removing .NET updates – KB4514599, Security Only KB4516064, IE KB4516046 fixes all of the issues.  Of course the SSU isn’t removable so KB4512938 is still in place.   I was a little surprised of the move to DEFCON 3.

      Note, our homogeneous 2016 platforms seem fine (both App & Database on OS 2016).  Anyone else seeing these types of issues?

    • in reply to: Total Meltdown (not Meltdown!) exploit now available #186570

      I hadn’t signed in above…

      The manual vbs should fix the disappearing NIC issue in 2008 SP2.

      KB 4089229

      3 users thanked author for this post.
    Viewing 4 replies - 1 through 4 (of 4 total)