<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: My nightmare experience with the new Dell Management Pack 3.1 A01</title>
	<atom:link href="http://www.scom2k7.com/my-nightmare-experience-with-the-new-dell-management-pack-31-a01/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.scom2k7.com/my-nightmare-experience-with-the-new-dell-management-pack-31-a01/</link>
	<description></description>
	<lastBuildDate>Wed, 18 Jan 2012 09:40:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Pete Zerger</title>
		<link>http://www.scom2k7.com/my-nightmare-experience-with-the-new-dell-management-pack-31-a01/comment-page-1/#comment-333</link>
		<dc:creator>Pete Zerger</dc:creator>
		<pubDate>Fri, 24 Oct 2008 11:54:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.scom2k7.com/?p=307#comment-333</guid>
		<description>Tim, 

The 4000 error is a known issues resolved by 951526, and is actually contained in a couple of newer fixes. You have to be sure your DLL versions are actually updated when you apply the fixes, as we have seen a couple of cases where this didn&#039;t happen. I would guess this is the case in your situation, as that fix definitely seems to be resolved by this fix.

See http://www.systemcenterforum.org/critical-hotfixes-for-opsmgr-and-essentials-2007-sp1-and-how-to-verify-youre-up-to-date/</description>
		<content:encoded><![CDATA[<p>Tim, </p>
<p>The 4000 error is a known issues resolved by 951526, and is actually contained in a couple of newer fixes. You have to be sure your DLL versions are actually updated when you apply the fixes, as we have seen a couple of cases where this didn&#8217;t happen. I would guess this is the case in your situation, as that fix definitely seems to be resolved by this fix.</p>
<p>See <a href="http://www.systemcenterforum.org/critical-hotfixes-for-opsmgr-and-essentials-2007-sp1-and-how-to-verify-youre-up-to-date/" rel="nofollow">http://www.systemcenterforum.org/critical-hotfixes-for-opsmgr-and-essentials-2007-sp1-and-how-to-verify-youre-up-to-date/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marnix Wplf</title>
		<link>http://www.scom2k7.com/my-nightmare-experience-with-the-new-dell-management-pack-31-a01/comment-page-1/#comment-112</link>
		<dc:creator>Marnix Wplf</dc:creator>
		<pubDate>Wed, 01 Oct 2008 07:15:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.scom2k7.com/?p=307#comment-112</guid>
		<description>Hi Tim.

Great job you&#039;ve done! I have had an issue at a customers site where EventID 5300 happened on the RMS. With this event the HealthService stalls (on the RMS!) and the RMS state turns to grey. So no flow of information, no more monitoring. With the help of Microsoft Support we were capable to find the culprit: the Dell Management Pack. Because we log everything we do we were capable off backtracking when the fist time EventID 5300 was logged. It was a couple of days after we had imported many new MPs. One of which was the updated MP of Dell...

After having removed this MP and the DRAC&#039;s as well, SCOM hasn&#039;t shown any EventID 5300 anymore.

So all I can say is that I concur your story about the new Dell MP and hosing the RMS.

Kind regards,
Marnix Wolf</description>
		<content:encoded><![CDATA[<p>Hi Tim.</p>
<p>Great job you&#8217;ve done! I have had an issue at a customers site where EventID 5300 happened on the RMS. With this event the HealthService stalls (on the RMS!) and the RMS state turns to grey. So no flow of information, no more monitoring. With the help of Microsoft Support we were capable to find the culprit: the Dell Management Pack. Because we log everything we do we were capable off backtracking when the fist time EventID 5300 was logged. It was a couple of days after we had imported many new MPs. One of which was the updated MP of Dell&#8230;</p>
<p>After having removed this MP and the DRAC&#8217;s as well, SCOM hasn&#8217;t shown any EventID 5300 anymore.</p>
<p>So all I can say is that I concur your story about the new Dell MP and hosing the RMS.</p>
<p>Kind regards,<br />
Marnix Wolf</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim</title>
		<link>http://www.scom2k7.com/my-nightmare-experience-with-the-new-dell-management-pack-31-a01/comment-page-1/#comment-104</link>
		<dc:creator>Jim</dc:creator>
		<pubDate>Wed, 24 Sep 2008 18:21:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.scom2k7.com/?p=307#comment-104</guid>
		<description>Already have that t-shirt...</description>
		<content:encoded><![CDATA[<p>Already have that t-shirt&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

