SharePoint 2007 and Office OneNote 2007

When looking to allow indexing of OneNote 2007 content (to allow for searching) within SharePoint Server 2007, I was directed toward this Microsoft KB: How to configure SharePoint to let you search OneNote 2007 content on SharePoint sites (KB925765). KB925765 describes the way to enable the indexing of OneNote content on MOSS 2007 using 5 steps:

  1. Install OneNote 2007 on the server
  2. Add…….

It really doesn’t matter what steps 2-5 are…step 1 really threw me for a loop. Install a Microsoft Office suite product on the server?!?!?! You have to be kidding me!

No Microsoft Office suite product (i.e. Word, Excel, PowerPoint, Publisher, OneNote, etc.) should ever be installed on a production server, IMHO! In fact, I would go as far to say it shouldn’t be installed on a development server either, especially if you don’t have a clean QA server because how do you know what you have configured on your DEV server will work on production when you have a client OS product (Office suite) installed on your DEV server?!

Seeing KB925765 got me worried, because people around my office hate it when a server admin says ‘no’ to a developer.

So, I kept looking and finally stumbled upon this KB: How to register Microsoft Filter Pack with SharePoint Server 2007 and with Search Server 2008 (KB946336). Ah, the wonderful Microsoft Filter Pack! The Filter Pack “includes IFilters for the following formats: .docx, .docm, .pptx, .pptm, .xlsx, .xlsm, .xlsb, .zip, .one, .vdx, .vsd, .vss, .vst, .vdx, .vsx, and .vtx.”

Following the instructions listed in KB946336 gave me exactly what I needed. There are also instructions on how to use the Filter Pack with WSS 3.0 and SharePoint Portal Server 2003.

Thank goodness I didn’t take the word of my fellow associate and go with KB925765!

Nashville SharePoint Users Group

If you are in the Nashville, TN, USA area and would like to hear wonderful SharePoint presentations, FREE! food, and great discussions with like-minded people, then come join us! The meetings are always free and open to the public.

Information concerning the Nashville SharePoint Users Group can be found here:

The Nashville SUG website also has copies of the . Some of the topics include:
-> Upgrading SPS 2003 Areas and Portals to MOSS 2007
-> Certification Options for SharePoint Professionals
-> Using K2 and MOSS for MOF
-> Free Tools for SharePoint 2007 and WSS 3.0
-> SharePoint Backup and Recovery along with Best practices for My Sites
-> A Practical Approach to SharePoint Content Management
-> …plus lots more!

Using STSADM to Add Permissions to SharePoint Sites

Recently I came across multiple WSS sites (v3) that someone else created. These sites are used by everyone in the company and were not provisioned correctly; the permissions were incorrectly setup.

So, instead of visiting every site and adding the appropriate permissions, I created a batch file that went through the sites and added several SharePoint groups and individual users to the sites in different roles.

The stsadm operation I used was ‘userrole’. The syntax of the userrole operation is as follows:
stsadm –o userrole –url <full url> –userlogin <domain\user or SharePoint group> –role <role, such as Contribute or “Full Control”>

I created the script in Excel so I could put it together rather quickly. I created three (3) columns in a new Worksheet.
-> The first column [A] was for the full URL of the sites
-> Second column [B] was for the following function: =”stsadm –o userrole –url “&A2&” –userlogin “&C2&”<SharePoint group name or domain\user>”&C2&” –role “&C2&”<intended role>”&C2
-> The third column [C] holds a double quote mark – “ (this is done so I can enter the “ symbol in the outputted text, but not within the function. The quote is needed in the output text because your SharePoint group or role may have spaces in the names)

For example, one of my cells in the [B] column looked like this:
=”stsadm –o userrole –url “&A2&” –userlogin “&C2&”SharePoint Members”&C2&” –role “&C2&”Contribute”&C2

The output text looked like this: stsadm –o userrole –url http://sharepoint/site1 –userlogin “SharePoint Members” –role “Contribute”

I then logged into the Windows 2008 SharePoint front-end server as a SharePoint Farm Administrator and copied all the text in the [B] column to a text file and named it permissions.cmd. I ran the file as an administrator (making sure the current directory was the ‘12 hive’ where the stsadm.exe resided) and after a few moments, all was well with the permissions.

You can also use the userrole operation to remove permissions by adding the –delete switch. For more information on the userrole option, type stsadm –help userrole

File Not Found When Trying to Create a Site

I recently was trying to create a SharePoint site and was surprised to see a “File Not Found.” error when I submitted the action. After scratching my head for a short amount of time, I remembered that I had created a managed path that was the same name as the site I was trying to create.

After removing the managed path, I was able to create my site and go merrily along my way.

Remove (Hide) SharePoint Templates

I have been asked several times about removing some of the templates that are available at site creation. There are several reasons you might want to do this and it really is simple to implement.

To hide a template from users, open the Webtemp.xml file located in the /program files/common files/Microsoft shared/web server extensions……/template/1033/XML folder. Change the Hidden parameter of the template(s) you want to hide. Recycle IIS and you should be set.

BTW, don’t even think about editing anything other than the Hidden parameter in the Webtemp.xml file. You don’t want to fall into the unsupported configuration category as KB 898631 explains.

Solutions Using the Microsoft Office System

I recently ran across a little gem on the TechNet website: “Solutions Using the Microsoft Office System: Learn how to use the Microsoft Office system to solve your business scenarios
This page includes over 40 large Visio diagrams detailing the Microsoft Office system, over 30 of which specifically reference SharePoint as a central topic.

The topics include InfoPath and Forms integration, scenarios using SharePoint (such as a Call Center, Intranet Portal, Internet News Site, etc.), Records Management, Business Intelligence, and detailed SharePoint Server topics including:

  • Application Security
  • Backup and Restore
  • Topologies
  • Baseline Site Hierarchies
  • Customization
  • Database Administration
  • Enterprise Content Management
  • Extranet Topologies
  • Inter-Farm Shared Services
  • Search Administration
  • Shared Services

The information presented can give you a really good understanding of the functions of SharePoint Server. I am currently diving into the Backup and Restore diagram. I just wish I had a poster printer for them!

Upgrade WSS 2.0 to WSS 3.0 or SharePoint 2003 to MOSS

It would be great if we all had a detailed guide to show us the upgrade steps specific for us. A step-by-step guide is a little more complicated than you might think. Without knowing your environment, any plan anyone will give you will be at least a little generic.

However, Microsoft has done a pretty good job at providing the steps. You will need to make your decision on how you will upgrade your environment. Your choices are gradual upgrade, in-place upgrade, and database migration. Basic concept: if you have a highly-customized environment, you will have a more complicated, but not impossible, upgrade path.

Instead of rewriting what has already been said, I suggest following Joel Oleson’s advice in his post labeled Best of… Upgrade and Deployment Guides for WSS v3 and Microsoft Office SharePoint Server 2007.

If you follow the steps listed on Microsoft’s TechNet site, you will probably have a successful upgrade. But, you have to read it all!
I suggest start at the beginning: Upgrading to Office SharePoint Server 2007

Here are the links to the sections below the link above.

If you want to do this correctly, you will need to read the content and make an informed decision on your path to upgrade. I have done upgrades and it can be a pain. But once it is done, you will love your new environment!

Response to a SharePointU post here: