Without wanting to decend into analysing the small print but 1. I did not mention anywhere "I can't use, I can't do'. It is a minor inconvenience for the SQL guys who have delegated restricted view of Ops console, but since the system health can be got at from other nodes under SQL MP such as Database engine state etc, they are happy enough, just though it would be nice if there was an EASY workaround. 2. Can't recall ever seeing anywhere a requirement that all patches MUST be applied before asking for help or advice on this site! I am sure many people on here run environments below the latest CU/Patch level - applying a CU can be a timely operation in large organisations who may not have the resource to keep up to the latest patch release. 3. My 'idea (if I don't have a problem I don't upgrade the software)' is not that extraordinary and is based on resource available to manage the SCOM infrastructure, therefore if it aint broke dont fix it works pretty well, esp since it is possible a CU can cause other issues eg CU4 stopping service in W2k8 servers - hence the need for further CU's. Infact that same advice was given to me from Kevin Holman, who I regard as a bit of a SCOM Legend, when I posted a query on applying CU2 http://social.technet.microsoft.com/Forums/en-US/operationsmanagergeneral/thread/8bfeeddb-2294-4eb3-a1ba-196fd86f43f7 I have had no major issues since CU1 in my environment to warrant the effort of applying a new CU...yet, however I would never say never, and if I've the time to do it then yes I'd love to get up-to-date, esp given that I'm very keen to adopt 2012 ASAP and there is likely a minimum CU level to allow an in-place migration which I'm assuming will be well above CU1!! I will apply the newer SQL MP as it is much easier to rollback to a previous MP if customizations have been done according to best practice. Cheers

3. My 'idea (if I don't have a problem I don't upgrade the software)' is not that extraordinary and is based on resource available to manage the SCOM infrastructure, therefore if it aint broke dont fix it works pretty well, esp since it is possible a CU can cause other issues eg CU4 stopping service in W2k8 servers - hence the need for further CU's. Infact that same advice was given to me from Kevin Holman, who I regard as a bit of a SCOM Legend, when I posted a query on applying CU2 http://social.technet.microsoft.com/Forums/en-US/operationsmanagergeneral/thread/8bfeeddb-2294-4eb3-a1ba-196fd86f43f7 right! i don't understand why microsoft makes the Service Pack or the Patch for the application....great claim "if works why i need to improve them?". the CU5 resolve the unexpected reboot of services plus many bug fix. the KB 2470949 resolve the performance counter error of ws2008r2....but no matter....because i don't have any kind of problem and so i don't need any kind of patch. good work SS.Net MCITP Enterprise Administrator - MCTS Virtualization - Operations Manager 2007 - Exchange Server 2007 - MCSE-M S.Net Blog WindowServer.it WindowServer.it Learning Portal

if its not a clustered sql you dont need to enable proxy for that now. But setting proxy enabled is actually not a bad thing (have never seen any exploit of that one). In most environments where I go we end up either turning it on for 65% of machines (covering any important box) so the other 35% is not a big issue anymore. So in some acses we just turn it all for every machine. There are many fixes in between CU1 and CU5. not only for the agents, but especially also for the scom server side. It is also possible to upgrade the server side and not the agents if you are afraid of that. Yes, in some cases the updates caused some issues as well, but as far as I know I dont see any issues with CU5. Doesnt say that thats your problem. A specific cu level is not needed for you to get answers here, however many things have been fixed with CU fixes and it is at times difficult to figure out if you have an already solved issue or if this is a new one. This is also why people ask what CU you are on and it is best to be at a current level (CU5), or at a near current level (CU4 where still many are at). If you call customer support they will mostly try to first get you to the latest CU level and re-produce the issue. Also for reasons I gave above. now for the issue at hand. I would expect you to see the health state of those computers when going to the monitoring pane and on the left hand side to Microsoft SQL Server -> Computers. In any case first try to update the sql mp. read the mp guide as well, especially if you are not using the run as profiles for sql already in the current version. as far as I know you dont need a specific cu version in order to upgrade the agent to a scom 2012 agent. But would still say it is best to move to CU5 for both servers and agents first. hope it helps.Bob Cornelissen - BICTT (My BICTT Blog) - Microsoft Community Contributor 2011 Recipient

I believe that CU5 will be required for the server components at least before upgrading to 2012. As far as why the SQL Servers don't appear in the view in question, you might want to look at the Operations Manager Event Log on the RMS. Look for errors coming from the Config service or Health Service. Its possible that GroupCalc is having issues putting the machines into the right group to appear in the view, or that the Agents are not getting updated HealthService configurations.Michael Pearson OpsMgr Performance Test Team http://blogs.technet.com/michaelpearson/ This posting is provided "AS IS" with no warranties, and confers no rights. Use of attachments are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm

Hi, recently I have noticed a small number of my SQL machines are NOT being discovered/displayed in the Microsoft SQL Server management Pach Computer node in the monuitoring pane of my SCOM 2007 R2 console. Strangely though in the Database Engines stae view node of the SQL MP the missing agents ARE appearing OK and are healthy for SQL Database and SQL 2008 DB. I also notice in the general Windows Computers State View node, where I have personalized the view to include SQL DB Engines, the SQL agents are listed in here too. So it just looks like an issue of not appearing in SQL Computers state view node. I have tried bouncing the health service and also done a repair and uninstall/reinstall of agent but has made no difference. any suggestions as to why the agents areent appearing under the SQL computers state node. Any help much appreciated...

Hi, Regarding the issue that SQL machines could not be discovered, please also check the settings and configurations referring to the management pack guide: SQL Server Monitoring Management Pack http://www.microsoft.com/download/en/details.aspx?id=10631 Meanwhile, please also check the issue referring to the following posts: Configuring Run As Accounts and Profiles in R2–A SQL Management Pack Example http://blogs.technet.com/b/kevinholman/archive/2010/09/08/configuring-run-as-accounts-and-profiles-in-r2-a-sql-management-pack-example.aspx SQL Database Properties Not Discovered http://blogs.technet.com/b/jimmyharper/archive/2009/06/11/sql-database-properties-not-discovered.aspx 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.

did you have enable the proxy-agent for the sql machine? http://opsmgradmin.blogspot.com/2011/10/agent-proxy-on-scom-agents.html SS.Net MCITP Enterprise Administrator - MCTS Virtualization - Operations Manager 2007 - Exchange Server 2007 - MCSE-M S.Net Blog WindowServer.it WindowServer.it Learning Portal

Hi, not agent proxy NOt enabled - I did not set this deliberately as it was my understanding you only set this on specific agent types, like DC's and clustered nodes etc? The missing machines are standard (virtualised) SQL servers and some other identical SQL virtual machines built from same template are showing in the Computers State view and these DON'T have proxy enabled either.

go to the active alerts and search any kind of error about the agent services. could be an installation issue (check if the last sql MP are installed and check the version of SCOM CU). for my experience the agent must be enabled also for sql machine.....for the cluster, vmm, exchange, lync, ect... SS.Net MCITP Enterprise Administrator - MCTS Virtualization - Operations Manager 2007 - Exchange Server 2007 - MCSE-M S.Net Blog WindowServer.it WindowServer.it Learning Portal

No recent alerts for errors on the affected agent machines. Had already reinstalled agent with no issues, but problem remained. I am only at CU1, have deliberately not applied subsequent CU's as some of the issues with them would have affected my environment and the advice at the time was only apply a CU if it addresses an issue for you. At this stage I am reluctant to apply the latest CU5 as 2012 is very much on the horizon and am happy to stay at CU1 until I move to 2012 (unless there was an urgent issue which the CU fixes). I do notice however that a newer SQL MP 6.1.314.36 is available - I had it downloaded but not applied. I will give that a try and see if it resolves the issue - am not overly keen to enable agent proxying as MP guide says only to do so if monitoring clustered resources which was my understanding all along and not relevant in this instance. Cheers

wo wo....stop. you can't say "i've a problem, i can't use, i can't do" if you don't apply the update. the CU1 was released over 1 year ago.....you install the patch just one time for year? before ask help you MUST apply all the patch....and if the problem are still present you can write an email, call the PSS, call my brother.... so: 1) install the CU5 and apply the new agent for the sql server 2) install the new MP for SQL (and for the other software) IMHO your idea (if i don't have a problem i don't upgrade the software) is out of the world SS.Net MCITP Enterprise Administrator - MCTS Virtualization - Operations Manager 2007 - Exchange Server 2007 - MCSE-M S.Net Blog WindowServer.it WindowServer.it Learning Portal

Hi I'd agree that this is unlikely to have anything to do with a cumulative update and like you, I prefer to fix one problem at a time rather than potentially create new ones by adding the cumulative update. Is there anything "particular" about the SQL Servers that are not showing up? - what version of SQL are they ? And with what Service Pack? - has the computer been renamed since SQL was installed? - does the windows agent show up as healthy in the windows computer state view? - do you have other SQL components (e.g. reporting services \ analysis services \ integration services) also installed on the server? - are they default and \ or named instances? Cheers Graham New SCOM 2012 Blog! - http://www.systemcentersolutions.com/blog/ View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

Long shot to finish then - can you check to make sure that no overrides have been set against any SQL discoveries for these machines ?? If the database discoveries haven't been overridden then it is possible that the SQL Server computers "objects" have been removed from SCOM but not the discovered databases. New SCOM 2012 Blog! - http://www.systemcentersolutions.com/blog/ View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

Had checked that as i knew i DO have an override in place to 'undiscover SQL role' - common use case I got from community where you may need to ignore machines the have the likes of SQLEXPRESS installed and there are not full blown SQL which our SQL team aren't interested in managing. Anyway no the missing ones aren't in that override so dead end me thinks! I'll try and come back to this one when I have a bit of spare time and if I get anywhere I'll post the resolution if I find one!! Cheers...

Thanks for all the replies Hi Graham, sorry for late reply - have another issue I've been dealing with (and may have to post on). Anyway, Re your Queries, no there is nothing particular with the machines not showing in SQL Computers node - all the machines are VM's built from a template and SQL installed in a 'standard/consistent' way - all SQL2008 R2. Compuiters have not been renamed - the only thing I can think of is that the agent may have originally been installed before the SQL team got round to installing SQL after servers provisioned, however I have since uninstalled/reinstalled agents which should negate this possibility? windows agent shows up healthy in windows computer state view. Basically the details can be seen in other nodes of the Microsoft SQL server state views, such as Database engines, Database State - it just doesn't show up in SQL computers state view. the only curious thing I can comment on is that in Database Engine state, the column for SQL 2008 agent shows healthy, but in SQL agent State view the machine state does show up and is healthy but under column SQL 2008 agent Job, there is no green circle (healthy or not monitored) for the 'missing' macheine. Not sure if that makes much sense. Like I say its just a minor inconvenience as the SQL guys can get what they need from other nodes in the monitoring console! Thanks everyone for your replies!!

Could you go to Authoring, Groups and find the SQL Computers group - then right click and View group members ... are the SQL Servers listed there? Also check the SQL instances group? I suspect they will be in this one but not the SQL Computers group.New SCOM 2012 Blog! - http://www.systemcentersolutions.com/blog/ View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

Graham, no the missing machines don't appear in either of these groups. More curious is that I also checked some other groups, such as SQL 2008 computers, SQL 2008 DB engine group etc and not showing up in their either - even though they DO show in the relevent state nodes under SQL MP monitoring pane. Though i'd found the issue - I checked WMI repository which says was inconsistent so I ran salvage and rechecked it which now says consistant. However no change in console affter ininstalling agent which I hoped would discovery the machine correctly the a good WMI repository this time! Think I'll just write this one off for now...