dataplat/docs

FQDN needed on instances with SSL/TLS

Closed this issue · 1 comments

Skodaddy commented

Module (1.1.143) manually copied to C:\Program Files\WindowsPowerShell\Modules\dbatools
powershell: Version : 5.1.14393.5582

When we run commands to SQL server instances that are encrypted with SSL (connection encryption); these always fail if we don't use the FQDN.
Commands from the SQLSERVER module run without FQDN.

Example:
SQLSERVER: Sqldatabase -ServerInstance 'SERVER\INSTANCE' --> works
SQLSERVER: Sqldatabase -ServerInstance 'SERVER.domain.com\INSTANCE' --> works
DBATOOLS: Get-dbadatabase -SqlInstance 'SERVER\INSTANCE' --> WARNING: [09:51:44][Get-DbaDatabase] Failure | The target principal name is incorrect
DBATOOLS: Get-dbadatabase -SqlInstance 'SERVER.domain.com\INSTANCE' --> Works

This gives a lot of issues when you pipe to next step:
example: Get-DbaAvailabilityGroup -SqlInstance 'SERVER.domain.com\INSTANCE' | Sync-DbaAvailabilityGroup -Whatif
will give an error for each AG:
What if: Performing the operation "Set variable" on target "Name: __dbatools_interrupt_function_78Q9VPrM6999g6zo24Qn83m0
9XF56InEn4hFrA8Fwhu5xJrs6r Value: True".
WARNING: [09:59:01][Sync-DbaAvailabilityGroup] Failure | The target principal name is incorrect
What if: Performing the operation "Set variable" on target "Name: __dbatools_interrupt_function_78Q9VPrM6999g6zo24Qn83m0
9XF56InEn4hFrA8Fwhu5xJrs6r Value: True".
WARNING: [09:59:01][Sync-DbaAvailabilityGroup] Failure | The target principal name is incorrect

Skodaddy commented

Sorry, wrongfully logged , mes excuses

  • 👍1