Skip to main content

Map SharePoint with local file drive - A complete guide

If you google around you can find quite a few posts talking about this 'simple' solution, but I find none of them gets into deepth, especially on prerequisites. So I write this post and hope it can provide meaningful information for users who need map SharePoint with local file drives. And I will give a short overview and the advantages and comments about this implementation.

 

Prerequisites

You need to make sure the the "WebClient" service is up and runing on your server. If this service is disabled or missing on your server, you will have an error saying "The folder you entered does not appear to be valie. Please choose another"
 
To check if "WebClient" service is in your services list, just open services and see. If it is missing, please follow the steps to make it available:
     
  1. Start the Windows Server Manager.
  2. In the tree view, highlight the Features node.
  3. In the details pane, click Add Features.
  4. In the Add Features Wizard, check the Desktop Experience box, and then click Next.
  5. Click Install.
  6. When the Add Features Wizard has finished, click Close.
  7. Click Yes when promoted to restart the computer.


After that you should be able to see the "WebClient" service is avaliable in your services:
And then you need to start it.

Map SharePoint with file drive

 
  1. Open "Windows Explorer" from your server
  2. Right click on "Computer" icon, select "Map network drive.."
  3. Click "connect to a web site that you can use to store your documents and pictures"
  4. In "specify the location of your website", input the library url where you want to store files (e.g. http://devsp2010tl/sites/dw/Shared%20Documents). Note in lower versions of SharePoint the url can't contain %20 charactors, so simply change the url as http://devsp2010tl/sites/dw/Shared Documents in this case.
  5. Give it a name
  6. Follow the instructure and finish!
After that you will be able to see the folder under your computers:
 

The benifits for using this mapping:

Lots of benifits, such as:
  • You can drag and drop files/folders into the mapped drive and it will be synced to SharePoint library (especially when you are using lower SharePoint versions before SharePoint2013)
  • Manange (adding/updating/changing/deleting) files from either SharePoint or file drive
  • Leverage version control of SharePoint
  • Leverage SharePoint search.
  • Security controls
  • you name it...
For business, one of the real world solution could be:

A business used to use a shared network drive to store company documents such as policies, forms, guides. Using this mapping, business can make the documents and files managable quickly. Meanwhile for file migration, it could also be a good solution.

Enjoy!
 

Labels:

Comments

Post a Comment

Popular posts from this blog

A Step-by-Step guide to use HttpModule in SharePoint with SPContext

I guess you must be familiar with what is HttpModule and how can we leverage it for our web applications. But if not, better have a good read of this article . SharePoint is built on top of .NET, so it has all the rights to use the beauties of .NET. Here I want to demo a simple case of httpmodule on SharePoint. Say if in a company it has lots of site collections and user 'Picky Docky' has access for all of them, for a reason farm administrator want to block him for one of the specific site without change his SharePoint permissions. Here are the steps to do it:-)   Create a empty SharePoint solution add a class file to it named  CustomSecurityModule.cs , code as below Create a feature and scope to "WebApplication" Create a feature receiver. Code as below When activate the feature it will create a modle in the web.config file for the SharePoint web applicaiton you deployed to as below: Enjoy!
2 comments
Read more

SharePoint 2013 online Parent/Child relationship - A step by step demo

SharePoint uses lookup fields to represent the Parent-Child relationship. For child list items it is OK as you can trace back to its parent from the lookup field. For parent the OOB forms are not good enough as they are not displaying the children belong to it. In real world it is often required that when view the parent list item it also displays its children, further more it is great if user can add child list items directly from the parent. In SharePoint on-premise we can use visual web parts and code the parent/child logic and use web part pages to replace the parent item forms. In SharePoint online we can't do server model code and visual web parts, so the solution is almost NO CODE and just a little bit client side scripts, and they work beautifully! Here I will do a step by step demonstration to explain the ideas:   Step 1: Create a parent list called "Category" and a child list called "Product", in Product list add a lookup field to reference Cat...
7 comments
Read more

SharePoint search on local file drive - Why and How

A team member asked me why in some situation we need to use SharePoint search on local file drive as we can do 'search' directly on the folder in windows. I think it is necessary to do some research to show why and why the benifit is to do this. And more importantly - HOW.   WHY? If you've played around with SharePoint local file search the answer is straight-forward: You can let it search multiple local file drives, but using windows you can hardly do this. SharePoint can search 'into' the real content even the keyword is in content of files in zip file . See the comparison I did a search for keyword 'issue':   Window built-in search: SharePoint search: SharePoint search can easily filter the result by type/date etc. SharePoint can show a bit of content from the files found to give a bit more indication. ... HOW  It's hard to find a step-by-step guide talking about how to make it work. That's why here I am:-)   Go to the f...
Post a Comment
Read more