Archive

Posts Tagged ‘Authoring’

SCOM2007 Performance monitor data and alert description

28/07/2011 Leave a comment

 

Yesterday I got a question about adding a specific data to an alert description. the problem was with a custom performance counter rule for  “% Processor Time”. Every time the total CPU is above 95% in the last 2 samples an alert is generated. the problem with this monitor is that the sampled value in not part of the automatic generated alert.

If we take a closer look, we will see that the alert description have a value filed, but this filed indicate the number of samples taken and not the last value that was monitored.

image

image

every alert have additional information, to view this info we will need to open the alert.
under the alert description there is a link named “view additional knowledge” , clicking on it and choosing the “Alert context” tab will show us more information.

image

and here it is, the “last sampled value” parameter.

The question now is: “How can we take the “Last sample Value” from the alert context and use it in the alert description?”

when clicking the image button the last sampled value is not part of the populated data.

image

?!?!?!?….did we worked for nothing ? if the data available in alert context, how can we get it? which parameter can we use to show it in the description.

Solution:

the easy way I found is to check the alert data using get-alert cmdlet.

get-alert | where{$_.Name –eq ‘my alert name‘}

and here it is:

image

changing the alert description and adding $Data/Context/SampledValue$ solved the problem

Instance $Data/Context/InstanceName$
Object $Data/Context/ObjectName$
Counter $Data/Context/CounterName$
Has a value $Data/Context/SampleValue$
At time $Data/Context/TimeSampled$

Advertisements
Categories: OpsMgr Tags:

SCOM Authoring console and the mysterious Microsoft.SystemCenter.Library.mp version 6.1.7221.61

07/06/2011 1 comment

Updated – 13/08/2011

Microsoft released a new KB Article that allows us to download the latest version of the Microsoft.SystemCenter.Library management pack. now we can reference it in the Authoring Console.

NOTE: Do not import the Microsoft.SystemCenter.Library management pack into your management group. You do not have to do this. In fact, in a very limited set of circumstances, importing this management pack can result in the need to restore the Operations Manager database from backup.

________________________________________________________________________

After upgrading my SCOM server to CU4 I can not open any management pack using SCOM authoring console, the following message appear “ Referenced management pack not found…”

image

OK, lets try to locate the file…the file is not part of the installation files of CU4 and is not part of any MP that is available to us on System Center Marketplace (the new pinpoint site). the only file with a same name is located under “c:\program files\system center operations manager 2007” and the date point to an old file (unfortunately MP files are missing the version property).

What is really happening here?
It is possible that SCOM team update the MP without replacing the file?

The answer we looking for is in CU4_Database.sql script. the management pack is updated directly via SQL!!!

image

that mean that every time we export an unsealed MP, the version of Microsoft.SystemCenter.Library.mp will be 6.1.7221.61.

Workaround:

1. Do not use the authoring console “Import MP from..”
image

2. Export the MP from the SCOM console.

3. Open the XML file using text editor and change the version of the referenced MP from:

<Reference Alias="SystemCenter">
  <ID>Microsoft.SystemCenter.Library</ID>
  <Version>6.1.7221.61</Version>
  <PublicKeyToken>31bf3856ad364e35</PublicKeyToken>
</Reference>

To:

<Reference Alias="SystemCenter">
  <ID>Microsoft.SystemCenter.Library</ID>
  <Version>6.1.7221.0</Version>
  <PublicKeyToken>31bf3856ad364e35</PublicKeyToken>
</Reference>

4. Save the file and open it using the authoring console.

Categories: OpsMgr Tags: ,

Enterprise Vault (EV) management pack for Operations Manager 2007 R2 does not automatically discover servers running on Windows Server 64-bit operating systems.

25/01/2011 Leave a comment

Today one of my colleagues, Ronen Tzimbel, show a problem with EV MP. the problem is also documented in Symantec support web site.

First we need to check the supported platform for the MP, as Symantec pointed it seems that there is two different MP’s. one for versions earlier then EV9.0 and the other for EV9.0.

clip_image002

So, what is the problem?

First Symantec deliver the two MP’s with the same name and version, the old one is an XML file and the new one is MP file…goodbye for MP upgrade!!! and if you will try to import the new MP you will end with two MP files, sealed and unsealed.

The other thing is that the above link show us how to resolve the problem only with the unsealed MP, and the environment should only used x64 OS with x32 EV.

What should I do?

in our environment we have two different implementation, EV 8.X for production (x32 OS) and EV 9.0 for testing (x64 OS) , both environments are monitored by the same operations manager server, so what do we need to do?

Resolution

1. Copy the EnterpriseVault2007.XML file to a temp directory.

2. edit the EnterpriseVault2007.XML.

3. locate the following lines and add the marked line:

          <RegistryAttributeDefinitions>
            <RegistryAttributeDefinition>
              <AttributeName>Enterprise_Vault_Installation</AttributeName>
              <Path>SOFTWARE\KVS\Enterprise Vault\Install</Path>
              <PathType>0</PathType>
              <AttributeType>0</AttributeType>
          <RegistryView>32bit</RegistryView>
            </RegistryAttributeDefinition>
          </RegistryAttributeDefinitions>
4. save and import the saved MP.

this change tells the SCOM agent to look in Wow6432node as well as the regular HKLM\Software part of the registry. and it valid only with SCOM R2!!!

This solution is good for every 32bit application discovery that could be installed in 32 or 64 bit OS.

Categories: OpsMgr Tags: ,

Can we run a custom rule during specific hours?

28/08/2010 Leave a comment

Cameron Fuller has another great Operations Manager post over on System Center Central , this time about how to create a custom rule that runs on only during specific hours. i tried to find a quick and easy way to do this, without the need to know scripting languages or high level writing with Operations Manager Authoring console. Cameron done a great job explaining it.

“In MOM 2005 it was pretty straightforward to create a rule which would occur only during specific hours of the day. With Operations Manager 2007 this became a lot more complex to accomplish…”

For all the details see Scheduling a custom rule to run during specific hours – without a degree in XML.

Categories: OpsMgr Tags: ,

How To Associate Run As Profile to a script

13/04/2010 Leave a comment

Recently i needed to run some scripts under a specific user. here are the steps that help me:

1. Open the console and go to “Administration”, go to “Run As Configuration” and choose “Profiles”

clip_image002

2. Right click on “Profiles” and choose “Create Run As Profile…”

clip_image002[4]

3. Create the profile and save it to a specific MP.

clip_image002[8]

Choose the run as account or create one and select the objects that this account will run under.

clip_image002[10]

4. When finished create the rule or monitor with the script and export the MP.

5. Edit the MP and search for the profile name and copy it:
<TypeDefinitions>
<SecureReferences>
<SecureReference ID="RunAsProfile_MyCustomProfile" Accessibility="Internal" />
</SecureReferences>
</TypeDefinitions>

6. Set the run as attribute in the monitor or rule (in this example in a unit monitor, marked in red)
<UnitMonitor ID="MyCustomMonitor" Accessibility="Public" Enabled="true" Target="MicrosoftWindowsLibrary6172210!Microsoft.Windows.Computer" ParentMonitorID="Health!System.Health.AvailabilityState" Remotable="true" Priority="Normal" Run As =”RunAsProfile_MyCustomProfile" “TypeID="MicrosoftWindowsLibrary6172210!Microsoft.Windows.TimedScript.TwoStateMonitorType" ConfirmDelivery="false">

7. Now it’s time to set the user account which the script will run under, search the script body and add the marked test after the </scriptBody> tag:
<ScriptBody>’ Enter a script that outputs a property bag ‘ Example VBScript: ‘ ‘ Dim oAPI, oBag ‘ Set oAPI = CreateObject("MOM.ScriptAPI") ‘ Set oBag = oAPI.CreatePropertyBag() ‘ Call oBag.AddValue("Status","OK") ‘ Call oAPI.Return(oBag)</ScriptBody>
<SecureInput>$RunAs[Name=”RunAsProfile_MyCustomProfile”]/Domain$[Name=”RunAsProfile_MyCustomProfile”/UserName$</SecureInput>

8. and that’s it. import the MP and check if it works.

Categories: OpsMgr Tags: ,