We have a scom 2012 server (ServerA). System Center Data Access Service run with domain user UserA. I recive this error: Data Access Service SPN Not Registered. The alert shows that i have to add two SPNs to ServerA. I don't understant why i don't have to add these SPNs to UserA

Hi, Check Kevin's blog: http://blogs.technet.com/b/kevinholman/archive/2011/08/08/opsmgr-2012-what-should-the-spn-s-look-like.aspx 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.

This is the problem... why Does alert show me that i have to add SPN to SCOM account (not user account)??

Operational Database is on Remote SQL Clúster...

Hi, What is a SCOM account and a user account in your environment? "This is caused by the fact that when the SDK service (System Center Data Access Service) starts up, it tried to ensure/update the SPN on the account that the SDK service is running under. By default in a domain, a standard user account does not have the right to update its own SPN."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.

SCOM Server: ServerA SDK Account: scomsdk (System Center Data Access Service run with this user). This user is a domain user that has admistrator permission on ServerA

Hi, You have to follow Kevin's guide to update the SPN on the SCOMSDK account you are using. Did you try that?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.

in that link said: Alert Description: The System Center Operations Manager SDK service failed to register an SPN. A domain admin needs to add MSOMSdkSvc/OMMS1 and MSOMSdkSvc/OMMS1.opsmgr.net to the servicePrincipalName of OPSMGR\omdas In my case is: Alert Description: The System Center Operations Manager SDK service failed to register an SPN. A domain admin needs to add MSOMSdkSvc/OMMS1 and MSOMSdkSvc/OMMS1.opsmgr.net to the servicePrincipalName of OPSMGR\OMMS1 That is the difference... If I add SPNs to OPSMGR\OMMS1 alert doesn't appear, but I don't understand it...

Hi, Did you add SPN to INTER\scomsdk ?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.

yes, but that doesn't solve the problem If I add INTER\VA-SCOM1$, it solves the problem !!!! (I don't understand it)

With refer to my experience, you should follow Kevin's blog: http://blogs.technet.com/b/kevinholman/archive/2011/08/08/opsmgr-2012-what-should-the-spn-s-look-like.aspx if you using domain account as scom SDK service account. This is same as SCOM 2007 R2. Best Regard Roger

Hello, I also have this problem in SCOM 2012 with the same SCOM 2007 R2 spn configuration, and i confirm that adding SPNs to domain\servername$ the alerts disappear!

Ok..... but.. is this a bug?

We have the issue too. 3 Management Servers, one Domain User as the SDK service account (local admin on each Management Server too), even set the permissions on the service account so that it can Read & Write SPNs...but the errors indicate that the Management Server machine accounts needs to be SPN registered and not the service account?

We have the issue too. 3 Management Servers, one Domain User as the SDK service account (local admin on each Management Server too), even set the permissions on the service account so that it can Read & Write SPNs...but the errors indicate that the Management Server machine accounts needs to be SPN registered and not the service account? SCOM 2012 RTM. The same problem. I think this is a bug.

Same problem here too. Can anyone confirm that this is a bug?