Test-DbaSpn returns wrong result from Azure IAAS SQL Server #695

Open
PowerDBAKlaas opened this Issue Feb 9, 2017 · 2 comments

Projects

None yet

3 participants

@PowerDBAKlaas
Member

Is this a feature OR bug:

bug

System Details

  • Operating system name and version:
    Windows 10 Enterprise 10.0.14393

  • Output from $PSVersionTable:
    PSVersion 5.1.14393.693
    PSEdition Desktop
    PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
    BuildVersion 10.0.14393.693
    CLRVersion 4.0.30319.42000
    WSManStackVersion 3.0
    PSRemotingProtocolVersion 2.3
    SerializationVersion 1.1.0.1

  • Output of dbatools version:
    0.8.707

  • SQL Server version for source/target
    all SQL2016

Steps to Reproduce

Test-DbaSpn -ComputerName SQLOnAzure

Action Results

[InstanceServiceAccount] returns "NT Service\MSSQLSERVER"
which is wrong, the service definitely runs under a domain account

[RequiredSPN] is empty
which results in an error from Set-DbaSpn when piped through

This happens on all 3 SQL Servers in Azure IAAS,
and on none of 16 SQL Servers on premise, 2 physical + 14 on VMWare

Expected Results

[InstanceServiceAccount] should return the correct Account
[RequiredSpn] should return an SPN

@SirCaptainMitch SirCaptainMitch added the bug label Feb 9, 2017
@PowerDBAKlaas
Member

@drewfurgiuele any news on this?

@drewfurgiuele
Contributor

Sorry @PowerDBAKlaas I was out sick yesterday; I will be working on this in the coming weekend.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment