<?xml version="1.0" encoding="iso-8859-1"?>
<rss version="2.0">
  <channel>
    <title>Aquilaweb - OpsMan Blog</title>
    <link>http://www.aquilaweb.com/blog</link>
    <description>Operations Manager 2007 Blog</description>
    <language>en-us</language>           
    <generator>Nucleus CMS v3.31</generator>
    <copyright>©</copyright>             
    <category>Weblog</category>
    <docs>http://backend.userland.com/rss</docs>
    <image>
      <url>http://www.aquilaweb.com/blog/nucleus/nucleus2.gif</url>
      <title>Aquilaweb</title>
      <link>http://www.aquilaweb.com/blog</link>
    </image>
    <item>
 <title>My Blog is Moving</title>
 <link>http://www.aquilaweb.com/blog/index.php?itemid=96</link>
<description><![CDATA[<p>As a Community Leader for the Windows Management User Group (<a href="http://www.wmug.co.uk">WMUG</a>) I am moving my blog to where it now belongs, on the WMUG website.</p>This site will remain in place with its current information indefinately but will not have any furher posts.</p><p>I look forward to your comments on my new <a href="http://wmug.co.uk/blogs/aquilaweb">blog</a>.]]></description>
 <category>OpsMgr 2007</category>
<comments>http://www.aquilaweb.com/blog/index.php?itemid=96</comments>
 <pubDate>Sun, 10 Aug 2008 20:12:23 +0100</pubDate>
</item><item>
 <title>WMI</title>
 <link>http://www.aquilaweb.com/blog/index.php?itemid=94</link>
<description><![CDATA[<p>After implementing Operations Manager in your environment you may find some of your servers experiencing WMI problems.  This can result in not being able to collect data or monitor what you need as the WMI queries in the rules and monitors will fail.</p><p>Here are some simple command sets to reset and re-register WMI which in my experience I have found to solve many WMI issues.</p><br />
<h2>Resetting WMI</h2><br />
<p><ol><li>net stop winmgmt</li><li>c:</li><li>cd %windir%\system32\wbem\</li><li>rmdir /s /q Repository</li><li>rmdir /s /q Logs</li><li>mkdir Logs</li><li>net start winmgmt</li></ol></p><br />
<h2>Re-registering WMI</h2><br />
<p><ol><li>net stop winmgmt</li><li>c:</li><li>cd %windir%\system32\wbem\</li><li>for %i in (*.dll) do RegSvr32 /s %i</li><li>for %i in (*.mof, *.mfl) do Mofcomp %i</li><li>net start winmgmt</li></ol></p>]]></description>
 <category>OpsMgr 2007</category>
<comments>http://www.aquilaweb.com/blog/index.php?itemid=94</comments>
 <pubDate>Sun, 3 Aug 2008 20:24:32 +0100</pubDate>
</item><item>
 <title>Reporting Problems - Enable Remote Errors</title>
 <link>http://www.aquilaweb.com/blog/index.php?itemid=91</link>
<description><![CDATA[<p>If you have experienced problems with OpsMgr reporting you will probably have seen the helpful message about how to get more information about the error.</p><br />
<p><i>"For more information about this error navigate to the report server on the local server machine, or enable remote errors"</i></p><br />
<p>Enabling remote errors does in most cases give very good information as to the cause of the error and MS has a good guide on how to enable remote errors which I thought I would share.</p><br />
<p><a href="http://msdn.microsoft.com/en-us/library/aa337165.aspx" target="_blank">http://msdn.microsoft.com/en-us/library/aa337165.aspx</a></p>]]></description>
 <category>OpsMgr 2007</category>
<comments>http://www.aquilaweb.com/blog/index.php?itemid=91</comments>
 <pubDate>Wed, 16 Jul 2008 15:44:55 +0100</pubDate>
</item><item>
 <title>Changing the look &amp; feel of Reports</title>
 <link>http://www.aquilaweb.com/blog/index.php?itemid=89</link>
<description><![CDATA[<p>Ever wanted to get rid of that poor quality System Center Operations Manager 2007 banner from across the top of all the default reports and replace it with your own branding?<br/><br />
<div style="text-align: center"><a href="http://aquilaweb.com/blog/media/2/20080707-original2.JPG">Original Banner</a><br />
</div></p><br />
<p>It's really quite simple..... </p><p>As all the default SCOM reports use the same JPG image files as their header, all you need to do is update those files with your lovely company logo banner.  So, open a web browser and navigate to SSRS (http://ReportServer/Reports), this will open the reporting services home page.  On this page will be banner_landscape.jpg and banner_portrait.jpg, these two files are the files used as the header on the reports so these are the files you need to change.  Before doing this, make sure you have your replacement JPG file for both portrait and landscape reports and name them banner_landscape.jpg & banner_portrait.jpg - usually the landscape file is the same as the portraight but just a bit wider.</p><br />
<p>With everything ready, click Upload File on the reporting service home page, click Browse and navigate to one of your two new banner files, check the box to overwrite item if it exists and click OK.<br /><br />
<div style="text-align: center"><a href="http://aquilaweb.com/blog/media/2/20080707-updateimage.JPG">Upload File</a></div><br /><br />
And then do the same for your second banner file.</p><br />
<p>That's it, you're done.  Run a report and you'll have your nice banner heading the report :-).<br /><br />
<div style="text-align: center"><a href="http://aquilaweb.com/blog/media/2/20080707-updated.JPG">New Report</a></div>]]></description>
 <category>OpsMgr 2007</category>
<comments>http://www.aquilaweb.com/blog/index.php?itemid=89</comments>
 <pubDate>Mon, 7 Jul 2008 15:27:19 +0100</pubDate>
</item><item>
 <title>Sealing a Management Pack</title>
 <link>http://www.aquilaweb.com/blog/index.php?itemid=85</link>
<description><![CDATA[<p>By default when you create a new management it is created as unsealed so it has a .xml extension and allows for the management pack to be edited.  Within the support tools of Operations Manager there is a tool called <b>mpseal.exe</b> which can be used to seal the management pack so it can not be edited but still allow for customization of the applied settings with the use of overrides in seperate management packs.  This can be very useful if distributing out to third parties.</p><br />
<p>To seal a management pack is relatevely straight forward and Microsoft have a "How to Seal a Management Pack" guide here, <a href="http://technet.microsoft.com/en-us/library/bb309498(TechNet.10).aspx" target="_blank">http://technet.microsoft.com/en-us/library/bb309498(TechNet.10).aspx</a> which outlines the basic steps and options.  The problem with Microsoft's guide is that the pre-requisistes state that it is possible to create a private certificate using Microsoft Windows Server 2003 Certificate Services.  This is not the case and I will show you how you can create the file required and seal your MP.  I have also contacted MS about there misleading prerequisites and they should be sorting it out soon :-).</p><br />
<p>Before sealing a management, or even generating the key required, there are a couple of prerequisites.</p><p>For key generation you will require .NET Framework 2.0 and any one of these:<br /><table width="75%" align="center"><tr><td><a href="http://www.microsoft.com/downloads/details.aspx?FamilyID=fe6f2099-b7b4-4f47-a244-c96d69c35dec&displaylang=en" target="_blank"><b>.NET Framework SDK</b></a></td></tr><tr><td><b>Micorosft Viual Studio 2005</b></td></tr><tr><td><b>Business Intelligence Development Studio</b> (from SQL 2005 Client Components)</td></tr></table></p><br />
<p>For management pack sealing you will require:<br /><table width="75%" align="center"><tr><td><b>System Center Operations Manager 2007 Support Tools </b>(available on install media)</td></tr></table></p><br />
<p>Once the prereq's have been met you can now create your key and seal up your management pack.  For my example I have copied the contents of the Support Tools folder to C:\Program Files\System Center Operations Manager 2007.</p><br />
<p>1.  Create the key file by running this command: <b>sn -k c:\pairkey.snk</b><br /><br />
<div style="text-align: center"><a href="http://aquilaweb.com/blog/media/2/20080703-key-create2.JPG">Create Key</a></div></p><br />
<p>2.  Extract the public key to file: <b>sn -p c:\pairkey.snk c:\pubkey</b><br /><br />
<div style="text-align: center"><a href="http://aquilaweb.com/blog/media/2/20080703-key-public.JPG">Extract Public Key</a></div></p><br />
<p>3.  Extract public key and public key token from file: <b>sn -tp c:\pubkey</b><br /><br />
<div style="text-align: center"><a href="http://aquilaweb.com/blog/media/2/20080703-key-pubtoken.JPG">Public Token</a></div></p><br />
<p>4.  With the key created, run mpseal.exe from the System Center Operations Manager 2007 Support Tools to seal a management pack:<br /><br />
<b>C:\Program Files\System Center Operations Manager 2007>mpseal.exe "c:\test_mp.xml" /I "c:\program files\system center operations manager 2007" /Keyfile "c:\pairkey.snk" /Company "My Company" /Outdir "c:\newmps" </b><br /><br />
<div style="text-align: center"><a href="http://aquilaweb.com/blog/media/2/20080703-mpseal2.JPG">MPSeal.exe</a></div></p><br />
<p>5.  The new sealed management pack is successfully created !</p><br />
<p>For full deatils on the options available when running mpseal.exe, check out the MS guide here, <a href="http://technet.microsoft.com/en-us/library/bb309498(TechNet.10).aspx" target="_blank">How to seal a management pack</a>.</p><br />
<p>You can then verify the MP by running MPVerify.exe located at C:\Program Files\System Center Operations Manager 2007:<br /><b>MPverify /I "c:\newmps\test_mp.mp"</b></p>]]></description>
 <category>OpsMgr 2007</category>
<comments>http://www.aquilaweb.com/blog/index.php?itemid=85</comments>
 <pubDate>Thu, 3 Jul 2008 11:09:25 +0100</pubDate>
</item><item>
 <title>SQL 2005 Log Shipping Part II</title>
 <link>http://www.aquilaweb.com/blog/index.php?itemid=83</link>
<description><![CDATA[<p>Following on from my SQL 2005 Log Shipping guide and I have created a Part II guide which covers restoring and configuring the secondary database as well as updating the configuration of Operations Manager to use it.</p><br />
<p>Available for download under <a href="../blog/guides">Guides</a>.</p><br />
<br />
]]></description>
 <category>OpsMgr 2007</category>
<comments>http://www.aquilaweb.com/blog/index.php?itemid=83</comments>
 <pubDate>Tue, 1 Jul 2008 16:42:03 +0100</pubDate>
</item><item>
 <title>WMUG Event - 15th July 2008</title>
 <link>http://www.aquilaweb.com/blog/index.php?itemid=81</link>
<description><![CDATA[<div style="text-align: center"><a href="http://wmug.co.uk"><a href="http://aquilaweb.com/blog/media/2/20080617-WMUG1.gif">WMUG</a></a></div><br />
<p><b>The next WMUG event has been announced, it will be taking place on 15th July 2008 at Microsoft Cardinal Place, London</b>.</p><br />
<p>There will be two presentations, one on SCCM presented by Rob Marshall and one on SCOM presented by myself and Gordon McKenna.  And, for the first time all the content will be presented in real time using Virtual Machine technology.</p><br />
<p> Check out full details of the event and register to attend here <a href="http://wmug.co.uk/groups/wmug_event_content/pages/wmug-event-15th-july-2008-cardinal-place-london.aspx">http://wmug.co.uk/groups/wmug_event_content/pages/wmug-event-15th-july-2008-cardinal-place-london.aspx</a>.</p><br />
]]></description>
 <category>OpsMgr 2007</category>
<comments>http://www.aquilaweb.com/blog/index.php?itemid=81</comments>
 <pubDate>Tue, 17 Jun 2008 17:07:05 +0100</pubDate>
</item><item>
 <title>OperationsManager DB Maintenance</title>
 <link>http://www.aquilaweb.com/blog/index.php?itemid=79</link>
<description><![CDATA[<p>Within OpsMan there are seven maintenance rules enabled to perform maintenance on the OperationsManager DB; these are<br /><br /><b><table border="0"><tr><td>Transfer Events</dt><td>Runs a workflow to transfer data</td></tr><tr><td>Optimize Indexes</td><td>Self explanatory</td></tr><tr><td>Maintenance Mode</td><td>Updates maintenance mode data</td></tr><tr><td>Detect and Fix Object Space Inconsistencies</td><td>Again, self explanatory</td></tr><tr><td>Discovery Data Grooming</td><td>Grooms discovery data</td></tr><tr><td>Partitioning and Grooming</td><td>Runs a workflow to partition and groom the database</td></tr><tr><td>Alert Auto Resolve Execute All</td><td>Auto resolve alerts</td></tr></table></b></p><br />
<br />
<p>Each of these rules has its own schedule to execute a stored procedure within the database and it is these stored procedures that keep the database maintained.  The stored procedures work very well and having them controlled by rules makes things even better as you can control when OpsMan performs its maintenance and how often which is great; except you can't.  As the rules are part of the System Center Internal Library management pack you can't alter the schedule as it is a sealed management pack and you are unable to override the schedule as there are no overridable parameters for the schedule.  This can cause some unwanted issues as a number of these rules only run once per day in the early hours of the morning which might not be to everyones needs, that might be your most critical time of the day.</p><br />
<br />
<p>To get round this issue I have put together a management pack which has... </p><p>...all these maintenance rules with configurable schedules.</p><br />
<br />
<p>Download:<a href="http://www.aquilaweb.com/blog/download/OpsDBMaintenance.zip">http://www.aquilaweb.com/blog/download/OpsDBMaintenance.zip</a><br /><font color="red">10/06/08 - Updated version, see comment below.</font></p><br />
<br />
<p>Import the management pack as you would any other, this will make the rules available under Rules in the Authoring pane in the Ops Console.  To make viewing easier, scope the management pack objects to Root Management Server and sort by Management Pack column.</p><br />
<br />
<div style="text-align: center"><a href="http://aquilaweb.com/blog/media/2/20080610-dbmaint3.JPG">View Rules</a></div><br />
<br />
<p>Select the rule where the schedule needs changing and select Properties from the Action pane.  Select the Configuration tab from the Properties window and click Edit next to Data sources.</p><br />
<br />
<div style="text-align: center"><a href="http://aquilaweb.com/blog/media/2/20080609-DS.JPG">Rule Schedule</a><br />
</div><br />
<br />
<p>Update the schedule as required then click OK and OK again.  Done !</p><br />
<br />
<p>Any questions, please contact me or leave a comment.</p>]]></description>
 <category>OpsMgr 2007</category>
<comments>http://www.aquilaweb.com/blog/index.php?itemid=79</comments>
 <pubDate>Mon, 9 Jun 2008 18:00:03 +0100</pubDate>
</item><item>
 <title>Restart Service Recovery Task</title>
 <link>http://www.aquilaweb.com/blog/index.php?itemid=77</link>
<description><![CDATA[<p>"After creating a Windows service monitor, how does one configure a recovery task to automatically start the service on failure?" is a question I have been asked many times and seen asked on forums, so I have put together this quick blog on how to do it.</p><br />
<p>This just covers the Recovery Task, not the creation of the whole monitor.<p><br />
<br />
<p>1.  Locate your monitor, right click and select Properties.  This example is using the Messenger service.<br /><br />
<div style="text-align: center"><a href="http://aquilaweb.com/blog/media/2/20080605-recovery.JPG">Monitors</a></div></p><br />
<br />
<br />
<br />
<br />
<br />
  <p>2.  Select the Diagnostic and Recovery tab, then select Add under Configure recovery tasks and click Recovery for critical health state.</p><br />
<br />
<p>3.  The Create Recovery Task Wizard will open, select Run Command as the type of Recovery task to create and then select a destination Management Pack.  Click Next.<br /><br />
<div style="text-align: center"><a href="http://aquilaweb.com/blog/media/2/20080605-recovery1.JPG">Create Recovery Task</a></div></p><br />
<br />
<p>4.  Give your recovery task a name and description if required.  Select the health state for which the recovery action will run and recovery target to what is relevant for your monitor.  Make sure the Run recovery automatically is checked if you want the task to run automatically.  Click Next.<br/><br />
<div style="text-align: center"><a href="http://aquilaweb.com/blog/media/2/20080605-recovery2.JPG">Task General</a></div></p><br />
<br />
<p>5.  In Full path to file type the command <b>%windir%\System32\net.exe</b>.  In Parameters, type <b>start Messenger</b>, obviously replace Messenger with relevant service.  Set working directory as '%Windir%' and set an appropriate timeout based on how long the service usually takes to start.  Click Create.<br/><br />
<div style="text-align: center"><a href="http://aquilaweb.com/blog/media/2/20080605-recovery3.JPG">Task Configuration</a></div></p><br />
<br />
<p>6.  There isn't a stage 6, you're done.  :-)</p><br />
<br />
If you want to test that the recovery action works, simply stop the service you are monitoring and watch it start back up again.  ]]></description>
 <category>OpsMgr 2007</category>
<comments>http://www.aquilaweb.com/blog/index.php?itemid=77</comments>
 <pubDate>Thu, 5 Jun 2008 10:05:07 +0100</pubDate>
</item><item>
 <title>Management Pack Guides...</title>
 <link>http://www.aquilaweb.com/blog/index.php?itemid=74</link>
<description><![CDATA[<p>...are now available without needing to download the MP itself.</p><br />
<p>If you navigate to this link, <a href="http://technet.microsoft.com/en-us/library/bb310604(TechNet.10).aspx" target="_blank">http://technet.microsoft.com/en-us/library/bb310604(TechNet.10).aspx</a>, it will take you to the System Center Operations Manager TechCenter.  There is plenty of information on OpsMan here including the MP guides which have been split under two different headings, Windows OS's and Server Products, which should make the guide you are looking for easier to find.  And, with the addition of Community Content you can now leave your comments, tips and tricks about the management pack and its guide.</p><br />
]]></description>
 <category>OpsMgr 2007</category>
<comments>http://www.aquilaweb.com/blog/index.php?itemid=74</comments>
 <pubDate>Mon, 2 Jun 2008 16:29:05 +0100</pubDate>
</item>
  </channel>
</rss>