• Clarification on SQL Server Collation Requirements for System Center 2012

    We have published a new blogpost on the System Center: Operations Manager Engineering Team Blog about SQL Server Collation Requirements.

     

    “There has been quite a bit of confusion over the requirements for SQL Server collation for the various components of System Center. We didn’t make a coordinated effort here to make this as easy as it could and should be. The documentation has conflicts within itself in some cases. We will be cleaning up the documentation over the next few days so that it is consistent and clear. Since the documentation is still component focused, we want to take this opportunity to provide a holistic view of the SQL Server collation requirement across the suite. This will hopefully clear things up and over time it will become even clearer as we make changes in the product itself to be consistent on this requirement.”

    Read more here.

  • Creating a System Center 2012 Operations Manager Alert RSS feed

    In OpsMgr 2007 we had the option to create a RSS Feed for Alerts using the Operations Web Console.

    image

     

    Selecting the RSS button would return the following RSS Feed info.

    image

     

    In System Center 2012 Operations Manager (OM2012) we don’t have that option anymore. But this is not really an issue, because with a little bit of PowerShell magic,
    we can create our own OM2012 Alert RSS feed with all the Alert information we want. And that is exactly what I did when I saw an internal question about this feature
    missing in OM2012.

    Environment information:

      • System Center 2012 Operations Manager with RU1 installed
      • Two Management Servers (OM12MS01 and OM12MS02)
      • OM12MS01 has the web console installed.
      • Server features installed on OM12MS01:
      • Application-Server
      • AS-NET-Framework
      • Web-Server
      • Web-WebServer
      • Web-Common-Http
      • Web-Static-Content
      • Web-Default-Doc
      • Web-Dir-Browsing
      • Web-Http-Errors
      • Web-App-Dev
      • Web-Asp-Net
      • Web-Net-Ext
      • Web-ISAPI-Ext
      • Web-ISAPI-Filter
      • Web-Health
      • Web-Http-Logging
      • Web-Request-Monitor
      • Web-Security
      • Web-Windows-Auth
      • Web-Filtering
      • Web-Performance
      • Web-Stat-Compression
      • Web-Mgmt-Tools
      • Web-Mgmt-Console
      • Web-Mgmt-Compat
      • Web-Metabase
      • NET-Framework
      • NET-Framework-Core
      • RSAT
      • RSAT-Role-Tools
      • RSAT-Web-Server
      • PowerShell-ISE
      • WAS
      • WAS-Process-Model
      • WAS-NET-Environment
      • WAS-Config-APIs

      Pre-requisites:

      What is PowerShel PipeWorks?

      PowerShell Pipeworks is a Framework for making Sites and Services with Windows PowerShell. Read more about Pipeworks here.

       

      Installation steps for creating an OM2012 Alert RSS feed

      1. Download PowerShell PipeWorks Module.
      2. Copy Module to Management Server where you have installed:

      • OM2012 Management Server with Console
      • PowerShell v2.0 or higher
      • ASP.NET

      3. Unblock PipeWorks.1.0.2.6.zip file before extracting (you can also use the PowerShell v3 unblock-file Cmdlet if you have PowerShell v3 installed)
      image

      4. Extract the PipeWorks Module to your default PowerShell Module folder.
          You can check the default folders where PowerShell is looking for PowerShell modules using the following PowerShell command:
        

      $env:psmodulepath   


              image
         
          I personally have created a D:\PowerShell\Modules folder to store the PipeWorks Module and added that path to my psmodulepath variable.
          You can add a new Module Path using the following Command in PowerShell:
        

      $env:PSModulePath = $env:PSModulePath + ";D:\PowerShell\Modules"

          image

      5. Create an IIS Application Pool for PipeWorks
          image
          
          image
         
          Change the Identity of the Application Pool to use the OM2012 SDK Account (Microsoft System Center Data Access Service account).
          image    image

      6. Add PipeWorks Application
          image

          Enter Alias and Select previously created Application Pool. Enter Physical Path where to store the later to be created OM2012 RSS Alert files.
          Create Folder PipeWorks (C:\inetpub\wwwroot\PipeWorks)  if that folder does not exist.
          image

      And configure the OM12_SDK Account to connect as configuration.

      image

      And finally Test Connection.
      image

       

      7. Use PipeWorks Module to create an OM2012 Alert Web Service, which we can use as an RSS Feed.
          a. Open PowerShell ISE
          b. Load PowerShell PipeWorks Module in PowerShell ISE.
             

      import-module PipeWorks -verbose

         c. Create the following Function in the PowerShell ISE:

      function Get-MySCOMAlert {
              <#
              .Synopsis
                  Shows SCOM Alerts
              .Description
                  Shows SCOM Alerts for OM2012
              .Example
                  Get-MySCOMAlert
              .Example
                  Get-MySCOMAlert -ResolutionState New
              .Example
                  Get-MySCOMAlert -ResolutionState Closed
              #>
              [CmdletBinding()]
              param
              (
              [Parameter(Mandatory=$True,
              ValueFromPipeline=$True,
              ValueFromPipelineByPropertyName=$True,
                HelpMessage='What is the ResolutionState of the Alerts you want to filter on?')]
              [string[]]$ResolutionState,
              [int]$First=50
              )
              process
              {
                  if(!(Get-Module OperationsManager))
                  {
                      Import-Module OperationsManager
                  }
                  #To convert string ResolutionStates to integers
                  switch ($ResolutionState) {
                      New {[int]$ResolutionState = 0}
                      Closed {[int]$ResolutionState = 255}
                      default {return "$($ResolutionState) is unknow ResolutionState"}
                  } #end Switch
                  Get-scomalert -ResolutionState $ResolutionState | sort -Property TimeRaised -Descending | select Severity, Priority, Name, TimeRaised -First $First
              } #end Process
      }

      image

      We can test the Function by selecting the function and hitting F8
      Running the following command: Get-MySCOMAlert -ResolutionState "New" -First 2 returns the latest 2 OM2012 Alerts with ResolutionState New.
      image

      d. Convert Function to PipeWorks Web Service by running the following PipeWorks Command:
         

      ConvertTo-CommandService -Command (Get-Command Get-MySCOMAlert) -RunOnline -OutputDirectory C:\inetpub\wwwroot\PipeWorks\Get-MySCOMAlert -Force

      e. Check the Web Service in your Web browser by running the following command from the PowerShell ISE

      Start-Process http://localhost/PipeWorks/Get-MySCOMAlert

      You should see something like this:
      image

      You can now test the Get-MySCOMAlert Web Service by entering a ResolutionState and First (number of Alerts you want to return)
      image

      Result:
      image

      8. Retrieve RSS feed URL.
          Now we have created the Get-MySCOMAlert Web Service we can add some parameters to retrieve the RSS Feed for the OM12 Alerts.
         

      http://localhost/PipeWorks/Get-MySCOMAlert/?Get-MySCOMAlert_ResolutionState=New&Get-MySCOMAlert_First=2&-AsRSS=true

      This will return the RSS Feed for all OM2012 Alerts with a ResolutionState of new and only shows the last 2 new Alerts.

      image

       

      Have fun and let me know some other cool things you have created using PowerShell PipeWorks!!

      DISCLAIMER: THIS PROGRAM SOURCE CODE IS PROVIDED "AS IS" WITHOUT WARRANTY REPRESENTATION OR CONDITION OF ANY KIND EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO CONDITIONS OR OTHER TERMS OF MERCHANTABILITY AND/OR FITNESS FOR A PARTICULAR PURPOSE. THE USER ASSUMES THE ENTIRE RISK AS TO THE ACCURACY AND THE USE OF THIS PROGRAM CODE OR RESULTING EXECUTABLE CODE

    • PowerShell Magazine blogpost: Formatting changes for OM2012 in UR1

      My blogpost on the formatting changes for System Center Operations Manager 2012 in Update Rollup 1 has been published on the PowerShell Magazine website.

      Take a look at my blogpost if you are interested in the PowerShell formatting changes that have been implemented after the release of UR1. Read more

      Technorati Tags: ,,
    • New KBArticle: Understanding Operations Manager Maintenance Mode

      Yesterday we published a new KBArticle about Operations Manager Maintenance Mode.

      It explains everything you want to know about Maintenance Mode.

       

      What is Maintenance Mode?

      Maintenance mode is a feature in Operations Manager to suspend monitoring of an object during regular software or hardware maintenance activities like Software Update installations, Hardware replacements, etc.

       

      Read more here.

    • Let’s Build a Cloud… With PowerShell! – Part 1: Deployment and Configuration

      Our Private Cloud team published a blog post about building a cloud with PowerShell!

      Windows Server 2012 introduces vastly improved Windows PowerShell support with over 2,300 cmdlets to manage just about everything in the platform. This means you can now use Windows PowerShell to automate all of the IT tasks around cloud datacenter management, starting from deploying your cloud infrastructure servers, through on-boarding virtual machines onto that infrastructure, and ending with monitoring your datacenter environment and collecting information about how it performs. Practically everything is automatable!”

      We already knew everything is automatable using PowerShell :-)

      Read more here.

    • CU6 for System Center Operations Manager R2 Released

      We have released CU6 for System Center Operations Manager 2007 R2.

      Cumulative Update 6 for Operations Manager 2007 R2 includes all previous cumulative updates for Operations Manager 2007 R2 and includes all cross-platform updates.

      To download Cumulative Update 6 for Operations Manager 2007 R2, go to the following Microsoft Download Center website:

      Download Cumulative Update 6 for System Center Operations Manager 2007 R2 (http://www.microsoft.com/downloads/details.aspx?FamilyID=694147f8-9691-4833-97af-0de918c60141)

      Cumulative Update 6 for Operations Manager 2007 R2 resolves the following issues:

      • RMS promotion fails if NetworkName and PrincipalNames are not in sync for agents.
      • UI is limited to only 100 MB for the Memory Usage field in the wizard.
      • Additional OIDs in auth certificate are not processed correctly.
      • AEM creates duplicate computer objects in OpsMgr based on Agents NetBIOS name.
      • Cannot open reporting pane on OpsMgr 2007 R2 remote console.
      • Cannot view schedule for scheduled report.
      • ManagementServerConfigTool with the option "promoterms" fails because it stops polling the SDK Service.
      • OpsMgr reports are failing on Windows 7 with the error: "Cannot initialize report."
      • ACS events have "n/a" as their category in the ACS database.
      • Watch agentless monitoring listener to detect failure to respond.
      • SCOM SDK memory leak on cryptography keys and cryptography contexts.
      • After you click Edit Schedule, a message box appears, and you cannot save the change value.
      • Audit events can be lost when the AdtServer process crashes.
      Cumulative Update 6 for Operations Manager 2007 R2 resolves the following cross-platform issues:
      • The installation process for the IBM AIX 6.1 agent incorrectly checks for AIX 5.3 packages.
      • After a system restart, the OpsMgr agent for Solaris may start to run before local file systems are mounted.
      • On Red Hat Linux version 4 and SUSE Linux version 9, LVM disks are not discovered and cannot be monitored.
      • The OpsMgr agent for AIX does not report the arguments for monitored processes.
      • When Microsoft security update MS12-006 is installed on an OpsMgr management server, that management server can no longer communicate with the OpsMgr agent on any Linux or UNIX server.
      • On HP-UX, OpsMgr cannot discover and monitor a logical volume that is composed of more than 127 physical volumes.
      Cumulative Update 6 for Operations Manager 2007 R2 adds the following cross-platform features:
      • Support for IBM AIX 7.1 (POWER).
      • Support for Oracle Solaris 11 (x86 and SPARC).
      Note The new agents for IBM AIX 7.1 and Oracle Solaris 11 are included in Cumulative Update 6 for Operations Manager 2007 R2. You can download the management packs for these new operating system versions by going to the following Microsoft website:

      System Center Operations Manager 2007 R2 Cross Platform Monitoring Management Packs (http://www.microsoft.com/downloads/details.aspx?FamilyID=b15fef5c-e331-4006-8913-be376bb0e0c1)

      Technorati Tags: ,