First published on TECHNET on Jun 01, 2017
Hi folks, Ned here again. This blog post contains all products requiring SMB1, where the vendor explicitly states this in their own documentation or communications, or where a customer has reported it and shown some degree of proof without vendor refutation. This list is not complete and you should never treat it as complete; check back often. All products arranged in alphabetical order, by vendor, by product, with a URL to their documentation stating SMB1 requirements. Vendor – Product - Documentation
To update this list, please email StillNeedsSMB1@microsoft.com or tweet @nerdpyle with hashtag #StillNeedsSMB1 . Adding a product to this list ideally requires direct quote or documentation from the vendor of that product, including their website, knowledgebase, support forums, or other vendor channels; third party forums are not enough to qualify. Alternatively, if your vendor has responded to you in a support case that SMB1 is required but does not provide public documentation, products will be added case-by-case. Consult your vendor for updates and newer product versions that support at least SMB 2.02. If you are a vendor and wish to report requirements for SMB1 or if information above has changed, email StillNeedsSMB1@microsoft.com . There are vendors who are not publishing their SMB1 requirements. It is up to you, their customer, to have them publish this information - Microsoft cannot make them do so. If a vendor does not state if they require SMB1 but you believe they do, please contact that vendor directly. If you need assistance getting a vendor response, email StillNeedsSMB1@microsoft.com and we will try our best to assist. Politeness works best; the person you are speaking to at a vendor is extremely unlikely to have put SMB1 into the product & probably isn't any happier about it than you are! For more information on why using SMB1 is unsafe, see StopUsingSMB1 . SMB1 has been deprecated for years and will be removed by default from many editions and SKUs of Windows 10 and Windows Server 2016 in the RS3 release.
Important: if your vendor requires disabling SMB2 in order to force SMB1, they will also often require disabling oplocks. Disabling Oplocks is not recommended by Microsoft, but required by some older software, often due to using legacy database technology. Windows 10 RS3 and Windows Server 2016 RS3 allow a special oplock override workaround now for these scenarios - see https://twitter.com/NerdPyle/status/876880390866190336 . This is only a workaround - just like SMB1 oplock disable is only a workaround - and your vendor should update to not require it.
Be safe out there,
- Ned Pyle, Principal Program Manager of the SMB protocol family at Microsoft
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.