All our users files are located on a centralized (Server 2016) file server. The directories individual users use are set to 'make available offline' - either via GPO for directories like their home drives, or by the users explicitly right clicking and selecting "make available offline" of various project directories. This works well for times when they need to leave the office and/or the network goes down; it also helps keep versioning issues to a minimum.
I now have a user doing a current project with very high I/O needs... high enough that, to be viable, they need to access files on their local drive rather than over the network. They still need to be 'network' files, however, as a few other people need access to the files too -- so simply "making a local copy" isn't a good option.
When they pull the network cord from their computer, things go speedy and nice... because their program is accessing the files stored on the hard drive.
When they are connected to the network, things go very slow... ostensibly because it's pulling the files over the network rather than the ones on the local drive. What appears to be the case is that the network files are used by by default and then just sync'd to the local drive.
How can flip this relationship? How can I make set the system to use the local files by default (and sync to the network as they change)?
In fact, I'd love to do this enterprise-wide if possible...
(Windows 10 system, server 2016 file server)
