Archive for the ‘Console’ Category.

Creating a xplat script monitor from the console, System Center 2012 Operations Manager

Announced in the Technet forum last week was the new ability to create a UNIX/Linux Shell Command Monitor. Download the file from here, run it and after importing the file called Microsoft.Unix.ShellCommand.Library.mpb you will be able to create a two and/or three state UNIX/Linux script monitor from within the Operations Manager console.

image

To create a monitor simply start the Create a Unit monitor wizard.

Make your choices:

image

Give the monitor a Name select Monitor target and choose if it will be enabled.

Select how often your script will run on the agent.

In the Shell Command details you need to provide your command or path to binary/script without line breaks. So my little script that checks if a file exists.

#!/bin/bash
if ! [ -f /tmp/OPSMGR.SE ];
then
echo "Error"
else
echo "OK"
fi

Needs to be put in a file on the agent or as a one-liner. Otherwise it wont be possible to continue the wizard and a red exclamation will show, like in this picture

image

Putting the script in one line makes it look like this, I removed #!/bin/bash so the line wont be marked as a comment..

if ! [ -f /tmp/OPSMGR.SE ]; then echo "Error"; else echo "OK"; fi

image

Specifying the Error Expression

image

Specifying the Healthy Expression

image

Finish the wizard and your monitor is now running.

image

Running both OpsMgr 2012 beta and 2007 R2 consoles on the same workstation

Connecting to a OpsMgr 2012 beta management server with a OpsMgr 2007 R2 console doesn’t work either does connecting with the 2012 beta console to a 2007 R2 RMS.

If you like me wants to be able to connect to both a 2012 beta management group and a 2007 R2 management group you can run 2 consoles on the same workstation. Just start with running the OpsMgr 2012 beta setup on your workstation, if an OpsMgr R2 console is already installed it will be upgraded, otherwise just install the console. If you don’t want to go through the setup GUI just run this from an elevated command prompt: setup.exe /silent /install /components:OMConsole /UseMicrosoftUpdate:[0|1]

When this is done, load your R2 media and install the console from that one.

This will give you two folders in %programfiles%:

folder

And also on the Start menu and Programs and Features:

startmenu 

features

Now we are able to run the consoles simultaneously

console

But you will soon notice that the Connect to Server.. windows is showing now and then when opening a console. This is also mentioned in this post:
http://www.opsmode.com/2011/03/manage-multiple-management-groups-with-powershell/

connect to

To get rid of this I edit the shortcut and add /Server:OPS-OMbeta-MS01.opsmgr.se for my 2012 console and /Server:OM.opsmode.local for the 2007 R2 console
"C:\Program Files\System Center Operations Manager 2007\Microsoft.MOM.UI.Console.exe" /Server:OM.opsmode.local
"C:\Program Files\System Center Operations Manager 2012\Console\Microsoft.EnterpriseManagement.Monitoring.Console.exe" /server:OPS-OMbeta-MS01.opsmgr.se

IIS Components when installing OpsMgr 2007 Web console on Windows 2008

When installing the Operations Manager 2007 web console on Windows Server 2008 you need to install the following IIS components:
iis

This can also be installed with a powershell script:

Import-Module ServerManager
Add-WindowsFeature NET-Framework-Core,Web-Metabase,Web-WMI,Web-Static-Content,Web-Default-Doc,Web-Dir-Browsing,Web-Http-Errors,Web-Asp-Net,Web-Net-Ext,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Filtering,Web-Windows-Auth -restart