Closed steffenengelhamburg closed 7 months ago
Is this the same as discussed in issue #513?
Hi Johlju, of course, it‘s the same issue / Change Request. I searched around the issue list with the error above but didn‘t found this issue.
I think this one can be closed if the change will be commited. I don‘t need more than 16 chars as listenername like in #513 but support a no length limit.
Thank you! Greetings from Hamburg Steffen
The NETBOIS-compatible host names has a limit of 15 chars, that is why the resource has that limit.
The limit is simply from the NETBIOS protocol, which has a limit of 16 bytes for the computername. The last byte in Windows networking is used for a service ID, hence the 15 byte (characters) limit on NETBIOS-compatible hostnames. https://techcommunity.microsoft.com/t5/windows-server-for-it-pro/hostname-character-limit/m-p/1068231
But the issue #513 suggest to remove the length entirely so then it is up to the user to make the correct choice depending on use-case.
So happy to see a PR that removes the limit and also updates the documentation that the user must be aware the choice it must make.
Closing this in favor of #513.
Problem description
Problem: Using a AG Listenername with maximum 16 Chars (Netbios Maximum) the Mof will be build, but not applied on the Target.
Verbose logs
DSC configuration
Suggested solution
Change ValidateLenght for $Name of AVG Listener in DSC_SqlAGListener.psm1
[Parameter(Mandatory = $true)] -[ValidateLength(1, 15)] +[ValidateLength(1, 15)] [System.String] $Name,
SQL Server edition and version
SQL Server PowerShell modules
Operating system
PowerShell version
SqlServerDsc version