Issue with renaming large files before upload is complete

Chad_V_Kealey 

You have several options going forward.

a. OneDrive for Business (ODFB)
This requires software on the client and also leaves the original file on the clients. This is likely going to cause conflict with the governance folks. You will also need to train users how to use ODFB properly and not end up with dozens of incident tickets.

b. Use "Open with Explorer"
It has deployment drawbacks like it requires IE and also ActiveX but it also has technical drawbacks (the maximum file size is controlled by a registry setting on the client and this is typically 50 - 100 MB.
I am not a fan of "Open with Explorer" even if the maximum file size is increased since I have encountered several problems (e.g. 0 kB files, files not uploaded and no errors, inefficient protocol, ...).

c. Use browser-based apps that address key issues like
- robust uploading (e.g automatic checks that ensure the file is uploaded completely, retransmission if an upload request fails, ...)
- support for very large files (some tools can now even support 100 GB files by uploading a large file in chunks)
- avoid configuration / software installs on the client
- prevent renaming until the file has been completely uploaded

For example, in Teams you can add a new tab that uses the standard web site app to open a tool (e.g. https://www.slimapplications.com/wp-content/uploads/2020/05/ExplorerOverviewUpload.png ). Users can upload one or more files using drag and drop, select content type (if multiple exist) and set metadata. Some tools can also extract metadata from the media files (e.g. duration, location, date time taken, ...) and capture the values into SharePoint columns. During the upload they cannot rename the file.
NB: it still requires an effort from the user to delete the original file.

To summarize, you can use technology to address the key issues but it also requires a minimum level of commitment from the users.

Paul