<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Tool: OpsMgr 2007 - RuntimeHealthExplorer</title><link>http://blogs.msdn.com/mariussutara/archive/2009/06/03/tool-opsmgr-2007-runtimehealthexplorer.aspx</link><description>Did you ever wonder what is the state of the instance as known to the runtime (health service) monitoring it? Did you believe that some state changes are unaccounted for? Did you see discrepancy in Health Explorer? I believe many of you may answer yes</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Tool: OpsMgr 2007 - RuntimeHealthExplorer</title><link>http://blogs.msdn.com/mariussutara/archive/2009/06/03/tool-opsmgr-2007-runtimehealthexplorer.aspx#9700245</link><pubDate>Thu, 04 Jun 2009 23:37:18 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9700245</guid><dc:creator>MSutara</dc:creator><description>&lt;p&gt;I just learned that runtime &amp;quot;refuses&amp;quot; to return and recognize &amp;quot;healthy to healthy&amp;quot; state change (which may occur when resetting the state of the monitor while it was healthy). This will cause such monitor become temporarily hiddent from this tool. It will remain in such state until next &amp;quot;real&amp;quot; state change and significantly affects the usability of this tool - SORRY!&lt;/p&gt;
</description></item><item><title>re: Tool: OpsMgr 2007 - RuntimeHealthExplorer</title><link>http://blogs.msdn.com/mariussutara/archive/2009/06/03/tool-opsmgr-2007-runtimehealthexplorer.aspx#9700828</link><pubDate>Fri, 05 Jun 2009 08:44:27 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9700828</guid><dc:creator>michelk</dc:creator><description>&lt;p&gt;Hi Marius,&lt;/p&gt;
&lt;p&gt;I like this tool already.&lt;/p&gt;
&lt;p&gt;My installation of this tool first failed. See eventlog entry below. It seems that you have to run the installation with a user that has a scom administrator role. Because the MP that you are importing during the installation. Maybe something to notice.&lt;/p&gt;
&lt;p&gt;Michel Kamp&lt;/p&gt;
&lt;p&gt;Product: System Center Operations Manager 2007 Runtime Health Explorer Tool -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. &amp;nbsp;Action _AC84155F_436B_469F_9EC5_291E1034A61A, location: C:\Program Files\System Center Operations Manager 2007\RuntimeHealthExplorer.SetupAction.exe, command: /import &amp;quot;C:\Program Files\System Center Operations Manager 2007\Microsoft.SystemCenter.Community.RuntimeHealthExplorer.Internal.mp&amp;quot; &lt;/p&gt;
</description></item></channel></rss>