Monthly Archives: November 2014
I was recently working with documents stored in SharePoint (Office 365 to be exact) and was seeing poor performance when trying to open file types with applications other than Office. At first I just put it down to a slow connection to Office 365, but I quickly realised that accessing files from Office 365 via alternate means (CSOM, Web Services) was much faster. I also found that the ‘Open with Explorer’ function (available on the Library ribbon as shown below) was slow to open.
In both scenarios I saw the performance issue (1) Opening non-Office files from SharePoint, and (2) Using the Open in Explorer function, the underlying technology that is performing the communication is WebDAV. WebDAV is the layer that makes it possible for applications that were not designed to work with SharePoint to.. well.. work with SharePoint I guess! WebDAV is actually a standard and isn’t SharePoint specific but I won’t go into that here. Suffice to say I’d isolated my issue down to being a performance issue related to WebDAV.
Now I knew what I was troubleshooting, the answer was readily available. Here’s the official KB of a known issue with WebDAV and the auto-detect settings option in Internet Explorer http://support.microsoft.com/kb/2445570
This was the fix for me:
In Internet Explorer, open Internet Options
Select Connections | LAN Settings
Uncheck ‘Automatically detect settings’
That’s it. After making this change I could go back to SharePoint and the SharePoint Library ‘Open in Explorer’ action was 4x faster than it had been. I was also getting much faster opening times of my non-Office files.
How to install/enable the WebClient (WebDAV) Service on Windows Server 2012 to open/edit SharePoint files
Are you having trouble opening/editing files stored in SharePoint, especially non Office files on Windows Server 2012?
By default the WebClient service is not installed on Windows Server 2012. Without this service running, opening/editing of non-Office files stored in SharePoint is very restricted.
To enable the WebClient service in Windows 2012 follow these steps:
Start Server Manager | Manage | Add Roles and Features
Select Installation Type of Role based or feature based installation
Choose the server to install the feature on (in my case I’m running server manager locally on the server I want to install the WebClient service on)
Just click Next to skip over Server Roles (it’s a feature we want to enable not a role)
Expand the User Interfaces and Infrastructure feature. By default this feature is partially installed. We need the Desktop Experience component of this feature. The WebClient is bundled with this component. According to Microsoft it is only possible to install the WebClient by enabling the entire Desktop experience and WebClient is not available on it’s own (https://social.technet.microsoft.com/Forums/windowsserver/en-US/e4ac654f-6d75-431d-baff-2f9dd511980a/installing-webclient-service-without-desktop-experience?forum=winserverTS)
Check Desktop Experience and you will be prompted to also install the pre-requisite Ink and Handwriting Services. Click Add Features.
This change required a server restart for me (and the feature installation continued after the restart) so check the option to have the server automatically restart if required.
Click Install and your server should restart and the feature installation will complete once the server comes back up.
Now check the Windows Services and ensure WebClient is present and running