Kevin Holman

13 Nov 2012 4:12 PM

@Fahim -

The list of known issues that were created by changing over to cluster disks (missing perf data, missing 2008 clusters) and the "Processor Information" change are the reasons I don't recommend upgrading to this version of the Base OS MP. When those issues are fixed in a future update, I'll change the stance. 6.0.6958.0 is a pretty solid MP with a few smaller issues which I have long since blogged about workarounds. I like where the MP is heading - changing to cluster disks is the *right* direction, to have these hosted by cluster resource groups, but with this change, came a few issues that will be resolved soon.

Fahim2010

13 Nov 2012 6:02 PM

Kevin,

Thanks for your prompt response. Any idea exactly when the new MP version will be released?

Regards,

Fahim

John Yantorno

26 Dec 2012 5:05 PM

Cluster disk discovery is definitely broken any ETA on a fix?

Kevin Holman

27 Dec 2012 6:34 PM

@John - I don't have any insight into the ETA. Best way to get that is open a support case on the bug and request a hotfix.

Dom

30 Dec 2012 9:57 PM

Hello Kevin,

Happy Holidays

I have installed the MP 6.0.6989.0 an hour ago and I do not get any performances back on any server... should I still wait...?

Thanks,

Dom

Vishi

3 Jan 2013 6:34 AM

Hi Kevin,

We are running 6.0.6958.0 MP, we don't have the addidtional components installed(CSV monitoring, BPA and reports) as I have upgraded via MP catalog. I could not download the earlier versions from microsoft catalog. Would it be a good idea to upgrade to 6.0.6989? What would you recommend us to do?

Kevin Holman

3 Jan 2013 1:42 PM

@Vishi -

I don't recommend upgrading from 6.0.6958.0 to 6.0.6989, as I stated in the summary of this article. Since this version breaks cluster monitoring of 2008 cluster disks... I'd recommend waiting for the next release where this will be fixed.

Vishi

4 Jan 2013 2:40 AM

Thanks Kevin, will wait for the next release then

uglywon

14 Feb 2013 1:21 PM

We are running 6.0.6958.0 and have several high profile 2008 Clusters so we've held off...Thank goodness I read your blog! We've been waiting patiently for the next release. But, since several of the newer MPs require the Core OS update. We have several other issues unresolved by fixes in these newer MPs. For us, the MPs affected are:

-Microsoft Hyper-V (6.2.6640.0) - huge deal for us

-Win2003 / Win 2008 Print Server (6.0.7004.0) - big deal for us

-Active Directory (6.0.8070.0) MPs.

Not to mention, the new Core OS MP itself will address several logical disk monitor capabilities we desperately need. I've heard from the rumor mill that a private fix is out. So, can you shed any light as to when we can expect the next release?

Thanks

--Steve

Chris McIntyre

28 Feb 2013 4:23 PM

We've imported this MP and I've worked around all the existing issues mentioned here. But there is one thing that still annoys me. If you go into the "Processor Performance" view, the legend shows two objects for each Server 2008 machine. One for the "Processor Information" object and one for just the "Processor" object. What puzzles me is that the same rule is indicated as collecting both counters, although it specifically only lists the "Processor Information" object in its configuration. It's a pain to not know which one to click, and have hundreds of items in the legend that don't show any data. Looks bad. Any ideas on how to fix this?

Sven Wells

8 Mar 2013 2:15 PM

Hello,

We upgraded to 6.0.6989.0 just before Christmas 2012. Previously we were running 6.0.6959.0. We've discovered what Leandro above discovered. Even though we've disabled the "Logicak Disk Free Space" monitor and enabled the "Windows Server 2003 Logical Disk Free Space (MB) Low" monitor, these alerts are not being produced. We've 'played' with the samples, increased the thresholds to unconventional/extraordinary amounts (ie. 100GB for a 50GB drive) etc. We see that the monitor is enabled and appears to be working, however, no Alerts. Performance collection rules are working fine.

Any ideas?

Thanks,

Sven

sckl

12 Mar 2013 6:28 AM

Hi Kevin

Do you know if there's any update planned regarding the new Processor counter instance especially for reports?

Actually processor performance is something essential for capacity planning and monitoring, so I don't really understand why the reports aren't reflecting this essential change.

You've written "Therefore, there is no performance monitoring or collection for your CPU on that OS. You will need to create a rule and a monitor to address this for “Processor” as a workaround for Server 2008 machines." => I hope that this will be fixed in the next release? For me this is base monitoring and therefore a must.

Thanks

BR

Klaus

Eric Peterson

12 Mar 2013 11:06 PM

Hi Kevin,

Is there any more information or a possible ETA on a solution for the 2nd known issue in this MP relating to collection of CPU data on Windows 2008 R2 machines?

Thanks,

-Eric

Cookie.Monster

26 Mar 2013 6:15 PM

Seems strange that the Processor / Processor Information change and resulting issues were identified nearly half a year ago and have yet to be resolved.

At least we have an informative post detailing the reason why, Thanks for the info!

NorthernTrustTim

1 May 2013 8:34 PM

What about the Monitor "Total CPU Utilization Percentage"? Doesn't it subscribe to the data published by "Processor % processor Time _Total"? My tests have shown the monitor to be broken by the CU5 update for Server 2008 Standard edition. Is there a fix for this?