Unity Editor takes 8 mins to save new project to mapped drive

We are a secondary school teaching Unity to classes of 30 or so students.

For some reason when we create a new Unity project on a mapped drive it takes around 8mins to start the Editor, however, if we save locally it's almost instant.

I appreciate it will be a bit slower on the network, but we have much larger projects from Adobe Premiere and thousands of other files saved to these mapped drives on a daily basis with no major issues. Unity however seems to be considerably slower to the point that the editor actually locks up and eventually crashes after about 30mins if too many students try to start a project at the same time.

As I say we transfer much larger files and larger numbers of files in other scenarios with no issues.

Has anyone else experienced anything like this or has a suggested fix? We are currently investigating the SAN that the mapped drive sits on and the Hyper-V environment that hosts the file server as well as anti-virus overheads, but nothing seems to be making much of an improvement.