New Demos to Show the Benefits of Migrating Lotus Domino Apps to MOSS 2007.

There are some new click through demos which help demonstrate the collaboration capabilities of SharePoint to existing Lotus Notes customers.

• Transporter Suite 2007 for Lotus Domino Demo: Application Data Migration - Application migration to MOSS using Transporter Suite 2007.
• Project Tracking Application Template Comparison Demo
• Sales and Inventory Tracking Application Comparison Demo

Compares Lotus template based and custom apps with the equivalent SharePointMedia Player Web Part

Steve Sofian posted on his blog about the Media Player Webpart for MOSS.

I went to install it on another web application earlier today and found his blog has gone.

Steve, if your reading this I hope you don’t mind me posting it again.  All the credit is yours.

This webpart allows you to play avi, mpg and wmv files with in your MOSS site.

Sharepoint Learning Kit

Sharepoint Learning Kit is available from www.codeplex.com/slk

SLK is used to assign individuals documents that they have to review, download and edit, answer the questions etc…

SLK is SCORM compliant which enable schools to create learning content from such programs as MS Class Server Teacher and assign it pupils where they have to then answer the questions within the document.  When the pupil has completed the assignment the server automatically marks the answers and lets the teacher know the marks they got.  The teacher can see the answer they got, leave a comment for the pupil and also let the pupil know which answer they got wrong.  The server can do it all if you set it up to.  All you have to do is assign it to the individual.

How to get over the “OOTB syndrome” for MOSS WCM

I rarely rant, but in some cases I have very little choice. As it seems I had little choice but to rant at this question, statements that I was confronted by time and time again. I call this the “OOTB syndrome”. This is usually a symptom which is present in people who have stumbled upon SharePoint recently.

In the context of this post SharePoint = Microsoft Office SharePoint Server = MOSS

“We want to use the Out of the Box (OOTB) functionality of SharePoint to build our web site”

“SharePoint templates are not XXXX compliant”

“It’s too difficult to build web sites with SharePoint”

Recap of Last Weeks Training: In a Word – Awesome!

I have been meaning to write a re-cap of the training I attended last week. It was great to get to get some hands on time, and more importantly face time with some very smart folk here at Microsoft. Before I summarize I do want to give a few shout outs to some great folks who I didn’t recognize earlier on this.

First off, James Petrosky. Wow, what can I say? If you ever have the opportunity to work with James or attend any of his events he is a rock star! James led most of the training modules and did most of the ground work in getting the training together. His real world insight and willingness to address the audience needs rather than rigidly stick to script was great and just what we needed.

Enabling MySites in MOSS 2007

Okay, this might seem like kind of a corny post, but I have run in to a couple of people inquiring about how to enable MySites after they have disabled them by using my previous post.

Pretty much it is the reverse of the article, but for good measure I will just go through the steps here too.

Internal Alias Question: What does Excel Services with files that don’t come from SharePoint?

The following question was asked on the internal alias:

Q: When I open a workbook in the EWA web part via URL (say, to a \\unc\file\location), does that file ever get stored in the WSS DB in some interim step, or does it just open directly in memory?

The real reason I’m asking is that I’m curious if workbooks opened this way would be subject to WSS file storage limits.

Working with CAML.Net - Part 2 [ Introducing the CAML Query Designer ]

In Part 1 of this series, I introduced the CAML.NET Framework, which provides a way for C# developers (and eventually VB developers) to construct CAML queries and other data structures using a strongly-typed .NET language instead of XML.  This has the added benefit of enabling CAML queries to be packaged easily into .NET assemblies that can then be called from any .NET application.  It does this using a combination of static classes, generic methods and a base class library for automatic data-binding to and from SharePoint list items.

Upgrade Performance and Time to Upgrade

Performance and time to upgrade depends on a number of things.  WSS and SharePoint Server provide multiple methods to upgrade, each have trade offs as well as differences in performance.  MS IT included their numbers on upgrade performance which help one understand.  I think this document talks through some excellent recommendations such as “dry-runs” and trying it out and getting feedback from users.   I understand the question may be an end to end question which would have even more variables, but this should help outline it a bit better.

Video: Creating A Knowledge Center 5 of 6 – Building the Blogs Environment

Creating a Knowledge Center Series: 1 | 2 | 3 | 4 | 5 | 6

This is video 5 of 6 in the Creating a Knowledge Center Series, Building the Blogging Environment. When creating an area for blogs it is important that we understand how to aggregate them as well as customize them for our particular needs. Once we understand that setting up the area is a breeze.

Using CustomAction to modify system pages

In the last post, I covered 2 examples of how to safely modify functionality in ’system’ areas of SharePoint, such as Central Admin and the Site Settings area. The first example was a tweaked Recycle Bin (which listed only items deleted by the current user), and the second was a custom ‘Create Site Collection’ admin page. In both cases, the technique was to copy the original page which shipped with SharePoint, make the customization to the copy, and then redirect the link in SharePoint to use our new page. The customization is then fairly transparent to users - depending on your implementation, they could simply be clicking the same link in the same place in SharePoint, yet going to somewhere different which is offering your modified functionality.

Common Risks for Common SharePoint Projects

{Cross-posted from Robert Bogue [MVP]}

There are a variety of project types that leverage SharePoint. There are also a variety of risks that each SharePoint Project faces. This
matrix by Robert Bogue shows the potential impact of each risk on each project type

Here’s the handout

Enabling anonymous access for a site collection in MOSS 2007

Suppose my Site Collection is http://servername/sites/CGOmain on MOSS 2007 Steps 1: Go to “SharePoint 3.0 Central Administration” Select “Application Management” Tab Select “Authentication Provider” under “Application Security” group Select your web application. Select on the zone where you want o enable anonymous access. You will find check box “Enable Anonymous access”. Check it. Click “Save” When you set this option, anonymous…

Using SharePoint 2007 audiences in combination with MOSS Publishing placeholders

In one of our projects we had a requirement to target the content of a SharePoint Publishing HTML field to an audience. The content should only be displayed to users that are member of an audience. It was very easy to create this and below you can find the steps to create this yourself: Create a new class that inherits from Microsoft.SharePoint.Publishing.WebControls.RichHtmlField Add a public property that holds the name of the audience Override the Onload and implement this as below:

Upgrade Performance and Time to Upgrade

Performance and time to upgrade depends on a number of things.  WSS and SharePoint Server provide multiple methods to upgrade, each have trade offs as well as differences in performance.  MS IT included their numbers on upgrade performance which help one understand.  I think this document talks through some excellent recommendations such as “dry-runs” and trying it out and getting feedback from users.

KB Articles:

• Error message when you run the “SharePoint Products and Technologies Configuration Wizard” when you upgrade to SharePoint Server 2007 or to Windows SharePoint Services 3.0: “Failed to initialize SharePoint Product and Technologies upgrade”
• Error message when you try to use a feature in SharePoint Server 2007 to open an InfoPath form in a Web browser: “The URL /FormServerTemplates/InfoPath.xsn is an unsupported relative URL”

Frustrated with Content Deployment Job Import

For the past week I have attempted to create a staging server for my client’s Sharepoint Site.  The problem is that it will import 9100-9700 objects and then it will fail and issue me these errors:Content deployment job ‘Remote import job for job with sourceID = 378a003b-941d-46dc-979b-e7e276e60c77′ failed.The exception thrown was ‘System.UnauthorizedAccessException’ : ‘Access denied.’ andAccess denied. at Microsoft.SharePoint.SPGlobal.HandleUnauthorizedAccessException(UnauthorizedAccessException ex) at Microsoft.SharePoint.Library.SPRequest.PatchUrl(String bstrUrl, String bstrWebRelFileUrl, String bstrWebRelOldUrl, String bstrWebRelNewUrl, Int32 grf) at Microsoft.SharePoint.Deployment.ImportObjectManager.FixLinkInFile(String fileUrl, Guid webId, String oldTargetUrl, String newTargetUrl) at

SharePoint Content deployement - step by step tutorial

I was looking around and realized that I couldn’t find an easy set of instructions to set up Content Deployment in Microsoft Office SharePoint Server.

In this post, I’ll show you how to set up content deployment from a staging site collection to a production site collection. For simplicity, I will host both site collections on the same server.

For a background on content deployment, see: http://blogs.msdn.com/sharepoint/archive/2006/05/02/588140.aspxA SharePoint 2007 (MOSS/WSS) WebPart to show up all subsites under a site

Here is the code for the WebPart:

 

using System;

using System.Runtime.InteropServices;

using System.Web.UI;

using System.Web.UI.WebControls.WebParts;

using System.Xml.Serialization;

 

using Microsoft.SharePoint;

using Microsoft.SharePoint.WebControls;

using Microsoft.SharePoint.WebPartPages;