SCOM - Creating the rule and targeting the computer group

PROBLEM:
===========
Creating the rule and targeting the computer group

CAUSE:
=========
We cannot directly Target the custom group while creating the rule.

RESOLUTION:
=============
If we want to target the custom group to any rule then we have to First target any built in groups at the time of creating the rule and disable the rule. Then set the override for the custom group.

Regarding the editing the rule, the user must have permission on the built in group that we have selected in the beginning and the customer group.

The permission can be given from Administrator console\user roles

1. Create your group and add the members you wish to monitor.
2. Create your rule/monitor and target it at a suitable class. For example if the machines you wish to monitor are all SQL servers, you can use the SQL Computers class.
3. Ensure the rule/monitor is disabled by default. To do this, click the General tab in the Properties dialog box for the rule or for the monitor in question, then make sure that the Rule is Enabled check box is cleared (not checked).
4. Create an override for the rule/monitor targeted at your group and sets the Enabled property to True. To do this follow these steps:
a. In the Authoring pane in the Operations Console, locate the rule or the monitor.
b. Right-click the rule or the monitor, point to Overrides, point to Override the Rule or to Override the Monitor, and then click For a group.
c. Click the group that you want to use, and then click OK.
d. Click to select the Override check box, and then click True under Override Setting.

Related Knowledgebase Articles:
==========================

938999 You cannot configure a rule or a monitor to target a computer group in the Operations console in System Center Operations Manager 2007

http://support.microsoft.com/?Id=938999

Move Operations Manager 2007 RMS to new server.

Following are the steps to promote Management Server to RMS:

1. On the Management Server to be promoted, copy SecureStorageBackup.exe and ManagementServerConfigTool.exe from SupportTools folder of the installation media to the install directory (by default, C:\Program Files\System Center Operations Manager 2007).

2. Open a Command Prompt window and change directory to C:\Program Files\System Center Operations Manager 2007

3. Type the command: C:\Program Files\System Center Operations Manager 2007>SecureStorageBackup.exe Restore filename This file is the backed up Root Management Server encryption file required by this procedure.

4. Provide password as required.

5. On the Management Server, type the command: C:\Program Files\System Center Operations Manager 2007>ManagementServerConfigTool.exe PromoteRMS

If you get an error that this Management Server is configured for multiple management group and its not supported.

Check the following registry key HKLM\Software\Microsoft\Microsoft Operations Manager\3.0\Server Management Groups Parent Health Service Send Priority VHA SCOM
We backup the "Parent Health Service" and "Send Priority" Keys and deleted them.

Run the same command again, and it should work

6. If the original Root Management Server is to be demoted to being a Management Server, on the original Root Management Server, type the command: C:\Program Files\System Center Operations Manager 2007>ManagementServerConfigTool.exe UpdateDemotedRMS

7. Go to the promoted Root Management Server, open the services snap-in, and stop the MOM HealthService.

8. Go to the installation directory (default: %ProgramFiles%\System Center Operations Manager 2007) and delete the Health Service State folder.

9. Start the MOM Health Service.

10. When you open the Operations Console the first time, specify the name of the new Root Management Server to connect to.

Reference:
============
How to Promote a Management Server to a Root Management Server Role in Operations Manager 2007

http://technet.microsoft.com/en-us/library/cc540401.aspx

SCOM - How to query Disk ,Memory ,Porcessoe

請參考下面的範例 .謝謝

****************************************************************
select ObjectName, CounterName, convert(varchar(10), DateTime, 120) DateTime, Path,

FullName, SUM(SampleCount) SampleCount, Sum(AverageValue * SampleCount) /

SUM(SampleCount) AverageValue, Min(MinValue) MinValue, Max(MaxValue) MaxValue

from

OperationsManagerDW.Perf.vPerfHourly AS vPerf

INNER JOIN

OperationsManagerDW.dbo.vPerformanceRuleInstance vPRI ON

vPRI.PerformanceRuleInstanceRowId = vPerf.PerformanceRuleInstanceRowId

INNER JOIN

OperationsManagerDW.dbo.vManagedEntity vME ON vPerf.ManagedEntityRowId =

vME.ManagedEntityRowId

INNER JOIN

OperationsManagerDW.dbo.vPerformanceRule vPR ON vPRI.RuleRowId = vPR.RuleRowId and

vPR.ObjectName in ('Processor', 'Memory', 'LogicalDisk')

group by ObjectName, CounterName, convert(varchar(10), DateTime, 120), ObjectName,

Path, FullName

union all

select ObjectName, CounterName, Convert(varchar(10), DateTime, 120) DateTime, Path,

FullName, SampleCount, AverageValue, MinValue, MaxValue

from OperationsManagerDW.Perf.vPerfDaily AS vPerf

INNER JOIN

OperationsManagerDW.dbo.vPerformanceRuleInstance vPRI ON

vPRI.PerformanceRuleInstanceRowId = vPerf.PerformanceRuleInstanceRowId

INNER JOIN

OperationsManagerDW.dbo.vManagedEntity vME ON vPerf.ManagedEntityRowId =

vME.ManagedEntityRowId

INNER JOIN

OperationsManagerDW.dbo.vPerformanceRule vPR ON vPRI.RuleRowId = vPR.RuleRowId and

vPR.ObjectName in ('Processor', 'Memory', 'LogicalDisk')

order by DateTime

SCOM - SDK and Config Service failed to start with error "1053 Could not start System Center Data Access Service on Local Computer"

Symptom
============
When we start the SDK Service, it does not start and the following event is logged:
Could not start the System Center Data Access service on local computer. Error 1053: The service did not respond to the start or control request in a timely fashion. 

Cause
=========
SDK Service times out before starting

Solution
========= Work around this problem, modify the registry to increase the default time-out value for the service control manager.

To increase this value to 60 seconds, follow these steps:

1.    Click Start, click Run, type regedit, and then click OK.

2.    Locate and then click the following registry subkey:
       HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control

3.    In the right pane, locate the ServicesPipeTimeout entry.

Note If the ServicesPipeTimeout entry does not exist, you must create it. To do this, follow these steps:

  a.    On the Edit menu, point to New, and then click DWORD Value.
  b.    Type ServicesPipeTimeout, and then press ENTER.

4.    Right-click ServicesPipeTimeout, and then click Modify.

5.    Click Decimal, type 60000, and then click OK.

This value represents the time in milliseconds before a service times out.

6.    Restart the computer.

Note This workaround may resolve the problem where the service does not start. However, we recommend that you research this problem to determine whether it is a symptom of another problem.

SCOM 2012 - Receiving alerts 'Operations Manager evaluation version about to expire'

The Set-SCOMLicense  cmdlet fails if the management group evaluation expiration time-out has expired.

If the product has been expired, you cannot open SCOM 2012 console and shell. In the situation, you can try the following steps to bring it back.

1.   Change system time.

2.   Open an elevated Windows PowerShell command window;

3.   Type command import-module OperationsManager

4.   Type command Set-SCOMLicense –ProductID xxx

5.   Reboot the management server.

Then you can use your SCOM now.

SCOM - Unable to Modify a custom group - "General communication exception"

1. Need to get the MP from customer and deleted all references of the group UINameSpaceX456707fe0ea4b2a9ddb5b7239bdc9fb.Group.

2. Updated the version of the MP and imported to the management group.

SCOM - Alert Message: "run as account failed verification" Event ID: 7015

Problem:

========

Alert Message: "run as account failed verification" Event ID: 7015     

  

Analyze

=======

Event ID 7015 (Error):
Description:
The Health Service cannot verify the future validity of the RunAs account TEST\xxx for management group xxx. 
The error is Logon failure: unknown user name or bad password.(1385L).

Solution

========= 

Runas profile was less secure. We changed it to more secure.

  

More Information
================
Comparing More Secure and Less Secure Distribution

Operations Manager distributes the Run As account credentials to either all agent-managed computers (the less secure option) or only to computers that you specify (the more secure option). If Operations Manager automatically distributed the Runs As account according to discovery a security risk would be introduced into your environment as illustrated in the following example. This is why an automatic distribution option was not included in Operations Manager.

For example, Operations Manager identifies a computer as hosting SQL Server 2005 based on the presence of a registry key. It is possible to create that same registry key on a computer that is not actually running an instance of SQL Server 2005. If Operations Manager were to automatically distribute the credentials to all agent managed computers that have been identified as SQL Server 2005 computers, then the credentials would be sent to the imposter SQL Server and they would be available to someone with administrator rights on that server.

When you create a Run As account, you are prompted to choose whether the Run As account should be treated in a Less secure or More secure fashion. More secure means that when you associate the Run As account with a Run As Profile, you have to provide the specific computer names that you want the Run As credentials distributed to. By positively identifying the destination computers, you can prevent the spoofing scenario that was described before. If you choose the less secure option, you will not have to provide any specific computers and the credentials will be distributed to all agent-managed computers.

Distribution and Targeting for Run As Accounts and Profiles
http://technet.microsoft.com/en-us/library/hh431855.aspx