Home » Sharepoint

Windows Server 2008 R2 - "Open in Windows Explorer" only works in special cases


I am running SharePoint 2007 off a Windows 2008 R2 server and it seems to be running fine.

We're using another Windows 2008 R2 server for clients to login to (using remote desktop) and connect to the SharePoint site. However, whenever a client tries to use the "Open in Windows Explorer"-feature when handling documents, nothing happens. I have run through all the posts here and checked that all services, webdav modules, etc. are as they should be.

I found a fix recently, but it does not make a lot of sense. If I go directly to the site after logging in, it does not work (as expected). However, if I type in the direct path to the documents folder, \\sitename\cases, it opens just fine and if I open a new browser AFTER that, the "Open in Windows Explorer" feature now works perfectly fine.

Is there some way to fix this behavior other than adding a "net use" command to all startup scripts for all the users? It seems like I'm circumventing the problem rather than fixing it.

EDIT: We disabled UNC paths (because of security issues on the client server), but even if we tells you the path is disallowed, simply typing it in triggers the function to work (and still gives you access through SharePoint). Very odd.


2 Answers Found


Answer 1



Please check and confirm that the WebClient Service is shown and running

Start =>Administrative Tools =>Services

Check the features of Windows Server 2008 R2

The name of the feature which supports this functionality called as Desktop Experience.


Note: The WebClient service is installed only when you install the Desktop Experience feature on the Server 2008 machine.



1.) Start =>Administrative Tools =>Server Manager

2.) In the Server Manager => go to Features and Add Features

3.) Select the Desktop Experience Feature and install it. Then Restart the Server (Required)

4.) Start =>Administrative Tools =>Services

5.) Select the Web Client Service and Start it.


check out for the following Registry Key on the Affected Systems:


Click Start, click Run, type regedit, and then click OK.

Locate and then double-click the following registry subkey:


On the right side, double-click restrictanonymous.

Make sure that the value in the Value data box is set to 0, and then click OK.

Close Registry Editor.

Restart the computer.


Also based on the above findings we may have to apply hotfix http://support.microsoft.com/kb/972584


Hope this helps ,






Answer 2

Agree with all the above, plus if you are running a terminal server then it's a good idea to disable Internet Explorer Enhanced Security Configuration for your users, as this will no doubt interfere with their browsing experience.





<< Previous      Next >>

Microsoft   |   Windows   |   Visual Studio   |   Sharepoint   |   Azure