02-15-2017 10:12 AM
02-15-2017 10:39 AM
02-15-2017 11:12 AM
Agree with Andy, you should avoid using Mapped drives unless you have a really really specific need for them. But just for completeness, here's the KB article on how to configure and troubleshoot them: http://support.microsoft.com/kb/2616712
You will run into issues if you use them, that's pretty much guaranteed. But if you insist, there are also some tools that can help you keep the sessions active, autoconfigure them for your users and so on. Do a search on the internet and you will find examples of such tools, both free and paid.
02-15-2017 12:15 PM
As Vasil said, the plain-vanilla mapping described in the support article will give you all sort of problems...
If you insist on using mapped drive, you should rather investigate products like ZeeDrive (http://www.thinkscape.com/Map-Network-Drives-To-Office-365-OneDrive/) which is known for working well.
02-15-2017 12:17 PM
Syncing is the way to go but if you are going to map drives, check out OneDriveMapper, though it might be overkill, it's a free script for mapping drives to OneDrive for Business (or SharePoint sites). I haven't used it myself but I have heard good things about it -
02-16-2017 07:44 AM
02-17-2017 06:09 AM
Thank you guys for your informations! At the moment I tested the simple connectivity between Windows 7 and One Drive for Business for know how is functionality.
Sorry, my bad english. I'm study this language.
09-06-2018 04:25 AM
It is easy to see why a mapped network drive is still necessary. Limited space on my local drive for syncing, therefore, a need to map to sharepoint O365 sites is needed. Is this still possible?