Imaging 4.0 Rx for SharePoint 2010 Health Monitoring and Analysis

24. August 2010

SharePoint Foundation (aka WSS v4) comes with some new monitoring and analysis features to give administrator better control over activity and performance of SharePoint 2010 Farm via rules (SharePoint Maintenance Engine) and reporting. At KnowledgeLake we knew we needed a little something extra to effectively support our SharePoint and KnowledgeLake implementations, enter the KnowledgeLake Log Viewer, a Microsoft Silverlight application.

Read the full post at the KnowledgeLake Team Blog.

Administration, KnowledgeLake, SharePoint , , ,

SharePoint 2010 Document File Open Behavior

14. July 2010

This screen cast demonstrates how to change the behavior of opening PDF files and other un-trusted files served from SharePoint 2010.  

A Web Applications General Settings allow you to change the File Handling as it’s serviced from SharePoint to the clients IE 8 Browser.  By default the X-Download-Options of the MIME-Handling header is set to Force Save or noopen. To change the behavior set the Browser File Handling to Permissive rather than Strict to allow the file to be open in the browser.

 

 

Browser File Handling 
Specifies whether additional security headers are added to documents served to web browsers. These headers specify that a browser should show a download prompt for certain types of files (for example, .html) and to use the server's specified MIME type for other types of files.

  • Permissive Specifies no headers are added, which provides a more compatible user experience.
  • Strict Adds headers that force the browser to download certain types of files. The forced download improves security for the server by disallowing the automatic execution of Web content that contributors upload.

Administration, SharePoint ,

SharePoint 2010 Technical Reference Guides

7. July 2010

SharePoint 2007 Web Part - Close vs. Delete

26. April 2010

It’s important to understand the there is a difference when you “Close” a Web Part and deleting it via the “Modify Shared Web Page” or Site Actions/Edit Page.

image

Closing a Web Part essentially hides it.  If you Close the web part you can use SharePoint Designer and view the ASPX page, in this case the default.aspx page and you’ll see the hidden (grayed out) web part.

image

If you delete the web part, it physically deletes the web part from the page. 

image

Deleting the web part via Page Edit mode.

image

Web part is deleted from page as viewed from SharePoint Designer.

image

So why is this minutia important to know.  Well, it’s about load time and resources.  Closing the web part still loads the web part invisible to the users, hence it requires time and resources to load the web part.

The hidden Web Part Maintenance page

Now, if you’ve used the Close option and want to clean up and delete those old parts you can use the Web Part Maintenance page.  The problem is it’s not on any of the SharePoint administration links (at least none I could find), so you have to use one of the following URL query string command to get to it.

  • http://<server>/_layouts/spcontnt.aspx?&url=default.aspx
  • http://<server>/default.aspx?contents=1

Once your on the Web Part Maintenance page you can delete the web part for Personal or Shared use.

image

image

image

image

SharePoint, Web Part ,

XPS Full Text Search in MOSS 2007 and Windows Server 2008

5. April 2010

Late in 2007 the XML Paper Specification (XPS) was published.  The means to create, view and print XPS files are integrated in you Windows OS, dare I say it is as ubiquitous as PDF and you may not even know it.  If you don’t have the XPS features installed you can get it free from Microsoft or one of the many 3rd party vendors deploying solutions for XPS.

Get an XPS Viewer  XPS Showcase

What is an XPS document?

The XML Paper Specification itself is platform independent, openly published, and available royalty-free and Microsoft has integrated XPS-based technologies into Microsoft Windows Vista operating system and the 2007 Microsoft Office system. Microsoft brings additional document value to its customers, partners, and the computing industry through the XPS-based technologies.

An XPS document is any file that is saved to the XML Paper Specification, or .xps, file format. You can create XPS documents (.xps files) by using any program that you can print from in Windows; however, you can view XPS documents only by using the XPS Viewer, which is included in this version of Windows.

An XML Paper Specification (XPS) document is a document format you can use to view, save, share, digitally sign, and protect your document’s content. An XPS document is like to an electronic sheet of paper: You can’t change the content on a piece of paper after you print it, and you can’t edit the contents of an XPS document after you save it in the XPS format. In this version of Windows, you can create an XPS document in any program you can print from, but you can only view, sign, and set permissions for XPS documents in the XPS Viewer.

XPS FTS in MOSS 2007

The XPS format is great for SharePoint.  Not only for view-ability but for it’s Full Text Search-ability (FTS).  The following is a step-by-step guide to enabling and configuring XPS IFilter support in Windows Server 2008 and MOSS 2007.  Note: I have a single server running all my MOSS farm services.  If I had a distributed farm with my MOSS Index service running on a dedicated server I would enable and configure the XPS feature on the dedicated Index server.

Step-By-Step

1. On the MOSS Index server launch the Server Manager and select Add Features, select the XPS Viewer and click Next.

image

2. Click Install.

image

3. Click Close.

image

4. From the SharePoint 3.0 Central Administration select the Share Service Provider/Search Settings and under Crawling select File types and then select New File Type.

image

5. Enter xps and click on OK.

image

6. You will see the new file type in the list.

image

7. You can also confirm it has been enabled by reviewing the registry setting for the following key.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0 \Search\Applications\<SITE-GUID>\Gather\Portal_Content\Extensions\ExtensionList

image

8. Next you’ll need to enter the following details in the HKLM hive for the XPS ifilter.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Search\Setup\Filters\ .xps]
        Default = (value not set)
        Extension = xps
        FileTypeBucket REG_DWORD = 0x00000001 (1)
        MimeTypes = application/xps

image

9.  In addition, you’ll need to add and set the Class ID for the XPS iFilter in the following HKLM hive location.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Search\Setup\ContentIndexCommon\Filters\Extension\.xps]

             Set the "Default" value to the CLSID of XPS IFilter.

             Default REG _SZ = {1E4CEC13-76BD-4ce2-8372-711CB6F10FD1}

image

image

10.  Next, stop and start the Office SharePoint Server Search service.

C:\>net stop osearch
C:\>net start osearch

image

11. Next, run a full or incremental crawl. If you’re interested, keep an eye on the C:\Users\<search-service-account>\AppData\Local\Temp\gthrsvc folder and you’ll see MOSS crawl writing the images to this folder to index.  This of course is why you need a beefy server for Indexing, lot’s of file IO.

image

12.  Once the crawl is complete you can verify the XPS files have been crawled via the Crawl Log’s URL Summary.

image

Searching

When I search for the keyword “galleries” in MOSS Advanced Search I get hits from the result FTS.

image

 image

 


For More Information

XML Paper Specification: Overview

ECMA International XPS Specification and Reference Guide

ECMA International XPS White Paper

Microsoft MSDN XPS Team BLOG

iFilter, MOSS, Search, SharePoint, Crawl, Windows Server 2008, XPS , , , , , ,

Performance Options for SharePoint IIS

27. June 2009

Here are a few quick tips on kickin' up the IIS performance for SharePoint 2007.

Disk-based Caching for Binary Large Objects

The purpose of the BlobCache is to avoid extra database roundtrips required to pass down these objects when the page loads. Use this setting in the WebApp web.config file.

<BlobCache location="C:\blobCache" path="\.(gif|jpg|png|css|js)$" maxSize="10" max-age="86400" enabled="true" />

  • location: Make sure you have plenty of hard drive for "location".
  • maxSize: The size in GB of the cache location.
  • max-age: Can be >= 0. The default is 86400 seconds (24 hours).

Flush the Cache

Use the stsadmin command to flush all binary large object (BLOB) caches associated with a specified Web application on different Web front-end computers on the farm: stsadm -o setproperty -propertyname blobcacheflushcount -propertyvalue 11 -url http://mywebapp:port

Enable IIS 6.0 Compression for SharePoint

 

REM Turn On Compression

cscript adsutil.vbs set w3svc/filters/compression/parameters/HcDoDynamicCompression true

cscript adsutil.vbs set w3svc/filters/compression/parameters/HcDoStaticCompression true

REM Set Compression to High Level

cscript.exe adsutil.vbs set w3svc/filters/compression/gzip/hcdynamiccompressionlevel "9"

cscript.exe adsutil.vbs set w3svc/filters/compression/deflate/hcdynamiccompressionlevel "9"

REM IIS 6.0 Only

cscript.exe adsutil.vbs set w3svc/filters/compression/gzip/hcscriptfileextensions "css" "js" "asp" "exe" "axd" "aspx"

cscript.exe adsutil.vbs set w3svc/filters/compression/deflate/hcscriptfileextensions "css" "js" "asp" "exe" "axd" "aspx"

 

The compression can be 0 to 10, 10 being the highest.

SharePoint, IIS ,