Post reply

SetSPN

  • March 21, 2013 at 11:35 pm

    #272475

    Where we would run SETSPN command for SQL Server ? -On DB Server on the domain controller ?

  • March 22, 2013 at 12:29 pm

    #1599950

    Either one, as long as both as connected to the domain. The changes it invokes are made to Active Directory not to the computer where it is run so it's more important who runs it (must have privileges to manage SPNs in AD) not where it is run.

    There are no special teachers of virtue, because virtue is taught by the whole community.
    --Plato

  • March 23, 2013 at 1:13 am

    #1600037

    Thanks

    When I put SETSPN - L FQDN

    I am not able to see spn for sql server (MSSQLSVC/fqdn:portno)

    But when I put SETSPN -L <sqlservice account> I could see Spn for sql server

    is this because of spn not proper registered ?

  • March 23, 2013 at 7:25 am

    #1600058

    Akkare (3/23/2013)

    Thanks

    When I put SETSPN - L FQDN

    I am not able to see spn for sql server (MSSQLSVC/fqdn:portno)

    But when I put SETSPN -L <sqlservice account> I could see Spn for sql server

    is this because of spn not proper registered ?

    It depends. Which account is your SQL Server service setup to log on as?

    There are no special teachers of virtue, because virtue is taught by the whole community.
    --Plato

  • March 25, 2013 at 10:56 pm

    #1600605

    Its Domain Account

  • March 26, 2013 at 8:01 am

    #1600806

    When running the service as a named domain account the SPN must be registered to the domain account which is why you do not see it when you ask to see the FQDN.

    There are no special teachers of virtue, because virtue is taught by the whole community.
    --Plato

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply