Welcome to Kraft Kennedy

When you click “New Item” in any SharePoint list or “Upload” in any document library, SharePoint sends you to a standard form for creating the new item.  Behind the scenes, SharePoint also passes in two parameters to let the form know where to post the item and where to go after the item is posted.  By leveraging these two parameters in the URL, you can make a link anywhere that posts data to any list and sends you someplace else when finished.  This has come in handy for us when creating intranet home pages, as we can create a list of links to post data to custom lists, which sends the person back to the home page afterwards.  Otherwise, the person would end up in the root of the list or library they submitted the item to.  So we were able to easily meet a requirement that the person be directed back to the home page after submitting the item.

Continue reading…

In a previous post, I discussed some useful free web parts for Windows SharePoint Services 3.0.  In this article I’ll discuss two more very helpful solutions for building extranets in SharePoint and for building more advanced workflows in SharePoint Designer.
Continue reading…

Most of the information in an employee’s MySite profile comes from the Active Directory profile import, which is set up in the SharePoint Shared Service Provider.  However, this can be tricky with employee photos since links to photos are not normally stored in Active Directory.  An easy way around this if you don’t want to store the links in Active Directory, is to simply create a picture library in SharePoint and upload all of the employee photos to the picture library with a standard name, such as username.jpg.  Then you can write a script to update each MySite profile and associate the photo with the person.
Continue reading…

Autonomy iManage and OpenText eDocs both have protocol handlers for SharePoint, which enable the SharePoint Enterprise Search engine to index documents stored in the DMS, while keeping the documents in the DMS.  Many people haven’t been aware of this and thought you had to migrate all of the documents into SharePoint to search them, or to use an enterprise search engine provided by the DMS vendor.  However, these protocol handlers can provide the best of both worlds by allowing you to continue managing documents in the current DMS, while taking advantage of Microsoft’s FAST enterprise search indexer to index the DMS content, SharePoint content, file shares, web sites, Exchange public folders, and other enterprise systems.  Security trimming is preserved by the protocol handler, so users will never see documents in the DMS that they don’t have access to.  The protocol handlers both support Microsoft Office SharePoint Server 2007.

More information on the OpenText eDocs SharePoint integration and protocol handler can be found here:

http://www.opentext.com/download/livelinkdownload.html?path=product/microsoft/ot-clmsp-edocs-po.pdf

More information on the iManage SharePoint protocol handler can be found in their partner portal, by filtering the list of products to “SharePointProtocol Handler.”  Note that you need a partner login account to download the documentation and release notes.

http://worksitesupport.interwoven.com/WorkSite/scripts/portal.aspx

Both vendors also offer a comprehensive set of web parts to drop into a SharePoint environment to view and manage their documents from within a SharePoint site.

Windows SharePoint Services (WSS) doesn’t come with a whole lot of web parts out of the box, but here’s a few handy ones we’ve found to spice up some of the home pages we’ve built.  These are all free and work with WSS.

• Tim Heuer’s RSS Feed Reader
  http://feedreader.codeplex.com/

Only MOSS comes with an RSS reader, and even that one can display only one feed.  This web part is invaluable if you’re using WSS.  This is the best free RSS feed web part that I’ve found, and it allows you to neatly pull multiple feeds next to each other.

• Bamboo World Clock and Weather
  http://store.bamboosolutions.com/pc-55-1-world-clock-and-weather-web-part.aspx

This web part neatly displays the weather in 3 cities side-by-side and can optionally display the time if they are in different time zones.  This is a nice looking web part and tends to fit nicely on the right-hand side of a home page for a firm with multiple offices.

• Amrein MSN Money Stock Quote
  http://www.amrein.com/apps/page.asp?Q=5731

This web part displays stock quotes, company names, changes, and percent changes pulled from MSN Money.  It’s the best free web part I’ve seen to do this, and will save a lot of time over trying to follow one of the examples online for doing this with a data view.

• Matt Jimison’s Twitter Search Web Part
  http://www.mattjimison.com/blog/2009/03/04/twitter-search-webpart/

This uses the twitter search API to search twitter based on the parameters you specify in the web part, and you can download the wsp or the source code from the web page.

• Kraft & Kennedy Google Search Box
  (Code below)

We’ve had a few instances where we were asked to put a Google search box on a SharePoint page.  This can easily be accomplished by just inserting a content editor web part on the page and editing the HTML directly.  You can paste in the following code, which includes JavaScript, to open a Google results page after the person enters a search term and presses enter or clicks a button.  This is of course a simple approach–you could also federate search results in your search center to include Google–but this simple html code works well in many cases.

<P align=left>Search Google: <INPUT id=Google name=Google onkeydown="javascript:if (event.which || event.keyCode){if ((event.which == 13) || (event.keyCode == 13)) {
window.open('http://www.google.com/search?hl=en&amp;q=' + this.value + '&amp;btnG=Google+Search','_blank','');
return false;}};"> <IMG alt="Go" id="btnGo" name="btnGo" src="/images1/icongo.gif" onclick="window.open('http://www.google.com/search?hl=en&amp;q=' + document.all.Google.value + '&amp;btnG=Google+Search','_blank','')"  onmouseover="this.style.cursor='hand'">
</P>

Whether or not SharePoint can be a viable DMS at a law firm has been a big point of contention in the legal community.  A lot of this comes down to the mentality and size of the firm, and the specific requirements that the firm has for document management.  With proper planning and one or two simple addins, SharePoint may be a viable DMS for certain firms that are flexible and willing to invest in a development effort.

The advantages of using SharePoint as a DMS are many:

• Being able to wrap an intranet or extranet around all of your content.
• Having basic matter management features available in every workspace, such as a shared calendar, task lists, and discussion threads.
• Having access to document workflows.
• Being able to search all of your repositories with Enterprise Search (available free with Microsoft Search Server Express.)
• Being able to integrate business intelligence dashboards.
• Providing access to web 2.0 features such as wikis, blogs, and personal sites.
• Leveraging native Word features, and not having to rely on vendors to update their software to support the latest version of Office.

Continue reading…

I recently downloaded the technical preview of SharePoint WorkSpace 2010, but was disappointed to find out that I couldn’t test any of the SharePoint features.  It’s only compatible with SharePoint 2010, so anyone interested in exploring all of the new features will have to wait a few more weeks/months until the technical preview of SharePoint 2010 is made public.

SharePoint Workspace 2010 is the next version of Groove, the collaboration software acquired by Microsoft in 2005.  Groove 2007 was only superficially integrated into the Office Suite, and never got a large following, as it was included in only the most expensive versions of Office, and most people had no idea what it was.  SharePoint WorkSpace 2010 will be included in Office 2010 Professional Plus, on the other hand, allowing it to expand to a wider audience.  Additionally, it will integrate seamlessly with SharePoint 2010 and other Office products.

SharePoint Workspace 2010 allows for the creation of “SharePoint Workspaces” and “Classic Workspaces.”  SharePoint Workspaces allow you to access all SharePoint site content on your computer, whether online or offline.  This is an improvement over SharePoint 2007, where only document libraries and certain types of lists could be synched with Outlook.  While you had to go into a library’s action menu in SharePoint 2007 to connect it to Outlook, you can now connect the SharePoint 2010 complete site to SharePoint WorkSpace by clicking Site Actions –> Sync to Computer.  Alternatively, you can sync to a site from inside SharePoint WorkSpace by creating a SharePoint Workspace and specifying the url.

Classic Workspaces are the workspaces that were available in Groove.  Users can create document libraries, discussion threads, calendars, and invite other users and chat inside the workspace.  Classic workspaces use peer-to-peer technology to synchronize documents and files between users.  That allows users in different companies, on different networks, to still collaborate quickly and securely.

SharePoint WorkSpace 2010: New WorkSpace Menu

Continue reading…

Outlook 2003 and 2007 support a protocol called stssync, which allow SharePoint libraries to be viewed in Outlook.  Outlook 2003 allows for read-only viewing, whereas Outlook 2007 also allows for two-way synching of certain content.  The most common way of connecting to a SharePoint library is through the SharePoint Actions menu, as shown below.
Continue reading…

We often come across instances where firms are using NTLM Authentication (Windows integrated authentication) for SharePoint, and expect that Internet Explorer will automatically pass through the authentication from machines within the company, however they still get prompted for credentials.  This issue exists with any IIS website, not just SharePoint, but seems to come up more frequently with SharePoint sites.

The solution revolves around checking the security zones in Internet Explorer, and ensuring that the SharePoint site is included in a zone that will pass through the authentication.  Adding the site to “Trusted Sites” is often the first thought, however that does not work by itself, because “Trusted Sites” only pass the username, not the password, by default in Internet Explorer 7+.  The better choice is to put the SharePoint site in the “Local Intranet” zone, as that’s the only zone which passes both the username and password by default.  If “Trusted Sites” is used, an additional step is necessary beacuse you have to change the custom settings, find user authentication, and check the box to do an “automatic logon with current username and password.”

In order to add your SharePoint site into the “Local Intranet” zone, click Tools –> Internet Options in Internet Explorer.  Then click Security –> Local Intranet –> Sites.  Click “Advanced,” enter the URL of the SharePoint site, and click “Add.”  You’ll notice that the zone name listed in the lower-right corner of the browser changes from “Internet” to “Local Intranet,” and you won’t be prompted for credentials anymore.  Note that this type of pass through authentication is only supported by Internet Explorer, and requires that the computer be inside the corporate network.

WSS does not have a user profile service and does not allow any kind of native targeting of content to users in different groups. This is one of the more serious limitations of WSS, especially for corporate intranets, where pages might need to be customized for users in different offices. MOSS, on the other hand, allows for the creation of audiences and easy targeting of content. As is typically the case with WSS, it is possible to achieve this functionality by writing code.

One way to do this is by adding a reference in your code to “System.DirectoryServices,” which allows you to query Active Directory. With that class, you can compare the current user to an Active Directory group’s membership collection, and add logic based on whether or not the user is in the group. If you plan to edit an aspx page directly, you will also have to add a page parser path in web.config, so that the code in the page will run. Rather than editing the page directly, it is often preferable to create a control or web part for security and manageability reasons.

If editing an aspg page directly in SharePoint Designer, just add the following line to the top of the page, so that the correct assembly is referenced.

<%@ Assembly Name="System.DirectoryServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" %>

Then add a code block into the page that gets the current user and compares it to the group membership. The following example uses VB.Net and sees if the current user is in the “NY Staff” group. If so, then the script redirects to the page “NY.aspx.” Rather than redirecting, you could also add code to write out customized content based on the membership information.

               <%

    Try
   'Get group membership for current user
        Dim DomainUser As String = Replace(User.Identity.Name, "\", "/")
        Dim ADEntry As New System.DirectoryServices.DirectoryEntry("WinNT://" & DomainUser)
        Dim MembersCollection As Object 'Underlaying is a IADsMembers interface
        MembersCollection = ADEntry.Invoke("Groups")
        Dim group As Object 'IADsGroup interface
        Dim vFound As Boolean = False
        For Each group In MembersCollection
            If LCase(group.Name) = "ny staff" Then
                vFound = True
                Exit For
            End If
        Next
        'Do something if group is found
        If vFound Then
            Response.redirect("NY.aspx")
        End If
      Catch ex As Exception
        'response.write(ex.message)
      End Try
%>