YeOldeStonecat
Well-Known Member
- Reaction score
- 6,556
- Location
- Englewood Florida
If you really want to mimic a traditional setup you can mount the local OneDrive folder as a drive.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\DOS Devices
Create a new string named Z:
Value: \??\C:\Users\Username\OneDriveFolder
After a reboot they will have a local drive Z: which is pointing to C:\Users\Username\OneDriveFolder
Added bonus any shortcuts they already had to Z:\ will continue working.
It's not something I recommend doing unless forced however it works surprisingly well.
EDIT:
Just adding a caveat to this which I forgot to mention. Explorer shell integration does not work when in the Z:\ drive. Windows treats it as any other folder so you don't get the right-click options for sharing, version history, selective sync etc.
I have done that, although using the old DOS command "SUBST"....in a batch file.
However, I only did it for a legacy report downloading script for a client, for online blackbaud, they needed to pull down reports in a .txt file format to upload into another reporting app. Zero use by others.
I strongly recommend not using a mapped drive letter, the indexing/searching will not function properly.
I look at the "OneDrive" syncing of each Team/Channel file library...as a way to "wean" users away from the old school file explorer method they've used for ~30 years. EVENTUALLY...users start fiddling with working with files withIN the Teams app itself....and start learning that it works..and works well, concurrent editing of files works better, etc. Another year or two down the road....you'll find they're really using the Teams app most of the time.