How can i disable the option "view in a windows explorer" from a particular form library?
Stump the Panel » Site Managers and Site Collection Managers
Disable "view in widows explorer"
(8 posts)-
Posted 6 months ago #
-
Amila,
Aside from disabling "WebDav" from the site collection, you may have to resort to a programmatic approach, or build a custom feature to hide the option (which may only be at "Site-level" and not "Document library-level".It's a bit out of scope for this forum, but here's a few resources for you on how to approach it if you wanted to look at building a custom feature for this.
MSDN thread discussing something similar: http://social.msdn.microsoft.com/forums/en-US/sharepointdevelopment/thread/7d19d5f1-f61a-415f-9b70-b882e881dd32/
MS references for adding custom actions:
http://msdn.microsoft.com/en-us/library/ms473643.aspx
http://msdn.microsoft.com/en-us/library/bb802730.aspxOne of the other moderators may have additional ideas as well...perhaps one can chime in? :)
- Dessie
Posted 6 months ago # -
Since the options in that list are largely created by JavaScript, others have had some success hacking the menus with JavaScript. This thread actually has some discussion of both options:
This isn't a "secure way" to do this and someone can still map the library like a network place.
Posted 6 months ago # -
we are looking at all these sources.
Can you explain a bit on disabling Webdav? Is it from IIS? What is the end effect?Posted 6 months ago # -
Based on permissions, use "Use Remote Interfaces - Use SOAP, Web DAV, or SharePoint Designer interfaces to access the Web site. " to control who can access it.
On a server-wide level, webdav in SharePoint isn't really webdav at all (meaning it doesn't use the webdav dlls you see in IIS). So disabling it probably means changing permissions (in IIS maybe) to MSDAIPP.DLL which could have other ramifications for site operation.
I heard of another method that uses urlscan: http://technet.microsoft.com/en-us/security/cc242650.aspx
to block certain url requests on a server.Whatever you do, try to make it as non-evasive as possible and something you can undo if it doesn't work.
I did notice in my own tests that SSL sites had problems accessing the webdav beyond the local network. That could have just been my institution's firewall or something but it may be worth a look.
Posted 6 months ago # -
Although removing the permission "Use Remote Interfaces" will remove the option to open in windows explorer, it has the side-effect of removing Office integration features as well (permission option of "Use Client Integration Features" is tied to "Remote Interfaces"). Users would have to work locally on their machines then upload after (they wont be able to use options like "Edit in Microsoft Word" within the library itself).
I know you can also disable certain abilities within the ONET.xml file as well (disabling access with SPD for example), so that may also be an option (havent tried myself).
- Dessie
Posted 6 months ago # -
Yeah, I think it's hard because they never intended for it to be disabled. But with the lack of metadata processing, I know why some implementations want to discourage it.
Posted 6 months ago # -
thanks guys, I ended up with this for the moment;
http://scothillier.spaces.live.com/blog/cns!8F5DEA8AEA9E6FBB!280.entry?_c=BlogPart
Posted 6 months ago #
Reply
You must log in to post.