Resolve-NetBiosName - Return ComputerNamePhysicalNetBIOS if clustered

[andreasjordan]

Type of Change

• Bug fix (non-breaking change, fixes [Bug] export-dbalinkedserver not working in a sql clustered instance #6053 )
• New feature (non-breaking change, adds functionality, fixes # )
• Breaking change (will change functionality of all commands using Resolve-NetBiosName against clustered instances)
• Ran manual Pester test and has passed (.\tests\manual.pester.ps1)
• Adding code coverage to existing functionality
• Pester test is included
• If new file reference added for test, has is been added to github.com/sqlcollaborative/appveyor-lab ?
• Unit test is included
• Documentation
• Build system

Purpose

Resolve-NetBiosName now does what the name says: It resolves the (physical) NetBiosName of the computer, so in clustered instances the ComputerName of the cluster node the instance currently runs on.

So no change for all non-clustered instances. Only risk: This would fail if the computer would only accept connections to the cluster name and not the node name. But I think the more offen case is like in the linked issue, that the computer only accepts connection to the node name.

[andreasjordan]

This pull request can be closed if we work on #5988 and remove Resolve-NetBiosName and replace it by Resolve-DbaNetworkName in all commands, as the later returns information about the physical node instead of the virtual cluster name.

[potatoqualitee]

I dig it, thank you!