Yeah, I'd guess so. They'll be disabling smb v1 because its got a fairly big security hole, linked to a lot of the more recent ransomware attacks.
Essentially, you've got the Win2k box on the Quanta that can only communicate via smb.v1, a support PC that needs smb.v1 to communicate with the Win2k Quanta PC and a requirement that all university network connected PCs have smb.v1 disabled and a minimum of smb.v2. Bit of a tricky one!
The only way I could think of doing it would require a second support PC (assuming that you can't enable smb.v1 on a per interface basis, which samba in Linux may be able to do), something along the following lines:
Quanta (Win2k) -smb.v1-> 1st Support PC (Win7,10w/smb.v1/Linux) -smb.v2-> 2nd Support PC (Win10 w/smb.v1 disabled) -smb.v2-> University Network
Both support PCs would need at least two NICs. The first support PC would be able to communicate via both smb.v1 and smb.v2, the 2nd support PC via smb.v2 and above. You could have the data cascading through the support PCs (possibly deleted from the 1st support PC to remove the storage requirement, depending on how you have the data policy configured). You could also make all the shares read only, adding an extra bit of protection.
To get round the requirement for regular antivirus updates, I'd disable all USB ports (via group policy) and ban USB pen drive access to any of the instrument or support PCs, making everyone pull the data from the network share (whether 2nd support PC or a data store on the university network), and preferably have the 1st support PC as a Linux machine also acting as a hardware firewall. I'd image a working version of the Quanta PC win2k installation, and keep that in a safe place and ensure that all the data that changes is sent off the instrument PC (removing the Norton Ghost requirement).
If going with windows for the support PCs, I'd recommend getting a backup/copy program that supports the volume shadow copy service, or write a script that creates the copy, robocopy to the network share then deletes the shadow copy - this should avoid any issues with locking a file currently having data written to it.