none
Caution: New Windows Server Management Packs and alert storms. RRS feed

  • Question

  • Hi,

    A new version the Windows Server Management Pack for 2016 and 1709 was released yesterday. I've installed this in my test environment and every server has gone critical.

    There are a number of new networking monitors based on the TCP Segments sent/received/retransmitted per sec counter. The default thresholds for these are very low indeed (100) every single server in a lightly used test environment tripped these monitors.

    There is also a Time Accuracy monitor based on the perf counter Windows Time Service\Computer Time Offset which also went critical on all systems, the knowledge is badly written but as far as I can tell it's defaulting to 1 microsecond which is madness!

    I've never before installed an MP upgrade which has created as much noise as this, this is not a good sign!

    I

    Thursday, March 8, 2018 4:04 PM

Answers

  • Thanks for your feedback. We have fixed these issues and released the updated MP at https://www.microsoft.com/en-us/download/confirmation.aspx?id=54303 Please test this and share your feedback. Thanks
    Saturday, June 16, 2018 11:48 AM

All replies

  • I have not imported that MP yet, but that's good to know, thanks!
    Thursday, March 8, 2018 5:24 PM
  • Thanks for the heads up!

    Cheers!


    Sam (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" wherever applicable. Thanks!)

    Thursday, March 8, 2018 5:43 PM
  • At least the MP documentation link was fixed, so it can downloaded.

    The another problem is that the new monitor ( Time Accuracy Out of Range) is also introduced, but there isn't a explanation about it. It seems that it haves very low threshold (1 sec?) but according to this article  https://blogs.technet.microsoft.com/askds/2007/10/23/high-accuracy-w32time-requirements/

    it is virtually impossible get this accuracy with built-in w32 time service. ( if this isn't changed in 2016 server, article is old..)

    Wednesday, March 14, 2018 10:18 AM
  • That article IS old. 2016 can do 1ms time accuracy, here's the details, but it boils down to the fact that 2016 can/should do 1ms accuracy.

    https://docs.microsoft.com/en-us/windows-server/networking/windows-time-service/accurate-time


    "Fear disturbs your concentration"

    Monday, March 19, 2018 10:00 PM
  • Your right on this thing, Never Import an MP without read the Guide!

    Here we have imported this MP and Set the threshold for time accuracy to 3 Sec (3000 MilliSec.)

    we are looking for the best value for TCP Segment Monitor.  


    Wednesday, March 28, 2018 5:08 PM
  • You can try to create a Perf Collection Rule on the same PerfMonitor Tageted in the time accuracy and you will see that Windows 2016 can really do it. 

    if your search on Time Accuracy topic on google you will found Wath MS change in Win32Time on WS2016. 

    Wednesday, March 28, 2018 5:11 PM
  • Thanks for your feedback. We have fixed these issues and released the updated MP at https://www.microsoft.com/en-us/download/confirmation.aspx?id=54303 Please test this and share your feedback. Thanks
    Saturday, June 16, 2018 11:48 AM
  • Thanks for your feedback. We have fixed these issues and released the updated MP at https://www.microsoft.com/en-us/download/confirmation.aspx?id=54303 Please test this and share your feedback. Thanks
    Saturday, June 16, 2018 11:48 AM
  • Thanks for your feedback. We have fixed these issues and released the updated MP at https://www.microsoft.com/en-us/download/confirmation.aspx?id=54303 Please test this and share your feedback. Thanks
    Saturday, June 16, 2018 11:49 AM