In Windows 8 or Windows Server 2012, there is a new PowerShell cmdlet that can easily tell you what version of SMB the client has negotiated with the File Server. Using PowerShell to check the SMB version Here’s a table to help you understand what version you will end up using, depending on what Windows version is running as the SMB client and what version of Windows is running as the SMB server: Client / Server OSĤ. You can use the support pages to also find support policy information for Windows XP, Windows Vista and Windows 7. The information is subject to the Microsoft Policy Disclaimer and Change Notice. You can find the most current information on the support lifecycle page for Windows Server. SMB 2.x in Windows Server 2008 and Windows Server 2008 R2 will be around at least until 2018, when Extended Support for those products is scheduled to expire. Windows Server 2003 R2 with a current service pack is under Extended Support until 2015, so SMB1 is still around for a little while. Windows NT is no longer supported, so CIFS is definitely out. SMB 3.0 (or SMB3) – The version used in Windows 8 and Windows Server 2012.SMB 2.1 (or SMB2.1) – The version used in Windows 7 and Windows Server 2008 R2.SMB 2.0 (or SMB2) – The version used in Windows Vista (SP1 or later) and Windows Server 2008.SMB 1.0 (or SMB1) – The version used in Windows 2000, Windows XP, Windows Server 2003 and Windows Server 2003 R2.CIFS – The ancient version of SMB that was part of Microsoft Windows NT 4.0 in 1996.There are several different versions of SMB used by Windows operating systems: Upgrading to a new version of SMB is something that happened a few times over the years and we established a process in the protocol itself by which clients and servers negotiate the highest version that both support. With the upcoming release of SMB 3.0 as part of Windows 8 and Windows Server 2012, I am frequently asked about how older versions of Windows will behave when connecting to or from these new versions.

Smb client for windows 7