JasonSamuel.com

When you’re applying updates to a large farm, you really need to check the version number of SharePoint running on each server in the farm in order to maintain consistency.  You can do this easily by going to CA > Operations > Servers in Farm.

But what do these version numbers actually mean?  There’s a great Wiki maintained here that can answer this:

http://www.sharepointdevwiki.com/display/SharePointAdministrationWiki/SharePoint+Versions

This page will show you all the past and current version numbers and their associated KB articles.  Very handy when troubleshooting updates or if you want to check the change log between versions.

This is an easy one but requires a little bit of work to get working correctly.  SharePoint uses a feature called Index Server to search documents but it doesn’t search within PDFs by default. Searching inside PDF documents requires an iFilter from Adobe which they designed for 3rd party systems to read the PDF file format. Adobe includes this filter with Adobe Reader or you can download iFilter separately from Adobe’s site if you don’t want Reader installed on your SharePoint servers. 

http://www.adobe.com/products/reader – Latest version of Adobe Reader

or

http://www.adobe.com/support/downloads/detail.jsp?ftpID=2611 – x86 iFilter
http://www.adobe.com/support/downloads/detail.jsp?ftpID=4025 – x64 iFilter

 
CENTRAL ADMINISTRATION
Now in SharePoint itself, you need to configure the search service to index files with the .pdf extension:

1. Go to CA and open up the Shared Service under Shared Services Administration.
2. Click Search Administration under the Search section.
3. Click File Types in the left nav bar and then click New File Type.
4. Enter “pdf” and click OK.

ICONS
You will also want to display the PDF icon next to PDF Documents in SharePoint.  You can download the icon from here:

http://www.adobe.com/images/pdficon_small.gif

and copy it into the 12 hive folder here:

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\IMAGES

Then open up this XML template file:

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions \12 \TEMPLATE\XML\DOCICON.XML

and add the this line in the <DocIcons.ByExtension> section if it isn’t there already:

<Mapping Key=”pdf” Value=”pdficon_small.gif”/>

REGISTRY
Now on to the registry changes you need to make on each index server.  Make sure to backup your registry before making any changes.  These two changes will register the Adobe PDF iFilter with the Office Search service.  The values that need to be changed are:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Search\Setup\ContentIndexCommon\Filters\Extension\.pdf

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\Search\Setup\ContentIndexCommon\Filters\Extension\.pdf

Both values should be changed to:

{E8978DA6-047F-4E3D-9C78-CDBE46041603}

SYSTEM PATH
Now you need to add the Adobe install directory to the System Path envrionmental veriable so that the search service can find the dll which provides the iFilter service:

1. Right click My Computer
2. Click Properties
3. Click Advanced
4. Click Environment Variables
5. In the bottom half of the window, find the Path variable and double click it.
6. At the end of the value, add:

;C:\Program Files\Adobe\Reader 9.0\Reader

RESTART SEARCH SERVICES
Now you need to restart the Office Search service so that all changes are reflected. Open up cmd prompt and type

sc stop osearch [press enter]
sc start osearch [press enter]

Or just restart it via the Services MMC.

If you already have PDF documents in SharePoint that you want to search inside, you have to ”Reset all crawled content” in Search Settings and then begin a new ”Full Crawl” under Content Sources.

Anyone that builds SharePoint environments knows CodePlex (Microsoft’s Open Source Project Community) is the biggest hub for free SharePoint solutions.  I’m always looking for add-ons to play with in my SharePoint farms.  Here are a few that I find very useful.  MAKE SURE to test them out in a test farm before deploying to a production environment!!!  Every company’s SharePoint farm is unique so you must make sure a 3rd party add-on doesn’t break functionality for existing or custom webparts or create security issues before deploying to a live farm:

1. SharePoint Learning Kit (SLK) – http://slk.codeplex.com/ - Used as an e-learning and delivery system.  Think of it as a student teacher portal.  A lot of school districts like this one and it has a huge following. 

2. PlanetWilson Color Calendar – http://planetwilson.codeplex.com/ - Gives you the ability to color code Sharepoint calendar entries.  Immensely popular with users!  Once you install it, you’ll wonder how you ever used a Sharepoint calendar without it.  Big kudos to Mark Wilson for developing this project!

3. Smart Tools for Sharepoint – http://smarttools.codeplex.com/ - A ton of nice little tools that will make your life as an admin or user easier.

4. ChartPart – http://chartpart.codeplex.com/ - Generate graphs from Sharepoint lists.  A lot of users request this feature so give it a shot.  There are other alternatives out there too that I have tried but ChartPart has been prettty popular with my end users.

5. SharePoint Access Checker Webpart – http://accesschecker.codeplex.com/- Allows site owners to check access for users within their site.  Helps keep requests to Sharepoint farm admins down when site owners can easily check their security settings.  It can also check permission inheritance.

6. SPWakeup – http://spwakeup.codeplex.com/ - I had previously made a blog entry about this.  It allows you to “warm up” your Sharepoint farms so the first users of the day don’t have to wait for your app pools to spin up and your IIS cache to be rebuilt.

These are just a few I find very useful.  Hope they help you out!