System Center Operations Manager SDK service failed to register an SPN

SCOM SP1 - SDK SPN Not Registered Alert

Ying Li at myITforum.com — Mon, 10 Mar 2008 05:57:18 GMT

After I upgrade to SCOM SP1, everytime I restart SDK service, I got the below alert: Alert: SDK SPN Not

re: System Center Operations Manager SDK service failed to register an SPN

Kerry Gerhard — Tue, 22 Jul 2008 21:56:25 GMT

I'm not domain admin: what to do?

The suggested fix in the alert is not working for me. Is this because I'm not domain admin?

(from alert)

• Setspn.exe –A MSOMSDK/<RMS FQDN> domain\username (this is the SDK service account name)

• Setspn.exe –A MSOMSDK/<RMS NETBIOS> domain\username

Note: If the RMS is clustered, you should use the virtual server name

re: System Center Operations Manager SDK service failed to register an SPN

kevinhol — Tue, 22 Jul 2008 22:07:11 GMT

Setting the SPN manually will not solve the event 26371. The SDK account will still try and UPDATE the SPN on each start. If you want to see the error go away - you must allow the SDK account the rights to update its own SPN.

Operations Manager 2007 SPN's

Jonathan Almquist on Operations Manager — Thu, 14 Aug 2008 09:16:41 GMT

There's a lot of confusion about SPN's (service principal name) when it comes to OpsMgr.  How are

re: System Center Operations Manager SDK service failed to register an SPN

Hayden Trail — Thu, 23 Oct 2008 01:25:21 GMT

I just had this issue with a customer and found that even though the account had access to update its own spn it was still producing the warning event. The problem in this environment was that the service account did not have access to read the OU that it was in, once this was granted the warning was gone. Hopefully this might help people.

re: System Center Operations Manager SDK service failed to register an SPN

Tom Brady — Thu, 06 Nov 2008 17:05:45 GMT

We receive the following AD Error on our DC: There are multiple accounts with name MSOMSdkSvc/RMS of type DS_SERVICE_PRINCIPAL_NAME.

I have found the SPNs in our environment are for the RMS machine account:

MSOMSdkSvc/rms.domain.com

MSOMSdkSvc/rms

MSOMHSvc/rms.domain.com

MSOMHSvc/rms

HOST/rms.domain.com

HOST/rms

And for the SDKService account:

MSOMSdkSvc/rms.domain.com

MSOMSdkSvc/rms

So we have the same SPN set for the Service account and the machine account and it is throwing up an error indicating this.

My question is it the best practice to set a Local System account for the health/sdk service on the RMS or a domain account. If it is the BP for a domain account than I assume we should just ignore the AD error about duplicate SPNs? I have seen many different views on whether account should be running the SDK/Health services and need a little clarification.

Thank you for the great site!

re: System Center Operations Manager SDK service failed to register an SPN

Trikke — Mon, 12 Oct 2009 11:21:02 GMT

Can anyone provide an example on how the SPN's should be registered for a clustered RMS?

Do i need to register the nodes or the cluster or the application layer?