Force SMB3 when possible?

Question

Background

I have an environment with 5000 or so workstations, 1000 or so servers.

All of my file share servers are running Windows Server 2012 or higher, and thus support SMBv3.

About half of my workstations are Windows 10, and thus support SMBv3; however the other half are Windows 7, and thus only support SMBv2 or lower.

I'm working on replacing these Windows 7 machines, but it'll be awhile. We've paid for extended support, so it's ok for another year.

My Issue

Is it possible to force SMBv3 connections when SMBv3 connectivity is possible, but support SMBv2 otherwise?

Example:

Windows 10 workstation visits the "Accounting" department share to get a file. The connection between the workstation and department share (our file server) is via SMBv3

Windows 7 workstation visits the "Accounting" department share to get a file. The connection between the workstation and department share (our file server) is via SMBv2

EDIT

I ran Get-SmbConnection on my Win10 workstation to my file server, and it reports version 3.02.

However, running Wireshark while transferring a file between workstation and share shows SMBv2, and Wireshark is able to re-create the transferred file from the captured packets. SMBv3 is encrypted, so this shouldn't be possible if it were.

This is where my confusion is stemming from I suppose.

Answer 1

This is how SMB functions to spec already. It will connect at the highest version that both parties support. Server 2012 to Windows 10 = smb3, 7 to server 2012, smb2, etc. This can be verified with Get-SmbConnection cmdlet in powershell on any host with an smb connection to another host.