pssdiag for non-default sql port about diagmanager

[PiJoCoder]

SQL Browser service should help you connect to the right instance even if non-default port is used.
SQLDiag.exe cannot read a connection string of the type "tcp:123.234.56.78,1455" and thus you cannot specify this as machine name in PSSDIAG. You would get an error similar to the following indicating that the machine is not local but somewhere "on the network" but is invalid:

2022/04/20 16:50:57.68 SQLDIAG Error opening HKLM key . Function result: 53. Message: The network path was not found.
2022/04/20 16:50:57.68 SQLDIAG Error opening HKLM key . Function result: 53. Message: The network path was not found.
2022/04/20 16:50:57.69 SQLDIAG Error opening HKLM key . Function result: 53. Message: The network path was not found.
2022/04/20 16:50:57.69 SQLDIAG There are no instances of version 15 on this computer
2022/04/20 16:50:57.69 SQLDIAG . Function result: 87. Message: The parameter is incorrect.

However, SQLDiag.exe does accept a separate parameter /T where you can specify /T tcp,port . Therefore as a workaround you can invoke SQLDiag.exe yourself using this switch and the rest of the switches.

[PiJoCoder]

We can consider adding the /T switch to pssdiag.ps1 PowerShell file to accommodate this ask