Ever wanted to dig into a management pack but could not because it is sealed? One workaround is to import the management pack into a management group and then export it. There is a much quicker way to do this using PowerShell and the SDK.
Attached is a small script that will do the trick. The prerequisite for this script to work is that you have the OpsMgr console or Management server and PowerShell installed.
The script is attached to this post.
Here is how you can run the script to get the XML representation of a sealed MP:
powershell d:\MpToXml.ps1 -mpFilePath:’d:\Microsoft.Exchange.Server.2003.Monitoring.mp’ -outputDirectory:’d:\’
When importing management packs into a management group, you should still use the sealed version as it provides a lot of benefits for upgrades and rolling back changes compared to unsealed management pack which you can easily modify.
This posting is provided «AS IS» with no warranties, and confers no rights.
Use of included scripts are subject to the terms specified at
Ever wanted to get rid of that poor quality System Center Operations Manager 2007 banner from across the top of all the default reports and replace it with your own branding?
It’s really quite simple….. Читать далее…
I was having trouble finding this post on the old SMSandMOM blog without a direct link, and saw this question asked on an alias so I thought it would be worth posting again on the new blog site for ConfigMgr 2007. This post describes how to move the Site Database for Configuration Manager 2007 to another drive, or another computer running SQL 2005. Читать далее…
Agent proxying needs to be enabled for a health service to submit discovery data about other computers
This looks like it is coming from the Root management server, but the details give you a GUID to the actual server with the error. It looks like this:
Details:Health service ( 168645A4-6B9C-31C6-801D-11B6B355091D ) should not generate data about this managed object ( F227C8F1-E50E-F847-9378-45EB7135B901 )
In order to get the actual name of the monitored device you need to use PowerShell. Don’t use the PowerShell that you find in Programs -> WindowsPowerShell 1.0 since this does not have the SCOM snap-in included. Go to Programs -> System Center Operations Manager 2007 -> Command shell then execute the following command. Replace the GUID with the one that your alert specifies.
Get-MonitoringObject -id:’FED0B867-F9AE-ACAF-4CCF-311DD92789C9′ | ft DisplayName
Then to enable Proxying:
Access the Administration Node and locate the agent under Agent Managed. Right click the node you found after you execute the above command. Select Properties. Click the Security tab. Check Allow this agent to act as proxy…
SC Operations Manager 2007 SP1 — Configuration Steps: SCOM2k7 Basic Service Monitor with a Diagnostic and a Recovery for a Stopped Service
We can use SCOM2k7 to solve many of the operational challenges faced in maintaining healthy Windows Servers. In this scenario I will generate a Basic Service Monitor. The intent of this Basic Service Monitor is to ensure SCOM2k7 offers a ‘Critical Alert’ when the specific Service of focus is stopped (in this case I am using the Print Spooler Service — but this could be a core Line of Business Application Service as another example). In addition, I then author a Diagnostic. A Diagnostic in SCOM2k7 is programmatic logic that determines what else was occuring when the Service stopped (or runs a custom diagnostic application as another example). Finally, I generate a Recovery. A Recovery in SCOM2k7 is programmatic logic that restarts the Service (in this example — again it could do anything programmatically necessary).
Here are the general steps: Читать далее…