Service Principal Names (SPN) are used to uniquely identify an instance of a service. SCOM Services are also registered and mostly everything will be just fine, but in some cases you might have issues with this.
My friend Walter Eikenboom has written up a very good post about SCOM and SPN, how to check it, how to set it etc. Check it out here: http://systemcenterdynamics.wordpress.com/2009/08/26/scom-2007-r2-what-should-my-spn-registrations-look-like/
Also a post by Kevin Holman about the subject:
System Center Operations Manager SDK service failed to register an SPN
http://blogs.technet.com/b/kevinholman/archive/2007/12/13/system-center-operations-manager-sdk-service-failed-to-register-an-spn.aspxSymptoms if you see an event from OpsMgr SDK Service with ID 26371
And another writeup by Jonathan Almquist:
http://blogs.technet.com/b/jonathanalmquist/archive/2008/03/12/sdk-spn-not-registered.aspx
Another case that can be brought back to an SPN issue by JC Hornbeck:
OpsMgr 2007: Agents stuck in Pending Management with Event ID 21016
http://blogs.technet.com/b/smsandmom/archive/2008/03/13/opsmgr-2007-agents-stuck-in-pending-management-with-event-id-21016.aspx
Back to the SCOM Tricks general list
