Archive for the ‘tool’ Category.

Whats running on the agent…?

Ever wanted to now what rules, monitors and discoveries is running on the OpsMgr agent? I sure did..

Now the answer is a great Powershell script written by Stefan Stranger.

It is to be found here:

Making Gateway approval easier

I am right now deploying a lot of Gateway servers so to make the Gateway approval a little easier I wrote a little script.
There is probably some way of doing this even better, but here goes:

$MS = Read-Host “FQDN of the Management Server”
$GW = Read-Host “FQDN of the Gateway”
$Site = Read-Host “Name of the site”

& “Microsoft.EnterpriseManagement.GatewayApprovalTool.exe” /ManagementServerName=$MS /GateWayName=$GW /Site=$Site /Action=Create”

When using the GateWayApprovalTool you need to have Write Permissions on the SQL Instance that holds the OpsMgr database.

1E System Center Watcher Tool v1 released

I couple of weeks ago I had the pleasure to beta test Dan Kregors tool OMWatcher. And I must say, this is a great tool that I will use at many customer sites…

This is the answer when some one is asking: “But who is watching the watcher?” Meaning, who is monitoring OpsMgr. Well the answer i OMWatcher!


The 1E OMWatcher tool for System Center Operations Manager 2007 fills an important, and often overlooked gap in every OpsMgr environment.

Arising from the question…

“Who’s watching the watcher?”

… 1E OMWatcher is designed to monitor the 3 critical service on the Root Management Server (SDK, Config and HealthService). 1E OMWatcher will proactively mitigate unnecessary and potentially expensive downtime by ensuring the RMS is active (via a ping), and taking remedial action should one of the core RMS services stop. In addition, 1E OMWatcher will notify administrators (via email) were an issue arises.

1E OMWatcher should be installed on a server other than the RMS (preferably on a secondary Management Server), and configured to run under an account that has local administrative rights on the RMS.

Key Features
  • Actively pings the RMS at regular polling intervals, alerting (via email) should the RMS not respond (indicating the potential for the server to be offline).
  • Checking the status for the 3 OpsMgr services, ensuring they are running. In the event that a service is stopped, OMWatcher will attempt to restart the service, and will alert (via email) that the service had stopped.
  • Checking the startmode for the OpsMgr service, they are not set to disabled. In the event that a service is set to disabled, OMWatcher will set the service to Automatic, restart the service, and will alert (via email) that the service was set to Disabled and stopped.

More here:
Download here (registration required):