Shyam_84728
Mar 09, 2011Nimbostratus
Not able to configure SCOM 2007
Regarding your first question about the SCOM deployment and the SQL Server (instance) not being found, I would suggest first running the Prerequisites checker (i.e. "Check Prerequisites") that comes with the SCOM 2007 R2 setup package. If you claim that MS SQL Server 2005 is installed on the host that you are trying to point the SCOM installer to, make sure also you point to the appropriate instance of the SQL Server. You may have multiple instances of SQL Servers running, as you mentioned you have also SQL Express installed. It is possible that the MS SQL Server 2005 instance is not running. Make sure the SQL Server (MSSQLSERVER) service is running (using the Services Control Manager) and when you specify the SQL Server in your SCOM 2007 R2 setup, make sure you point to this instance.
There could definitely be other reasons for your issue. I would recommend reading up the following thread on a similar topic: http://social.technet.microsoft.com/Forums/en-US/operationsmanagergeneral/thread/47f797a1-7646-4f90-8b2e-28a3ce20a683
About the other question, regarding the F5 Management Pack interacting with SQL Server, the answer is yes, there is an F5_ManagementPack SQL database created through the deployment of the F5 MP and this database stores/caches the discovered F5 device configuration settings and other (static) data related to general F5 device properties. But everything else (i.e. statistics, monitoring state, health state, etc) is written into the SCOM database through the SCOM Health Service (and not directly).
Julian