Hi It is on the service account
"The SCSM 2012 use the SPN with he service class "MSOMSdkSvc". SPN must be registered to service account (or run as account for System Center Data Access Service)." If your service account is domain account: setspn -A MSOMSdkSvc/SCSMSERVER YOURDOMAIN\ServiceAccount setspn -A MSOMSdkSvc/SCSMSERVER.fqdn.name YOURDOMAIN\ServiceAccount You must repeat this commands for each of your management servers (DW too). Also you must restart SDK Service to take effect. Taken from http://blog.scsmsolutions.com/2012/11/configure-the-kerberos-for-scsm-2012-spn-and-delegation/ Hope this will help you /Kristoffer Stormark From: [email protected] [mailto:[email protected]] On Behalf Of Séguin, Mario Sent: 21. januar 2014 14:48 To: [email protected] Subject: [servman] RE: Weird problem Hello Kristoffer, Thank for the info. Where did you setup the SPN config. On the SCSM Server? thanks From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Kristoffer Stormark Sent: January 15, 2014 3:23 AM To: [email protected]<mailto:[email protected]> Subject: [servman] RE: Weird problem Hi, For our scsm setup, this was also an issue at the beginning. Im not 100% sure if this is the solution. But after we made the right SPN configuration, the problem went away In our setup we have tree management servers and it looks like the sync some how don't work before you restart the service. /Kristoffer From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Travis Wright Sent: 9. januar 2014 18:46 To: [email protected]<mailto:[email protected]> Subject: [servman] RE: Weird problem That's not unusual. : ) From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Séguin, Mario Sent: Thursday, January 9, 2014 6:27 AM To: [email protected]<mailto:[email protected]> Subject: [servman] Weird problem Hi all, Whenever I add a task or management pack and I close SCSM and restart, the changes are gone until I go to the SCSM server and manually restart the Data Access Service. Anyone else have this issue.
