Assigning more than 2 site collection administrators

I found this trivial tip on Itay Shakury’s blog and I must admit that I have been asked this question many times too and always have to think twice before I remember how to do it.

So that’s way this is posted here as well [:D]

SharePoint Central Administration’s has a page that allows you to select site collection administrator, you are prompted to specify a site collection administrator, and optionally a secondary administrator.

assign SC admin 

But there is no reason why you won’t have more than tow administrators for a site collection.
Go to the site collection settings page, and click on Site collection administrators. (or open the following page: http://YourSite/_layouts/mngsiteadmin.aspx)


Now add as many users as you wish, separated with semicolons.


MOSS Search for emails and attachments context

found this article on:

Some of our customers requested to have the ability to search context within email messages and within its attachments.

Searching the web for a solution came with results that indicate that a third-party development is needed to achieve this ability…
Then I found Gavin Adams post and Tom Vandaele post that wrote that the ability to deep search within msg files is a MOSS out-of-the-box option that need to be configure.

Followed their instructions I tried to search context in a docx file attachment with in a msg file that was uploaded to a document library. I succeed to get the msg file by searching its context , but failed to get results related to the email’s attachments.

After some tests of my own, I figure out that the registry should look like that:

  1. Make sure that this key exists in the MOSS registry
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Search\Setup\ContentIndexCommon\Filters\Extension\.msg
  2. Add these keys and values to the .msg

The MimeTypes application/msoutlook is the one I use to gain the deep search ability (couldn’t do it using the MimeTypes = application/

How to create a ‘Slipstream’ installation for MOSS with SP1 by Martin Kearn

Ha finally, I found it. Thanks to Martin Kearn I finally found a way to have a single installation source for installing MOSS with SP1 embedded (slipstreamed)

Here is the original article of Martin posted @

In order to install MOSS 2007 on Windows Server 2008 you will need to install ‘MOSS with Service Pack 1’. This is known as a slipstream installation and it contains the original image for MOSS RTM and the MOSS and WSS SP1 files. The problem is that this ‘all in one’ slipstream is not available for download just yet, so you have to create your own slipstream image. Fortunately, this is very easy to do, just follow these steps:

  1. Download MOSS and WSS Service Pack 1 files

You can download the MOSS and WSS SP1 files from here. You will need both service packs for a MOSS installation:



Once downloaded you will have two executable files: Wssv3sp1-kb936988-x86-fullfile-en-us.exe and Officeserver2007sp1-kb936984-x86-fullfile-en-us.exe

  1. Extract the exe’s

You now need to extract the exe’s, to do this enter this command (this assumes you’ve downloaded the exe’s to your c:\, change if not)

C:\Wssv3sp1-kb936988-x86-fullfile-en-us.exe /extract:c:\wsssp1extract

C:\ Officeserver2007sp1-kb936984-x86-fullfile-en-us.exe /extract:c:\mosssp1extract

  1. Add the extracted files to your RTM MOSS installation

Once you’ve extracted the service pack exe’s you need to copy the extracted contents to the /Updates folder on the MOSS CD. The easiest way to do this is take a copy of your MOSS RTM CD (or extract your ISO image) onto your file system and simply copy the contents of both c:\wsssp1extract and c:\mosssp1extract into the \Updates folder.

You’re done; you will now be able to install MOSS as usual on your Windows Server 2008 machine. If you need a guide for doing this, check out my other post here: . This guide was written for Windows Server 2003 so there may be some minor variations.  

Beware of the Default Logging in MOSS if you like your diskspace


By default, SharePoint trace logging is enabled and the log files are stored at: C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\LOGS on your front-end web server. Without changing the verbosity of logging via event throttling settings, or the number of minutes before creating a new log file, each log file is around 50 Meg! By default, SharePoint keeps 96 of these files, spanning 2 days for a grand total of around 4.8 Gig.

Here are the default log settings on the diagnostic logging operations page:


In our case, we want to keep the current verbosity level and expand the length of time that we retain the logs to 3 days, but we want to store the logs on a different disk. All we have to do is change the path in the Trace Log section of this maintenance page and increase the number of log files to 144.

NOTE on PSCDiagnostics files: You may notice log files whose names start with “PSCDiagnostics”. These files are post-setup configuration files. Each time that you open SharePoint’s central administration page, a new PSCDiagnostics file is created. These files are always stored in the same directory as the trace logs. So, if you change the trace log location, these logs will follow.

You also have a very fine degree of control over the types of events to log. The following is a comprehensive list of event types:


For each event, you can set the least critical event to report to the event log:


and you can report the least critical event to report to the trace log:


You must press OK at the bottom of the maintenance page for each modification to the throttling settings. This works well enough if you are making a modest number of changes to these levels. However, if you are making more pervasive changes or you wish to make changes to hidden event categories, then the stsadm.exe command line utility is your better option.

Here is the command line syntax for showing hidden event categories:

stsadm.exe –o listlogginglevels -showhidden

Here is the command line syntax for changing logging levels as detailed in Jose Baretto’s blog. Here is a link to the entire post:

stsadm -o setlogginglevel [-category < [CategoryName | Manager:CategoryName [;…]] >] {-default | -tracelevel  < None;  Unexpected; Monitorable; High; Medium; Verbose> [-windowslogginglevel < None;  ErrorServiceUnavailable;  ErrorSecurityBreach;  ErrorCritical;  Error;  Warning;  FailureAudit; SuccessAudit;  Information;  Success>] }

MOSS Planning worksheets provided by Microsoft

Hi all,

I was scouting the internet for documents regarding planning for MOSS when I stumbled upon a collection of planning worksheets on Technet. These worksheets help you though a lot of aspects in planning. There are about 40 or so worksheets listed on

Just wanted to post this link. You never knwo when you need something like them, right ? [H]

How to change the Alert Email notification message for Announcements

Yes, you all know the kind of messages I mean. I was asked yesterday if there was a way to remove some data from those announcement messages that are sent out when you have enabled alerting on a announcement list. It turns out that you can change this for about any alert in MOSS/WSS

The typical announcement message looks something like this:

Test Site

Test Item has been added

Modify my alert settings


View Test Item.


View Announcements

Title: Test Item   
Body: Test Body Text   
Expires: 18/01/2008   
Last Modified 7/01/2008 14:51 by System Account

Well, one of our users wanted us to remove the Title, Body and Expires Field from the mail message.

So I did a little research and found out that the place to make this change is the alerttemplates.xml file.

I was guided somewhere to the following document on the net (I attached the document to this post)

Another source I used is:

Anyway in short I ended up changing the following lines in the xml file in the <AlertTemplate Type=”List Name=”SPAlertTemplateType.Announcements> section:


<Properties>       <ImmediateNotificationExcludedFields>ID;Author;Editor;Modified_x0020_By;Created_x0020_By;_UIVersionString;ContentType;TaskGroup;IsCurrent;Attachments;NumComments;</ImmediateNotificationExcludedFields>  <DigestNotificationExcludedFields>ID;Author;Editor;Modified_x0020_By;Created_x0020_By;_UIVersionString;ContentType;TaskGroup;IsCurrent;Attachments;NumComments;</DigestNotificationExcludedFields> </Properties>


<ImmediateNotificationExcludedFields>ID;Title;Body;Expires;Author;Editor;Modified_x0020_By;Created_x0020_By;_UIVersionString;ContentType;TaskGroup;IsCurrent;Attachments;NumComments;</ImmediateNotificationExcludedFields> <DigestNotificationExcludedFields>ID;Title;Body;Expires;Author;Editor;Modified_x0020_By;Created_x0020_By;_UIVersionString;ContentType;TaskGroup;IsCurrent;Attachments;NumComments;</DigestNotificationExcludedFields> 

this tells SharePoint to longer show the fields Title, Body and Expires in the alert

Once edited and saved, you need to enable this as follows:

  1. copy the modifed xml into the C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\xml of every FrontEnd server in your farm

  2. execute command stsadm -o updatealerttemplates -filename <your modified xml file> -url <your site>

  3. execute iisreset on every Frontend

  4. restart the Windows Sharepoint Services Timer service 


Of course, if you are looking for changing some other type of alert besides Announcements, you need to make the necessary changes in the corresponding section of the xml file. The available sections are:

Alert Template Name



The first alert template in Alerttemplates.xml. GenericList is used unless there is a match to one of other event types.


Notification of changes in document libraries


Notification of changes in surveys


Notification of changes in links


Notification of changes in announcements


Notification of changes in contacts


Notification of changes in events


Notification of changes in tasks


Notification of changes in discussion boards


Notification of changes in picture libraries


Notification of changes in XML form


Notification of changes in data connection libraries


Assigned to task / issue list notifications


Are your alerts not sending email? Use these stsadm commands to verify your alert settings.

I recently had a colleague asking me to troubleshoot some workflows. Apparently the workflow should send emails, but nothing was coming thru.

As part of my troubleshooting I came across 2 stsadm commands that may help you identify an issue with your alerts.

Although these commands did not help me solve the issue (a reboot of the Frontend did [:D] ), I found these commands worth writing down in a post:

First command:

stsadm.exe -o getproperty -url <http://problemsite> -pn alerts-enabled
this command should return: <Property Exist=”Yes” Value=”yes” /> which means that alerts are good on the site

Second Command:

stsadm.exe -o getproperty -url <<http://ProblemSite>> -pn job-immediate-alerts.
this command shoud return: <Property Exist=”Yes” Value=”every 5 minutes between 0 and 59″ />

What else can you do to troubleshoot?

Open the MOSS Central Administration page, click Operations–Timer Job Status,

make sure the following two jobs are showing “success” and 100%
Change Log
Immediate Alerts


User Comments and Ratings web parts are now Free!

hi all,

I have been playing around with this small collection of webparts in its beta phase, but was not quite ready to install this on my production servers because I didn’t know what it would eventually cost. It’s always tricky to give your users some cool webparts when you know that when you have to start to pay for it, you will probably be asked by your boss to remove them from your servers.

Great was my surprise to see that the creators of these webparts have made them available for FREE!

So, if you can, download and install these webparts.

You can learn all about them on the following site:

direct download link:

Installation is really easy.  Download the package, unzip, and run the install.cmd file.  You’ll be prompted for the URL to your SharePoint 2007 site.  Once installed, two web parts are added to SharePoint’s web part gallery.