SharePoint Manageability Toolkit Updated

I received word over the weekend Solution Accelerators have updated the SharePoint Manageability Toolkit.  See below for a complete list of updates:

  1. Linked Reports are added specific to the MOSS and WSS Management Pack. They consists of performance reports, alerts reports, event analysis reports, Most common alerts and Most common Events reports with respect to the target objects of our Mp such as MOSS computer Group, WSS Computer Group, MOSS computer role/ Moss Server and WSS computer Role/ WSS server.

  2. Alert suppression is implemented in all event based rules in both the MOSS & WSS Packs based on Event ID, Event Source, Event Description and Logged computer(by Agent name).

  3. In Both Packs views such as alerts view, event view, performance view, state view and task status view are all scoped precisely to the target objects of our Mp such as MOSS computer Group, WSS Computer Group, MOSS computer role/ Moss Server and WSS computer Role/ WSS server. This actually reduced the noise much better and considerably improves the performance of the MP views. Gives More accurate results to the user.

  4. KB articles for Performance rules were added to both the Packs.

  5. All the rules in both the packs have Rule description.

  6. Service Monitors in both the MOSS and WSS Packs are fine tuned to match the alert and health state of the service. Hence they match the health state more precisely.

  7. MP folder names are corrected to have same naming convention.

To download the SharePoint Manageability Toolkit Beta 1 Refresh browse to Microsoft Connect, and login with your Windows Live ID.

Daylight Savings Time Change Approaching

As Daylight Savings Time (DST) approaches it is time again to plan and prepare for impacts on your existing SharePoint Products and Technologies deployments…I intend to keep this post dynamic and updated with the latest information surrounding DST impact and mitigation for Windows SharePoint Services 3.0 and Microsoft Office SharePoint Server 2007.

Planning and Preparation

A technical product review/ summary webcast is scheduled for 2:00PM Pacific on Monday, September 24th to help customers and partners prepare for change to Daylight Saving Time and various time zones.  Information about this Webcast for customers is available at:   

Windows SharePoint Services 3.0

KB941422 (includes a software update for daylight saving time (DST)) is recommended to address the impact of DST on Windows SharePoint Services 3.0 for more information visit

Microsoft Office SharePoint Server 2007


Profiles and Properties – Questions and Answers

A e-mail dialogue came up with a colleague surrounding Profiles and Properties in Microsoft Office SharePoint Server 2007, with the questions specific to profile cleanup and management of changes in profile properties.

  1. How are inactive user profiles managed…

  2. How do I manage Active Directory property changes in Microsoft Office SharePoint Server 2007’s profile database…

After I sent my reply, I realized this was not the first time the question arrived in my inbox so I’ve decided to include the explanations here:

Profile Cleanup

User profiles are checked against the Active Directory to determine whether or not there is a matching Active Directory object. If a matching object exists, the bDeleted flag is removed or set if a matching object does not exist during an incremental import. Management of these objects where a match could not be determined is handled through the native MySite Cleanup Job through either deleting the MySite collection for the unmatched object or assigning permission to the user’s manager and generating an e-mail notification.

Handling Active Directory Changes

Common occurrences in most organizations are changes in a user’s Active Directory properties, for example, a name change as the result of marriage or some other event. The user may report that when uploading documents, updating list items, etc. their name is incorrect; however, their SharePoint profile references the correct information. To resolve such occurrences, delete the user profile from the Shared Service Provider an execute a profile import to introduce a “clean” data set into the SSP or optionally run STSADM –o migrateuser to migrate the user data properly, edit some property on the profile to trigger the synchronization job.

Deploying ProClarity Viewer 6.3 for SharePoint

I was recently asked to deploy the ProClarity Viewer 6.3 for SharePoint Web Part – after downloading the package I realized that it was not offered in a deployable package, but rather a compressed archive of the .dwp, assembly, and resource files.  The challenge became offering a user experience similar to the previous ProClarity Viewer version so I decided to package the Web Part into a reusable solution.  For those interested or looking to create a deployable Web Part package I’ve documented the steps below:

Step 1 Create a Manifest

The Manifest file is a required configuration file that describes the contents and overall structure of the cabinet file.  STSADM will use the Manifest file to deploy the contents of the cabinet file when executing the addwppack operation.

    <Assembly FileName=”SPSPageViewer.dll“>
        <SafeControl Assembly=”SPSPageViewer, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35″ Namespace=”SPSPageViewer” TypeName=”*” Safe=”True” />
        <ClassResource FileName=”images/Book.gif“/>
        <ClassResource FileName=”images/Folder.gif“/>
        <ClassResource FileName=”images/Library.gif“/>
        <ClassResource FileName=”images/Page.gif“/>
        <ClassResource FileName=”images/TPMax2.gif“/>
        <ClassResource FileName=”images/TPMin2.gif“/>
        <ClassResource FileName=”images/Unknown.gif“/>
        <ClassResource FileName=”images/up.gif“/>
    <DwpFile FileName=”PasPageViewer.dwp“/>

The <Assemblies> node contains the overall definitions for each of the assemblies being deployed, the child <Assembly> node uses the FileName attribute to define the assembly file name, in this case SPSPageViewer.dll, and contains the definitions for the class resources in addition to the XML for the SafeControls list.  The XML for the SafeControls list can be found in the ProClarity Viewer Web Part Setup Guide or optionally copied from the example above.  This information will be written to the web.config for the Web application(s) when the solution is deployed to the SharePoint Products and Technologies server farm using the SharePoint administration tool (STSADM).

The <ClassResources> node contains the base definitions for each class resource that will be deployed, the child <ClassResource> node uses the FileName attribute to define the class resource file name, in this case each of the images accompanying the Web Part are defined in a <ClassResource> node with their path relative to wpresources at a global or localized level.

The <DwpFiles> node contains the definitions for each .dwp file being deployed, the child node <DwpFile> uses the FileName attribute to define the file name of the .dwp file, in this case the .dwp file name accompanying the downloaded Web Part archive is PasPageViewer.dwp.

The complete Manifest file should appear as follows:

<?xml version=”1.0″?>
<WebPartManifest xmlns=””>
    <Assembly FileName=”SPSPageViewer.dll”>
        <SafeControl Namespace=”SPSPageViewer” TypeName=”*” />
        <ClassResource FileName=”images/Book.gif”/>
        <ClassResource FileName=”images/Folder.gif”/>
        <ClassResource FileName=”images/Library.gif”/>
        <ClassResource FileName=”images/Page.gif”/>
        <ClassResource FileName=”images/TPMax2.gif”/>
        <ClassResource FileName=”images/TPMin2.gif”/>
        <ClassResource FileName=”images/Unknown.gif”/>
        <ClassResource FileName=”images/up.gif”/>
    <DwpFile FileName=”PasPageViewer.dwp”/>

Step 2 Create a MakeCab Directives File

The MakeCab directives file controls how files are compresses in a cabinet.

Create a logical file structure by copying Book.gif, Library.gif, Page.gif, TPMax.gif, TPMin.gif, Unknown.gif, and up.gif to /images.  *You will need to create the images directory in your cabinet directory.  The directives file is also used to define the name of the cabinet file.

.set DiskDirectoryTemplate=CDROM
.Set CompressionType=MSZIP
.Set UniqueFiles=’ON’
.Set Cabinet=on
.Set DiskDirectory1=.
“C:ProClarity63imagesBook.gif”    “imagesBook.gif”
“C:ProClarity63imagesFolder.gif”    “imagesFolder.gif”
“C:ProClarity63imagesLibrary.gif”    “imagesLibrary.gif”
“C:ProClarity63imagesPage.gif”    “imagesPage.gif”
“C:ProClarity63imagesTPMax2.gif”    “imagesTPMax2.gif”
“C:ProClarity63imagesTPMin2.gif”    “imagesTPMin2.gif”
“C:ProClarity63imagesUnknown.gif”    “imagesUnknown.gif”
“C:ProClarity63imagesup.gif”        “imagesup.gif”
“C:ProClarity63PasPageViewer.dwp”     “PasPageViewer.dwp”
“C:ProClarity63SPSPageViewer.dll”    “SPSPageViewer.dll”
“C:ProClarity63Manifest.xml”        “Manifest.xml”
;*** <the end>

Step 3 Create the Cabinet

To create the cabinet file execute MakeCab.exe /F <filename>.ddf where <filename> is the name of your directives file.  The cabinet file when a source destination is not specified is commonly created under C:Documents and Settings<user>.

Step 4 Deployment

To deploy the Web Part package, copy <cabinet>.cab to a location on one Web front-end server.

Execute STSADM -o addwppack -filename <cabinet>.cab [-globallinstall].

Step 5 Verify Deployment

The Web Part package will be listed in the list of available/deployed solutions to the SharePoint Products and Technologies server farm under SharePoint 3.0 Central Administration | Operations | Solutions Management (see image).


To review deployment details, retract, or remove the solution click <cabinet>.cab (see image).


Step 6 Add the ProClarity Viewer to a Page

To add the ProClarity Viewer Web Part to a page, navigate to a site collection and select Site Actions | Edit Page.

Select a Web Part zone and click Add Web Part.

Select ProClarity Viewer from the list of available Web Parts and click Add.

Tafiti + Halo 3 = Search Goodness

I was just looking at the new Halo 3 skin recently applied to Tafiti and was very impressed. For those who’ve never heard of or much less used Tafiti. Tafiti is an experimental Microsoft search front-end designed primarily for research projects spanning multiple queries and sessions through a variety of visualization, storage, and collaboration/sharing presentation and management layers. Tafiti uses a combination of Live Search and Silverlight to both power and render results. For example a recent query I performed on my Volkswagen Passat is provided initially in a flat structured result set (, but it really gets interesting when presented in Tree View. Using the flat view you dynamically filter results by syndication, news, images, etc.

For a complete Tafiti functionality walk through visit or to being your search.