Hi
Your doubt is well founded. I didn't realise it was really just this one service and absolutely nothing else on this server.
There is no easy way to do this with SCOM - it is an application based around auto-discovery of the applications installed on a server and then automatically deploying the management packs (rules \ monitors and discoveries) to those servers. You wouldn't
have to override \ disable every rule and monitor but you would need to do override the discoveries and then purge the discovered objects from the SCOM database using remove-discoveredmonitoringobject powershell cmdlet.
http://technet.microsoft.com/en-us/library/gg132269.aspx
http://blogs.technet.com/b/jonathanalmquist/archive/2008/09/14/remove-disabledmonitoringobject.aspx
It would be a very big job to achieve a very small amount of monitoring. Is there a reason why you do not want any other monitoring of this server?
A quicker alternative would be to script something that another server does a remote check on this service and generates an alert if it detects that the service is down. You can use win32_service to pull back information about the service.
http://msdn.microsoft.com/en-us/library/windows/desktop/aa394418(v=vs.85).aspx
Cheers
Graham
Regards Graham New System Center 2012 Blog! -
http://www.systemcentersolutions.co.uk
View OpsMgr tips and tricks at
http://systemcentersolutions.wordpress.com/
