<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Finding solutions to the larger issues affecting our world. &#187; Operations Manager</title>
	<atom:link href="http://www.briandeyo.us/brd/wp/index.php/tag/operations-manager/feed" rel="self" type="application/rss+xml" />
	<link>http://www.briandeyo.us/brd/wp</link>
	<description>The saturation of technology is inevitable.</description>
	<lastBuildDate>Sat, 17 Jul 2010 11:27:14 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Operations Manager not sending email after IM notification settings changed.  Event ID 4509.</title>
		<link>http://www.briandeyo.us/brd/wp/index.php/2009/10/08/operations-manager-not-sending-email-after-im-notification-settings-changed-event-id-4509</link>
		<comments>http://www.briandeyo.us/brd/wp/index.php/2009/10/08/operations-manager-not-sending-email-after-im-notification-settings-changed-event-id-4509#comments</comments>
		<pubDate>Thu, 08 Oct 2009 15:47:13 +0000</pubDate>
		<dc:creator>brian</dc:creator>
				<category><![CDATA[Computers and Technology]]></category>
		<category><![CDATA[email]]></category>
		<category><![CDATA[IM]]></category>
		<category><![CDATA[instant message]]></category>
		<category><![CDATA[Operations Manager]]></category>
		<category><![CDATA[OpsMgr]]></category>

		<guid isPermaLink="false">http://www.briandeyo.us/brd/wp/?p=202</guid>
		<description><![CDATA[forward-slash in IM 'return address' field for OpsMgr notification breaks all notification workflows]]></description>
			<content:encoded><![CDATA[<p><span>For several hours I&#8217;ve been trying to retrace my steps on how I managed to break our Operations manager 2007 email notifications.  For 2 days now alerts are being triggered and our server&#8217;s health states are being updated, but no email was getting out.</span></p>
<p><span>I checked the message tracking logs on Exchange and nothing was ever leaving the <span>OpsMgr</span> server.  I tried to telnet to the smtp server and that worked.  I checked the logs and there was an innocuous message about the &#8220;Instant Notification&#8221; settings I were using, and how it was causing a notification <span>workflow</span>.  The app log message looked like this:</span></p>
<hr />Event Type: Error<br />
<span>Event Source: <span>HealthService</span></span><br />
Event Category: Health Service<br />
Event ID: 4509<br />
Date: 10/8/2009<br />
Time: 9:38:07 AM<br />
User: N/A<br />
Computer: OPS-RMS<br />
Description:<br />
<span>The constru<span>ctor</span> for the managed module type &#8220;Microsoft.<span>EnterpriseManagement</span>.<span>HealthService</span>.Modules.Notification.Sip.<span>SipNotificationTransportModule</span>&#8221; threw an exception. This module was running in rule &#8220;Subscriptiond2e36701_7544_4b03_9c18_811f5d34a5<span>fd</span>&#8221; running for instance &#8220;Alert Notification Subscription Server&#8221; with id:&#8221;{E07E3FAB-53BC-BC14-1634-5A6E949F9230}&#8221; in management group &#8220;GROUP&#8221;.</span></p>
<p> </p>
<p>The exception text is:<br />
<span>Microsoft.<span>EnterpriseManagement</span>.<span>HealthService</span>.<span>ModuleException</span>: The specified Uri : (sip:<span>email</span>@im.vanity.com/home) has one or more invalid elements. A valid sip <span>uri</span> should be of the format sip:user@host.</span><br />
<span>Parameter name: <span>uri</span> &#8212;&gt; System.<span>ArgumentException</span>: The specified Uri : (sip:<span>email</span>@im.vanity.com/home) has one or more invalid elements. A valid sip <span>uri</span> should be of the format sip:user@host.</span><br />
<span> </span></p>
<p><span>(insert lenghty description of lots of things going crunch)</span></p>
<p>For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.</p>
<hr /> </p>
<p>So I decided it was important to revisit my IM settings, since I knew that was what I was working on the day notifications had stopped. And there it was glaring at me in the face. the last thing I changed was added &#8220;/home&#8221; to the &#8220;Return Address&#8221; under the notification settings.</p>
<p><span>Once I removed that I proceeded to get 2 days worth of back-logged alerts. It is interesting to note that an error with the IM notification <span>workflow</span> actually affected the Email notification also. </span></p>
<p>I&#8217;m just happy I found it and fixed it. In case anyone ever sees the Event ID 4509 on your RMS, I would suggest visiting your notification settings.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.briandeyo.us/brd/wp/index.php/2009/10/08/operations-manager-not-sending-email-after-im-notification-settings-changed-event-id-4509/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Workaround for OpsMgr Agent event id 1220 and 7022 if deployed from image</title>
		<link>http://www.briandeyo.us/brd/wp/index.php/2009/06/05/workaround-for-opsmgr-agent-event-id-1220-and-7022-if-deployed-from-image</link>
		<comments>http://www.briandeyo.us/brd/wp/index.php/2009/06/05/workaround-for-opsmgr-agent-event-id-1220-and-7022-if-deployed-from-image#comments</comments>
		<pubDate>Fri, 05 Jun 2009 16:19:01 +0000</pubDate>
		<dc:creator>brian</dc:creator>
				<category><![CDATA[Computers and Technology]]></category>
		<category><![CDATA[Operations Manager]]></category>

		<guid isPermaLink="false">http://www.briandeyo.us/brd/wp/?p=158</guid>
		<description><![CDATA[If you are like me and love deploying systems from an image, you have may have experienced a problem when having the Operations Manager agent installed on the image, and after deployment and a rename of the server, you end up with event id&#8217;s 1220 and 7022 in your Operations Manager event log every 30 [...]]]></description>
			<content:encoded><![CDATA[<p>If you are like me and love deploying systems from an image, you have may have experienced a problem when having the Operations Manager agent installed on the image, and after deployment and a rename of the server, you end up with event id&#8217;s 1220 and 7022 in your Operations Manager event log every 30 minutes.</p>
<p>The reason for this issue is the Operations Manager certificate for this computer still has the original image build&#8217;s server name on it.</p>
<p>To fix this:</p>
<ol>
<li>Stop the Operations Manger Health Service</li>
<li>Open up an MMC and openthe certificates snap-in for &#8220;Local Computer&#8221;</li>
<li>Navigate to Certificates -&gt; Operations Manager -&gt; Certificates</li>
<li>and delete the certificate with the original build&#8217;s name</li>
<li>Restart the Operations Manager Health Service.</li>
</ol>
<p>This fix may not be the best way to solve this issue, but I have not done a thorough web search for better solutions yet.  If no one else has this documented somewhere, the steps could easily be scripted, and if I don&#8217;t find a better solution I will post the eventual script for this once I have it done.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.briandeyo.us/brd/wp/index.php/2009/06/05/workaround-for-opsmgr-agent-event-id-1220-and-7022-if-deployed-from-image/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
