Update Rollup System Center 2012 R2 is Now Available

April 23rd, 2014


  • Data Protection Manager — KB2958100,
  • Operations Manager — KB2929891,
  • Orchestrator — KB2904689,
  • Service Manager — KB2904710,
  • Service Provider Foundation — KB2932939,
  • Virtual Machine Manager — KB2932926
  • Chocolatey for Open Source

    April 21st, 2014



    DPM Installation Error ID:820

    April 19th, 2014


    When you install DPM 2010, right after the prerequisites  verification you receive an error  “Verify that Windows Management Instrumentation (WMI) Service is running. if…


    in order to fix this issue, you need to reinstall WMI , this is how to do it

    From an elevated Command Prompt

    1. Disable and stop the WMI service.

    sc config winmgmt start= disabled

    net stop winmgmt

    2. Rename the Repository folder under C:\Windows\System32\wbem to Repository.old

    3. Run the following commands.

    Winmgmt /salvagerepository %windir%\System32\wbem

    4. Re-enable the WMI service and then reboot the server to see how it goes.

    sc config winmgmt start= auto

    Management Pack Development Training

    April 17th, 2014

    System Center 2012 R2 Operations Manager Management Pack




    Microsoft Azure Brazil South region is now in public preview.

    April 17th, 2014



    DPM 2012 R2 Support Windows 2003 server

    April 17th, 2014


    Don’t be surprise , DPM 2012 R2 doesn’t support Windows server 2003 ,   the rollup update is coming shortly and it will fix the issue.

    I know if Shreesh said that it will happen :)


    Do I need to run maintenance on MY SCOM DBs ?

    April 17th, 2014


    This question came from Momo my DBA Friend, I have SCOM 2012 installed , what kind if maintenance Plan I need to run, Momo meant DBCC check, Index rebuild etc..

    my answer nothing , you don’t need to run any maintain on SCOM DBs and the  reasons are the following :

    1- there is a rule name “Optimize Indexes” that execute a daily database maintenance it calls a Store Proc name “p_OptimizeIndexes” , by default the rule runs once a day  at 2:30 AM , you can change the time (Configuration Tab,View DS  ),


    the index optimization Store Proc has the following


    SCOM Management Pack for SQL Server Analysis Services

    April 17th, 2014


    There is always something new , in the System Center area,  there is a new SQL Server Analysis Services released early January 2014

    it supports the following :

    1- SCOM 2012 and later

    2- Virtualized SSAS instances

    3- Clustered SSAS instances

    Download the MP 

    From Microsoft web site :

    System Center Management Pack for SQL Server 2008 Analysis Services

    System Center Management Pack for SQL Server 2012 Analysis Services

    Monitoring Pack Purpose

    Monitors Scenarios

    1- SSAS Instance monitoring

    2- SSAS Database monitoring

    3- SSAS Partition monitoring

    Health Rolls Up :


    a well detailed article please visit Oleg’s Blog

    ldm threshold reached in DPM

    April 17th, 2014


    The Issue started with the ldm threshold reached and we had to delete all the protection group and recreate then.

    Due to this mass deletion of protection group. The pressure on the garbae collection job mounted as it had to delete lot of objects from sql database.

    Now whenever the garbage collection job ran it increased the size of the tempdb which would consume almost all the space on the drive.

    In order to find what query the garbage collection gets stuck we used this script.


    the result Was:


    Ran the garbage collection job along with this script and waited for tempdb to grow abnormally.

    We got following output from the powershell script.


    to fix the issue :


    A huge credit to Abhishek   from the DPM Support Team

    this is just a snapshots , from the resolution , if you get this error , don’t try to run the query on your own, i really recommend to contact MSFT support

    OPSMGR execution of CLR code

    April 17th, 2014

    if you just installed SCOm m, and received the following ERRO , this is because CLR is not enabled  on your SQL Server


    in order to resolve this issue , run the following command in SQL server that host your SQL server DBs