SharePoint Blog - René Hézser

Anmelden  RSS Feed RSS Feed
Startet die Suche

Archive

Kategorien

Links

Andere Blogs




ITaCS GmbH

Jan 122012

Major Update to the Fileserveraccess Web Part

In 2008 I’ve released a Web Part, which enables your users to access files on your fileservers through SharePoint. Original post. This Web Part has been downloaded many times. With this new version, I’ve tried to deal with the most asked questions (like Kerberos), which will make the Web Part easier to use. Naturally new features have been implemented, to get you to upgrade to the new version.

With this release, the Web Part requires SharePoint Foundation / Server 2010. For the users who are still using WSS V3, please stick to the old version, or upgrade your farm Smile

First some screenshots, so you know what I am talking about.

image

image image

Features

  • Download files from your fileservers via SharePoint
  • Download a folder with all containing files as zip-file
  • Upload files to a fileserver
  • Delete files from a fileserver
  • View the file properties
  • By default, the fileserver path has to be UNC. Local paths are not allowed, so a user cannot enter C:\ to access e.g. the web.config or other files on the local server
  • Multilanguage

Of coarse the access to the files is security trimmed. Meaning that if your users would not be able to access files with their logon from their client, they won’t be able from the Web Part!

Requirements

For authorization against the fileserver, the credentials of the currently logged on user is used. For SharePoint (and any other application as well), it is necessary to configure the WebApplication which is hosting the Web Part to use Kerberos instead of NTLM. Otherwise a server cannot pass the user credentials forward to a second server. This is called the “Double-Hop problem”. To get a glimpse about the topic, take a look at an article I wrote some time ago. Configuring Kerberos for SharePoint. That post has been written for SharePoint V3! But thereimage are plenty of Kerberos Guides out there for SP 2010. And a whitepaper from Microsoft: Configuring Kerberos Authentication for SharePoint 2010 Products http://technet.microsoft.com/en-us/library/ff829837.aspx

If you do not configure Kerberos for the WebApplication, the Web Part will detect that, and show a notification in the properties section.

A small sidenote: If you are going to use local paths (meaning a folder on your SharePoint server), you can continue using NTLM. 

Another good starting point for Kerberos-Troubleshooting can be found here: http://blogs.msdn.com/b/friis/archive/2009/12/31/things-to-check-when-kerberos-authentication-fails-using-iis-ie.aspx

Configuration

image

To use the WebPart, you’ll need to at least configure a path. Files – and subfolders – from that path will be shown.

Additionally, there are some properties, which modify features of the Web Part.

The Paging size defines, how many files are displayed on one page. With the next three checkboxes, you can allow files to be downloaded as zip, allow files to be uploaded and to be deleted.

I recommend to leave the caching activated. Deactivate only, if you have specific reasons, because there will be more todo for your SharePoint server and fileserver.

Using a local path as source

In case you want to use a local path as source for the Web Part, you have to allow the path to be used. To do so, follow the steps below.

  1. locate the feature.xml file ("C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES\FileserverAccess\Feature.xml")
  2. Edit the file in your favorite editor
  3. Look for the property with the key “AllowLocalPaths” and modify the value to correspond to the driveletter you wish to use
    image
    Replace “Driveletter” with e.g. “C”. You can specify more than one drive letters. In that case use a “;” as divider
  4. Save the feature.xml
  5. Restart your IIS (iisreset)

Remember that you’ll need to modify the file on all of your FrontEnd SharePoint Servers! After an upgrade of the Web Part, the file has to be modified again. If you do not allow local drives, the Web Part will show an error.

image

This version is compatible to the old version. So you can simply upgrade the solution and benefit of the new features!

Download the new version for SharePoint 2010 (Foundation and Server): RH.FileserverAccess.wsp

Download the old version for WSS V3 / MOSS 2007: RH.FileserverAccess.wsp


Dec 202011

Update to the “My Alerts” Webpart

I’ve made a small update to the My Alerts Webpart.

The update improves SharePoint 2010 support.


Published: 12/20/2011  7:17 PM | 0  Comments | 0  Links to this post
Tagged as: Development, MyAlerts, SharePoint, Webparts

Aug 172009

Active Directory User Editor

SharePoint is importing user information from the Active Directory through the Shared Services Provider (if you have MOSS).

Wouldn’t it be nice if users could “manage themselves”? That would save lots of time for the Admins :-)

The answer is here: http://nominesptools.codeplex.com/

  • 5 different types of properties fields: Simple TextBox, DropDownList/ListBox (with predefined values), People Picker, Date Picker with calendar.
  • Multi-domain compatible.
  • Nearly Any Active Directory property can be easily added or removed of the edit form, directly trough the webpart configuration (nothing "hard-coded").
  • SharePoint "look & feel"
  • Available in English and French

Additional informations and installation manual are available here (French & English): http://alexis.nomine.fr/

image

This Webpart is again a prove that there are plenty SharePoint solutions for you to use.

btw: this was my post #200 :-D


Published: 8/17/2009  7:49 PM | 1  Comment | 0  Links to this post
Tagged as: CodePlex, Webparts, Products, SharePoint

Jan 072009

Upload documents/pictures to a discussion lists

You might already know my Wiki Webpart, which allows you to upload pictures and documents to a Wiki while editing it.

What is it?

With this Solution you can upload images and documents from the new/edit form into existing picture/document libraries. After the file has been uploaded, a link will be inserted into the Body.

This is either a <img> or a <a> tag, depending on the uploaded file.

How does it work?

After uploading the image/file, it will be put into your Body via JavaScript. There is no reload of the page required.

Requirements

.NET 3.5 (SP1) on all of your frontend servers

Installation

The DiscussionListUpload comes as a SharePoint solution (wsp file), which will be installed on your SharePoint farm via "stsadm -o addsolution -filename RH.DiscussionListUpload.wsp".

The solution contains one feature, which has to be activated on site collection level.

After the feature has been activated, discussion lists will have a new link in the list properties.

If you click on the link, it will bring up a settings page for the feature.

Enabling the feature in the properties will add the Webpart to the NewForm and EditForm of your discussion list. Disabling it, will remove the Webparts.

Update:

Instead of this solution you can use my Custom Files and Images Upload Field.

If you want to use it, please make sure you disable this feature on the discussion list and on your sitecollection.

Download

Download Solution

Download Source code

Technorati Tags: ,

Published: 1/7/2009  12:08 PM | 8  Comments | 0  Links to this post
Tagged as: Webparts, Development, SharePoint, Upload Webparts