Thursday, April 11, 2013

[OpsMgr 2012 SP1] System Center Operations Manager 2012 SP1 UR2 has been released


Update Release 2 has been release and here are the fixes to SCOM and you can look/download what else is being addressed in this release on Microsoft site



Operations Manager (KB2826664)

Issue 1
The Web Console performance is very poor when a view is opened for the first time.
Issue 2
The alert links do not open in the Web Console after Service Pack 1 is applied for Operations Manager.
Issue 3
The Distributed Applications (DA) health state is incorrect in Diagram View.
Issue 4
The Details Widget does not display data when it is viewed by using the SharePoint webpart.
Issue 5
The renaming of the SCOM group in Group View will not work if the user language setting is not "English (United States)." 
Issue 6
An alert description that includes multibyte UTF-8 characters is not displayed correctly in the Alert Properties view.
Issue 7
The Chinese (Taiwan) Web Console displays the following message even after the SilverlightClientConfiguration.exe program is run:
Web Console Configuration Required.
Issue 8
The Application Performance Monitoring (APM) to IntelliTrace conversion is broken when alerts are generated from dynamic module events such as the Unity Container.
Issue 9
Connectivity issues to System Center services are fixed.
Issue 10
High CPU problems are experienced in Operations Manager UI.
Issue 11
Query processor runs out of internal resources and cannot produce a query plan when you open Dashboard views.
Issue 12
Path details are missing for "Objects by Performance."

Operations Manager - UNIX and Linux Monitoring (Management Pack Update) (KB2828653)

Issue 1
The Solaris agent could run out of file descriptors when many multi-version file systems (MVFS) are mounted.
Issue 2
Logical and physical disks are not discoverable on AIX-based computers when a disk device file is contained in a subdirectory.
Issue 3
Rules and monitors that were created by using the UNIX/Linux Shell Command templates do not contain overridableShellCommand and Timeoutparameters.
Issue 4
Process monitors that were created by the UNIX/Linux Process Monitoring template cannot save in an existing management pack that has conflicting references to library management packs.
Issue 5
The Linux agent cannot install on a CentOS or Oracle Linux host by using FIPS version of OpenSSL 0.9.8.

This posting is provided "AS IS" with no warranties.

Wednesday, April 10, 2013

[MMS 2013] Session in video are available



The Microsoft Management Summit (MMS) brings together the brightest IT professionals from around the world to increase their technical expertise through an intensive week of training led by experts in desktop, device management, datacenter, and cloud technologies.

Microsoft published the videos of the sessions and you can watch them on Channel9 : 


This posting is provided "AS IS" with no warranties.

Thursday, April 4, 2013

[OpsMgr 2012] Publishing SCOM 2012 dashboards to SharePoint by Kelvin Holman

This feature is covered in the product documentation on Microsoft site :  http://technet.microsoft.com/en-us/library/hh212924.aspx



Kevin Holman recently ran into a problem setting this up for a customer – so thought he should talk about that on his blog. You can read his article directly on Kevin's blog.



This posting is provided "AS IS" with no warranties.

[MMS 2013] Retrieving MMS 2013 Content Sessions using PowerShell



Stefan Stranger has created a PowerShell script which retrieves all sessions of the MMS 2013 and makes it possible to export the result to a csv file using the Export-CSV cmdlet.

If you want you can do many more fun things with the results, let him know what you created.



Remarks:

Retrieving the website and getting the HTML Tag name elements can take some time to finish, be patient!
You need PowerShell v3 to run this script.


This posting is provided "AS IS" with no warranties.

[OpsMgr 2007 R2] Powershell script to export all product knowledge for rule and monitor for a specific MP

I've been asked to provide knowledge article to application owner in order to help them to determine what instruction to give to support level one for alert raised by SCOM management pack.

With no access to SCOM console, I didn't find an easy way to do it and I also decided to proceed with a powershell script.



Here are the command line I've written to export all product knowledge for rules and monitors for a specific MP. Create a PS1 file named ExportKnowledgeArticleFromAMP.ps1 and copy paste the command line from this post and go down and click download to get the PS1 file.

Usage a this script needs 2 parameters : MP name and Path to create files.
Example:
.\ExportKnowledgeArticleFromAMP.ps1 "Microsoft.Windows.Server.PrintServer.2012" "C:\Temp"

  1. param([string]$MPName, [string]$Path)
  2. # Script to export all product knowledge for rule and monitor for a specified MP 
  3. # usage : .\ExportKnowledgeArticleFromAMP.ps1 "Microsoft.Windows.Server.PrintServer.2012" "C:\Temp"
  4. function MamlToHTML($MAMLText)
  5. {
  6.  $HTMLText = "";
  7.  $HTMLText = $MAMLText -replace('xmlns:maml="http://schemas.microsoft.com/maml/2004/10"');
  8.  $HTMLText = $HTMLText -replace("maml:para","p");
  9.  $HTMLText = $HTMLText -replace("maml:");
  10.  $HTMLText = $HTMLText -replace("</section>");
  11.  $HTMLText = $HTMLText -replace("<section>");
  12.  $HTMLText = $HTMLText -replace("<section >");
  13.  $HTMLText = $HTMLText -replace("<title>","<h2>");
  14.  $HTMLText = $HTMLText -replace("</title>","</h2>");
  15.  $HTMLText = $HTMLText -replace("<listitem>","<li>");
  16.  $HTMLText = $HTMLText -replace("</listitem>","</li>");
  17.  $HTMLText = "<html><body>" + $HTMLText + "</body></html>";
  18.  $HTMLText;
  19. }
  20. # Mainline
  21. # Clear the screen.
  22. cls;
  23. # Get US Culture information.
  24. $ciUS = [System.Globalization.CultureInfo]'en-US';
  25. # Retrieve the Management Pack.
  26. $mps = get-managementpack
  27. $mp = $mps | ? { $_.Name -eq $MPName}
  28. $FolderName = $MPName + " - " + $mp.version
  29. # Create Folder
  30. New-Item -ItemType directory -Path $Path\$FolderName
  31. # Retrieve the Management Pack rules and monitors.
  32. $rules = $mp.getrules()
  33. $monitors = $mp.getmonitors()
  34. cls
  35. # Retrieve the knowledge Article for rules.
  36.  $i = 1
  37.  $j = 1
  38. foreach ($rule in $rules) {
  39.  $article = $rule.GetKnowledgeArticle($ciUS);
  40.  if ($article -ne $Null)
  41.  {
  42.   if ($article.MamlContent -ne $Null)
  43.   {
  44.     $article_text = $article.MamlContent;
  45.     $article_text = MamlToHTML($article_text);
  46.   }
  47.   write-host "Outputing HTML...";
  48.   if ($rule.DisplayName -ne "")
  49.     {
  50.     $RuleName = "Rule - " + [string]$i + " - " + [string]$rule.DisplayName
  51.     }
  52.   else
  53.     {
  54.     $RuleName = "Rule - " + [string]$i + " - " + [string]$rule.Name
  55.     }
  56.   # < > : " / \ | ? * removal
  57.    $RuleName
  58.   $RuleName = $RuleName.replace('<','lower than')
  59.   $RuleName = $RuleName.replace('>','Greater than')
  60.   $RuleName = $RuleName.replace('/','')
  61.   $RuleName = $RuleName.replace('|','')
  62.   $RuleName = $RuleName.replace('\','')
  63.   $RuleName = $RuleName.replace('!','')
  64.   $RuleName = $RuleName.replace('?','')
  65.   $RuleName = $RuleName.replace('*','')
  66.   $RuleName = $RuleName.replace(':','')
  67.   $RuleName = $RuleName.replace(';','')
  68.   $ExportFile = $Path + "\" + $FolderName + "\" + $RuleName + ".htm";
  69.   $article_text.tostring() | out-file $ExportFile
  70.   $i = $i + 1
  71.  }
  72. }
  73. # Retrieve the knowledge Article for monitors.
  74. foreach ($monitor in $monitors) {
  75.  $article = $monitor.GetKnowledgeArticle($ciUS);
  76.  if ($article -ne $Null)
  77.  {
  78.   if ($article.MamlContent -ne $Null)
  79.   {
  80.     $article_text = $article.MamlContent;
  81.     $article_text = MamlToHTML($article_text);
  82.   }
  83.   write-host "Outputing HTML...";
  84.    if ($monitor.DisplayName -ne "")
  85.     {
  86.     $MonitorName = "Monitor - " + [string]$j + " - " + [string]$monitor.DisplayName
  87.     }
  88.    else
  89.      {
  90.     $MonitorName = "Monitor - " + [string]$j + " - " + [string]$monitor.Name
  91.     }
  92.   # < > : " / \ | ? * removal
  93.    $MonitorName
  94.   $MonitorName = $MonitorName.replace('<','lower than')
  95.   $MonitorName = $MonitorName.replace('>','Greater than')
  96.   $MonitorName = $MonitorName.replace('/','')
  97.   $MonitorName = $MonitorName.replace('|','')
  98.   $MonitorName = $MonitorName.replace('\','')
  99.   $MonitorName = $MonitorName.replace('!','')
  100.   $MonitorName = $MonitorName.replace('?','')
  101.   $MonitorName = $MonitorName.replace('*','')
  102.   $MonitorName = $MonitorName.replace(':','')
  103.   $MonitorName = $MonitorName.replace(';','')
  104.   $ExportFile = $Path + "\" + $FolderName + "\" + $MonitorName + ".htm";
  105.   $ExportFile
  106.   $article_text.tostring() | out-file $ExportFile
  107.    $j = $j + 1
  108.  }
  109. } 
Executing the script will create a folder Microsoft.Windows.Server.PrintServer.2012 - 6.0.7004.0 that contains an HTML file for each monitor/rules.




Note :
  • The script sometimes return errors on some monitors or rules - I guess the conversion to HTML is failing - but in that case, the impact is that the HTML file is not created for that rule/monitor.
  • The script can be easily adapted of courses to run on OpsMgr 2012.


Here is a link where you can download my script : ExportKnowledgeArticleFromAMP.ps1



I'll publish a page on my blog >>>> HERE <<<< with all the product knowledge for all the provided MP I've in my environment.


This posting is provided "AS IS" with no warranties.

[OpsMgr 2007 R2][OpsMgr 2012] System Center Management Pack for Windows Server DNS



This management pack help administrators monitor Windows Server DNS



Quick details


Version:7.0.8560.0                Date published:3/29/2013
Language:English

Files in this download

The links in this section correspond to files available for this download. Download the files appropriate for you.
File nameSize
OM_MP_DNS2012.doc306 KBDownload
System Center Management Pack          
for Windows Server DNS.msi
476 KBDownload


Overview

The System Center Management Pack for Windows Server DNS monitors DNS health, availability, configuration, security, and zone-transfer issues on DNS servers running the Windows Server 2003 and Windows Server 2008, 2008 R2 and Windows Server 2012 operating systems.

Note This Management Pack is intended to completely replace the functionality of the previous DNS Management Pack, and as such it is not backwards compatible with them. The old and new management packs can live side-by-side, so you can uninstall the old MP’s if/when you are comfortable with the new Management Pack.


Release History

3/29/2013 - Original English release, version 7.0.8560.0
Top of page
System requirements
Supported operating systems: Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012

Other Software:

System Center Operations Manager 2007 R2 or later
Top of page
Instructions
Please refer to MP Guide


This posting is provided "AS IS" with no warranties.

[OpsMgr 2012] VSAE – Include File Content

David Allen, has posted on April 3, 2013, an article to show how to include your own vbs, ps1 or JS script in your authored management pack.


The include syntax in this example is $IncludeFileContent/Scripts/MonitoringScript.vbs$, and this is generated based on the path of the file.  In this MP, I stored the VBS file in a folder called Scripts, which is why “Scripts/MonitoringScript.vbs” is added to “IncludeFileContent”.

This posting is provided "AS IS" with no warranties.