Hi Everybody, I have a number of SQL instances on non-domain member servers, they are currently being monitored by SCOM using certificates but the SQL instances are not being monitored. I have created a local account on each of these servers called 'sqlmonitoring', I have given this account local admin and also given it sysadmin rights in the SQL instance. I then created a new 'simple account' in Run As Accounts, and associated it to my server for distribution. I then went to the SQL Discovery Profile and the SQL Monitoring Profile and added in the new Run As Account and associated it to the specific db engine instance I wanted to monitor. I would have expected this to work, but it doesn't. In the SQL MP instructions the low privilege instructions indicate to create a low privilege account of type Action Account, I can't use this as it demands a domain name, but as this is not on a domain I have used the simple account option. Has anybody successfully managed to monitor a SQL instance not on a domain? I am using SCOM R2, the SQL boxes are all SQL 2008 and SQL 2008 R2. I should note that the server monitoring is working fine, it's just the SQL monitoring which I can't get working. Any help is greatly appreciated. Thanks, Michael

This article of kevin holman gives the basics of SQL runas accounts and links to the "deep-dive". http://blogs.technet.com/b/kevinholman/archive/2010/08/16/sql-mp-version-6-1-314-36-released-adds-support-for-sql-2008r2-and-many-other-changes.aspx Rob Korving http://jama00.wordpress.com/

A more specific guide that Kevin has done for SQL is this one: http://blogs.technet.com/b/kevinholman/archive/2010/09/08/configuring-run-as-accounts-and-profiles-in-r2-a-sql-management-pack-example.aspx You should use the Action Account option and just type in (I think) the local machine name. You can just type this in. Cheers GrahamView OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

Hi, Firstly, I think we should ensure the server which hosts SQL Server is managed and the agent has been installed properly: What does it take to monitor servers in workgroup from SCOM http://blogs.msdn.com/b/nitgupta/archive/2009/09/28/what-does-it-take-to-monitor-servers-in-workgroup-from-scom.aspx Monitoring agents in an untrusted domain or workgroup using Operations Manager 2007 http://support.microsoft.com/kb/982910 Step by Step for using Certificates to communicate between agents and the OpsMgr 2007 server http://blogs.technet.com/b/operationsmgr/archive/2009/09/10/step-by-step-for-using-certificates-to-communicate-between-agents-and-the-opsmgr-2007-server.aspx Then check if the SQL Server can be monitored. Hope this helps. Thanks. Nicholas Li - MSFT Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

hi Nicholas I think this is the case as from the original post (first line) - "they are currently being monitored by SCOM using certificates". I think it is just a Run As Account \ Profile issue - perhaps the original poster can confirm. Cheers Graham View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

Graham, thank you very much for your reminder. According to the current situation, I also suspect this is related to the security settings. Michael, please check your considerations referring to the following guide and see if you can get some hints: Security Considerations http://technet.microsoft.com/en-us/library/dd279700.aspx If you need further investigations or you have any updates, please feel free to let us know. Cheers. Nicholas Li - MSFT Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.