We help IT Professionals succeed at work.

There are multiple accounts with name MSSQLSvc/server.mydomain.local:3846

HalCHub
HalCHub used Ask the Experts™
on
There are multiple accounts with name MSSQLSvc/server.mydomain.local:3846 of type DS_SERVICE_PRINCIPAL_NAME.


dn: CN=SERVER,OU=Domain Controllers,DC=MYDOMAIN,DC=local
changetype: add
servicePrincipalName: MSSQLSvc/server.MYDOMAIN.local
servicePrincipalName: MSSQLSvc/server.MYDOMAIN.local:3846
servicePrincipalName: {14E52635-0A95-4a5c-BDB1-E0D0C703B6C8}/SERVER
servicePrincipalName:
 {14E52635-0A95-4a5c-BDB1-E0D0C703B6C8}/server.MYDOMAIN.local
servicePrincipalName: exchangeMDB/server.MYDOMAIN.local
servicePrincipalName: exchangeMDB/SERVER
servicePrincipalName: exchangeRFR/server.MYDOMAIN.local
servicePrincipalName: exchangeRFR/SERVER
servicePrincipalName: SMTPSVC/SERVER
servicePrincipalName: SMTPSVC/server.MYDOMAIN.local
servicePrincipalName: exchangeAB/SERVER
servicePrincipalName: exchangeAB/server.MYDOMAIN.local
servicePrincipalName: DNS/server.MYDOMAIN.local
servicePrincipalName: GC/server.MYDOMAIN.local/MYDOMAIN.local
servicePrincipalName: HOST/server.MYDOMAIN.local/MYDOMAIN.local
servicePrincipalName: HOST/server.MYDOMAIN.local/MYDOMAIN
servicePrincipalName:
 ldap/410f4591-8e32-4878-a9c5-59050b706eb7._msdcs.MYDOMAIN.local
servicePrincipalName: ldap/server.MYDOMAIN.local/MYDOMAIN
servicePrincipalName: ldap/SERVER
servicePrincipalName: ldap/server.MYDOMAIN.local
servicePrincipalName: ldap/server.MYDOMAIN.local/MYDOMAIN.local
servicePrincipalName:
 E3514235-4B06-11D1-AB04-00C04FC2DCD2/410f4591-8e32-4878-a9c5-59050b706eb7/RAMA
 HDAROM.local
servicePrincipalName:
 NtFrs-88f5d2bd-b646-11d2-a6d3-00c04fc9b232/server.MYDOMAIN.local
servicePrincipalName: HOST/SERVER
servicePrincipalName: HOST/server.MYDOMAIN.local

dn: CN=SERVER2,OU=Domain Controllers,DC=MYDOMAIN,DC=local
changetype: add
servicePrincipalName: ldap/server2.MYDOMAIN.local/MYDOMAIN.local
servicePrincipalName: ldap/server2.MYDOMAIN.local
servicePrincipalName: ldap/SERVER2
servicePrincipalName: ldap/server2.MYDOMAIN.local/MYDOMAIN
servicePrincipalName:
 ldap/669a52ef-23ee-486d-af1a-16a81227740a._msdcs.MYDOMAIN.local
servicePrincipalName: GC/server2.MYDOMAIN.local/MYDOMAIN.local
servicePrincipalName:
 E3514235-4B06-11D1-AB04-00C04FC2DCD2/669a52ef-23ee-486d-af1a-16a81227740a/RAMA
 HDAROM.local
servicePrincipalName: DNS/server2.MYDOMAIN.local
servicePrincipalName: HOST/server2.MYDOMAIN.local/MYDOMAIN
servicePrincipalName: HOST/server2.MYDOMAIN.local/MYDOMAIN.local
servicePrincipalName:
 NtFrs-88f5d2bd-b646-11d2-a6d3-00c04fc9b232/server2.MYDOMAIN.local
servicePrincipalName: HOST/SERVER2
servicePrincipalName: HOST/server2.MYDOMAIN.local

What do I need to do to fix this problem ?

Thanks
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Senior Solutions Architect
Commented:
Does that server currently or did it ever host a SQL server instance?
Those are SPN records which are used to advertised application services on your network.

If it's not running any SQL Services then you can safely delete those records.
Leaving them shouldn't cause any issues either...so it's entirely your choice.

Role of SPN's
http://msdn.microsoft.com/en-us/library/ms191153.aspx

To check SPN:
"setspn -L server" should give you pretty much the same results as you're seeing above.

To delete a SPN
"setspn -D MSSQLSvc/server.MYDOMAIN.local:3846 server.MYDOMAIN.local"

To re-register a SPN
"setspn -A MSSQLSvc/server.MYDOMAIN.local:3846 server.MYDOMAIN.local"