I will today try to explain what you need to export all management pack every day. It can be usefull if like to take backup, or just like have all version of the management packs.
Archive for SCOM – Management Pack
IBM have release new version for the hardware management monitoring for OpsMgr.
Now support OpsMgr 2012, very nice one:-)
Below is link for the download and support manuals.
Very nice blog regarding SolarWinds integration to OpsMgrt 2012
Today I past the nive blog about Lync 2010 and OpsMgr from Tom Arbuthnot.
I will recommend you have take look if you have Lync 2010 in your system. Because Tom show how easy is it to setup.
Source: Tom Arbuthnot Blog
Today I have to modify a self made MP. And when I open the MP in the Autoring Console it ask for the Microsoft.SystemCenter.Library MP.
I seached my library of MP’s, but I could not find it. Finaly i found below KB from MS.
To display overrides for a management pack, use the following procedure.
To display overrides for a management pack
|1. In your management server, click Programs, and then click System Center.2. Click Command Shell.
3. In the Command Shell, type the following command:
get-override -managementPack name.mp | export-csv filename
4. A .csv file is created. The .csv file can be opened in Office Excel.
In Office Excel, you may be required to specify that the .csv file is a text file.
- Open SCOM Console
- Goto Authoring
- Open Management Pack Objects
- Right Click Task
- Choose ‘Create a New Task’
- Select Agent Task – Command line, and choose the right Manamgement Pack(never choose ‘Default Management Pack”)
- Give it Task name, Description and choose the Task target.
- In ‘Full path to file’ type cmd.exe, and in ‘Parameters’ type /c type “[FILE LOCATION]”
Sealing a Management Pack is easy. Although, it can be frustrating the first time through. It’s a process that requires a few different pieces to interact, so preparation is key. Going through some simple steps now will save time in the future.
- Create a directory somewhere on a workstation where you’ll be sealing MP’s. For this example, I created the directory c:\MPS
- I also created four directories within c:\MPS
- \Input – this directory will contain the MP to be sealed (the xml file)
- \Output – this directory will contain the sealed MP (the final mp file)
- \MP – this directory will contain all referenced MP’s
- \Key – this directory will contain the pair key file
- Copy MPSeal.exe from the source installation files “SupportTools” directory to the c:\MPS directory.
- Copy sn.exe to the c:\MPS directory
- If you need a copy, the sn.exe utility comes with .NET Framework SDK
- Copy your unsealed MP (xml file) into the \Input directory
- Copy all the *.mp files from the RMS installation directory into the \MP directory
- Usually “%Program Files%\System Center Operations Manager 2007\”
- Also, copy all *.mp files that you’ll be referencing to the \MP directory
- TIP: I’d just keep this directory updated with all available current MP’s (ie; Active Directory, Exchange, etc)
Finally, the c:\MPS directory will look like this.
The two files highlighted:
Command.txt is just a file I created that contains the commands needed to seal the management pack. The MPResources.resources file is automatically created while sealing management packs. This is not anything you’ll need to copy into the directory.
Now, we’re ready to seal our Management Pack.
Open a command prompt and navigate to your work directory (c:\MPS). Run these commands in sequence. (beware of word wrap with these commands)
- sn -k c:\mps\key\PairKey.snk
- sn -p c:\mps\key\PairKey.snk c:\mps\key\PubKey
- sn -tp c:\mps\key\PubKey
- mpseal c:\mps\input\unsealed_mp.xml /I “c:\mps\mp” /Keyfile “c:\mps\key\PairKey.snk” /Company “Your Company” /Outdir “c:\mps\output”
You should now have your sealed MP in the Output directory. And, you’ll have a working directory for later use. Just remember to keep the MP versions in the c:\MPS\MP directory current with your Management Groups. Otherwise, you’ll get version errors while attempting to run the MPSeal tool.
Hint: Once you’ve created the key the first time around, it’s not necessary to create a new key each time you seal a MP. The current key may be reused. So, the only step you’ll need to actually do after the first run is the last step. How’s that for easy!
A note to developers: I’ve had some questions about where the MPResources.resources file mentioned above is created. Specifically, if two build flavor threads (x64 and x86, for example), compiles at same time and try to create this file under sources, one build thread will break.
To solve that problem, execute MPSeal from a different location. Examples below.
To put a monitored object into maintenance mode
- Log on to the computer with an account that is a member of the Operations Manager Administrators role for the Operations Manager 2007 management group.
- In the Operations console, click the Monitoring button.
- In the Monitoring pane, expand Monitoring, and then click Computers.
- In the Computers pane, right-click the computer that you want to place into maintenance mode, click Maintenance Mode, and then click Start Maintenance Mode.
- In the Maintenance Mode Settings dialog box, under Apply to, click Selected objects only if only the computer is to be placed into maintenance mode; otherwise, click Selected objects and all their contained objects.
- Select Planned if this is a planned event; otherwise, leave it cleared.
- In the Category list, click the appropriate maintenance category.
- Under Duration, select and enter the Number of minutes or select and enter the Specific end time, and then click OK. A maintenance mode icon appears in the Computers pane, in the Maintenance Mode column for the computer you selected.