"Get-SmbServerConfiguration"-Checks fail in some scenarios

[TuemmlerKelch]

In contrast to below error message, the error is not related to filename-length.
Affected systems seem to be able to process these commands as soon as the "lanmanserver"-service is activated. However, this seems to be only part of the issue, as a lot of systems can still process these commands with lanmanserver being disabled.

[TuemmlerKelch]

suggestions:

old	new
Microsoft	MS (for OS part, not Baseline publisher)
Restricted Traffic Limited Functionality	RTLF
Domain Controller	DC

[qngngyn]

Current status is found in branch #443. The changed filenames do not fix the issue of Get-SmbServerConfiguration: Filename too long.

Suggestion: Run Get-SMbServerConfiguration -ErrorAction Stop to enable catching of errors, and proceeding the test with registry keys.

[TuemmlerKelch]

Please add a note when fallback is used and set status to warning:
*Get-SMBServerConfiguration failed, resorted to checking registry, which might not be 100% accurate. See here and here