oglede RE: Re: SystemCentre 2012 Licensing Model
Thanks for the response, if what you say is true that is still pretty neat in my opinion. Cheers

oglede post a question under Operations Manager.
SystemCentre 2012 Licensing Model
I understand System Centre 2012 introduces a model whereby no license purchase is required for the Management Server or associated SQL Servers as long as SQL is used soley to host the System Centre Databases i.e "Licences are now only required for the endpoints being managed". Can somebody please clarify what this means as far as SQL licensing is concerned? Does this mean that we can commission a dedicated SQL 2008R2 Standard or Enterprise server with multiple processors to host SCOM 2012 without having to pay for the SQL license?  Sounds too good to be true!! Thanks in advance

oglede post a question under Operations Manager.
SPN's for Named SQL Instances
Before I log this out with Microsoft, would anyone happen to know whether use of SPN’s on named SQL Instances is bad practice from a Kerberos perspective?   We had a SCOM issue earlier today whereby all of our local & mgmt server consoles stopped working.  We then discovred that the SQL application logs were full of this error:  Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: 172.xx.xx.xxx] I then put my Sherlock cap on and discovered that one of my SPN's for the SQL Service had been deregistered:  The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ MSSQLSvc/DC1-SCOMDB.live.co-op.local:52809 ] for the SQL Server service. After re-registering the SPN my environment sprung back into life.  I just read some comments in a TechNet article

oglede oglede updated the answer: RE: Re: Check for presence of CU5 agent using a script?

oglede RE: Re: Check for presence of CU5 agent using a script?
Run this SQL Query against your Operations Manager DB to determine which agents are not patched to CU5 standards. select bme.path AS 'Agent Name', hs.patchlist AS 'Patch List' from MT_HealthService hs inner join BaseManagedEntity bme on hs.BaseManagedEntityId = bme.BaseManagedEntityId where hs.patchlist not like '%2495674%' order by path