MicrosoftJamesKehr While it's good to see Microsoft trying to get rid of SMBv1, i think a lot more could be done...
SMBv1 was deprecated back in 2007 with the release of Vista which first introduced SMBv2, and yet 15 years later we still see devices not only supporting but in some cases actually requiring SMBv1. And i suspect a big part of this comes down to the way in which backwards compatibility is implemented...
If a user on Vista tries to access an SMB share, it will try SMBv2 first and if that fails it will fall back to SMBv1, but the problem is there is no feedback to the user indicating that they have been degraded to an older inferior protocol. The users have no way to know what version they are using, so they are not going to demand support for newer better protocols from vendors, neither are they going to favor products which already support the newer protocols.
What should really happen is displaying a warning to users whenever they are failed over to a weaker protocol, possibly including a link to a site explaining in simple terms that the older protocol has been replaced with a superior replacement, which they should be using whenever possible.
SMBv2 isn't even current, SMBv3 has been out for several years and offers plenty of benefits over SMBv2. Then there are other superior protocols like TLSv1.3, IPv6, HTTP/2, WPA3 and SNMPv3 among others yet the legacy versions are still widely used because there is little widespread demand for the newer versions.
So my ask to Microsoft and other vendors. As well as supporting current protocols, display warnings to users if they are accessing a service which forces a downgrade to any legacy protocol. Create awareness, and thus demand for progress.
