Changing Server Name gives Ooops

If you change the server name in Windows networking you get an Ooops. If you then reselect Windows Networking from the menu, the change seems to have worked.

Debug log attached:
debug.log

Digging into it, it probably come from when we started deprecating "server max protocol", and the code around that is not quite working correctly.

From memory, the logic should be:

• If "server max protocol" is set to NT1 leave it - This was the Windows 10 Domain Logons field, now renamed to something like "Force SMB1 Protocol"
• If it gets set to disabled in the webconfig, remove the option from the webconfig and, obviously, smb.conf