4

I have a couple of drives mapped to a SharePoint site. When I open Windows 10 Explorer and look at the details of my Windows (C:) drive, it tells be there are "4.77 GB free of 66.7 GB".

When I look at the details of any of the drives I have mapped to SharePoint, I see the exact same storage information as I do when I look at my C: drive (4.77 GB free of 66.7 GB).

Is there something funky going on, or am I just misunderstanding how mapped drives really work?

Ƭᴇcʜιᴇ007
  • 111,883
  • 19
  • 201
  • 268
Stupid Clown
  • 73
  • 1
  • 4
  • I’m not that familiar with SharePoint – how exactly do you map a drive? – Daniel B Jan 08 '16 at 15:40
  • a drive mapping is a sort of shortcut, so there is nothing funky going on. You just made a shortcut of your C:\ drive to your sharepoint site. The actual size of the disk will be the same on the mapped item. – doenoe Jan 08 '16 at 15:42
  • You map it as you would any other drive, except you would paste the SharePoint document library URL in the folder field. – Stupid Clown Jan 08 '16 at 15:44
  • OK. I see. So the info about the available storage has nothing to do with the mapped drives. Right? – Stupid Clown Jan 08 '16 at 15:53

2 Answers2

2

It's because WebDAV ("Web Distributed Authoring and Versioning") is used to create the drive mapped to the SharePoint URL.

From Microsoft's KB2386902: WebDav mapped drive reports incorrect drive capacity:

Cause:

...WebDAV protocol doesn’t support querying server’s disk capacity. With this constrain of WebDAV protocol, Windows client sets WebDAV mapping drive’s capacity the same as its System Drive.

Resolution:

This is by design. A WebDAV mapped drive's capacity is set to match the client machine's System drive capacity. This means that the capacity you get from a WebDAV mapped drive is the same as your local System drive. System drive is where Windows is installed.

Example:

On a Windows client:

System drive C:\

Free disk space: 39.9 GB

Used Disk Space: 11.2 GB

WebDAV mapped drive Y:\

Free disk space: 39.9 GB

Used Disk Space: 11.2 GB

Community
  • 1
Ƭᴇcʜιᴇ007
  • 111,883
  • 19
  • 201
  • 268
0

Microsoft's statement is incorrect.

As shown in the RFC 4331 standard it is actually supported. Microsoft just didn't implement it.

Community
  • 1
tcr
  • 1
  • 1
    I suspect that KB article predates RFC 4331 by several years, so it _wasn't wrong_ at the time – they just never bothered to update the Windows client later. – u1686_grawity Mar 16 '21 at 23:12