Nick Grattan's Blog

About Microsoft SharePoint, .NET, Natural Language Processing and Machine Learning

Archive for the ‘SharePoint Administration’ Category

SharePoint Versions – MOSS v. SharePoint Services

with 2 comments

In this post I explained how to determine if your SharePoint installation is service packed, and to what level. However, the situation is a little more complex since your MOSS 2007 farm will be running Microsoft SharePoint Services 3.0 and MOSS on top.

When using Central Administration / Operations / Servers In Farm to report the version number you’re seeing the Windows SharePoint Services 3.0 version number. This will be updated when you run the Windows SharePoint Services (WSS) service pack update.

So how do you find which service pack for MOSS you’re running with? One way is to find the version number of the Microsoft.Office.Server assembly from the Windows GAC (Global Assembly Cache). To do this:

  • Run the Windows Explorer.
  • Navigate to \Windows\Assembly.
  • Right-click the file Microsoft.Office.Server and select Properties.
  • Click the Version tab.
  • Take a note of the “File Version”:

ver1.PNG

Here are the version numbers for the main MOSS services packs using this technique:

Service Pack

WSS Version (Central Admin)

MOSS Version from Microsoft.Office.Server
Unserviced packed 12.0.0.4518 12.0.4518.1014
Service Pack 1 12.0.0.6219 12.0.6211.1000
Service Pack 2 12.0.0.6421 12.0.6420.1000

Version numbers from the Microsoft.Office.Server assembly do not follow exactly those for the WSS reported version number, but there is a close correlation.

Written by Nick Grattan

November 5, 2009 at 7:47 pm

Am I Serviced Packed?

with one comment

You can find the current version number for MOSS 2007 through Central Administration:

  • Run Central Administration.
  • Click the Operations tab.
  • Click Servers in farm under the “Topology and Services” section.

This shows the version number for the farm and each individual server in the farm:

version.PNG

Here are the version numbers for various MOSS 2007 service packs:

Unservice packed 12.0.0.4518
MOSS Service Pack 1 (SP1) 12.0.0.6219
MOSS Service Pack 2 (SP2) 12.0.0.6421

For a full list of version numbers, including interim builds see here.

Update: 5 Nov 2009: See here for how to find MOSS 2007 and Windows SharePoint Services version numbers.

Written by Nick Grattan

September 1, 2009 at 4:08 pm

Content Database – Changing Default Location

leave a comment »

When new databases are created, SharePoint uses the default SQL Server location. This is typically the “C:\Program Files\MS SQL\Data” folder. Many organisations use RAID or SAN storage which may have different locations, e.g. “D:\Database”.

Within SharePoint you don’t have the option of specifying where the data and log files for the databases are created.

Using the instructions in this blog you can change this default location for new databases. For existing database you need to “DETACH” and “ATTACH” the data and log files.

Written by Nick Grattan

September 9, 2008 at 12:03 pm

Storing BLOBs Externally in SharePoint 2007

with 2 comments

Documents in SharePoint Document Libraries are stored in the SQL Server database. In most situations this works well – backing up the SQL Server content database backs up all the documents in a consistent way.

However, for storing Binary Large Objects (BLOBs) may be inefficient and costly. It may be more efficient to store such BLOBs in the file system and then link these files to SharePoint Document Libraries.

This can now be done through the ISPExternalBinaryProvider interface. Prior to SharePoint 2007 SP1 this component was available as a hot fix, but is now included mainstream.

The interface is documented here: http://msdn2.microsoft.com/en-us/library/bb802976.aspx.

Written by Nick Grattan

January 17, 2008 at 12:54 pm

Auditing Permission Changes

with 13 comments

Question: Can you audit permission changes in a site collection?

Answer: This is possible, but by default security changes are not audited. To enable auditing:

  1. Select Site Actions + Site Settings + Modify All Site Settings at the site collection root site.
  2. Click the Site collection audit settings link.
  3. Select the Editing users and permissions option:

Audit1

Once turned on, changes to permissions on sites, lists and items will be audited. To view the audit log:

  1. Click the Audit log reports link on the “Site Settings” page for the site collection.
  2. Click the Security Settings link:

Audit2

This will open the audit log in an Excel spreadsheet. The following example shows a summary showing a single security change resulting from a breaking of permission inheritance:

Audit3

More detailed information is available in the “Report Data” sheet in the Excel workbook.

Written by Nick Grattan

November 27, 2007 at 9:13 pm

SPS 3.0 and MOSS 2007 Single Server Installs

leave a comment »

A single server install of MOSS 2007 will install SQL Server 2005 Express Edition and therefore each content database will be limited to 4GB. Therefore, a site collection (if given its own content database) will be limited to 4GB of content.

A SPS 3.0 single server install does not install SQL Server 2005 Express Edition – instead it installs the Windows Integrated Database (WID), which is also known as SQL Server 2005 Embedded Edition. The instance name is “MICROSOFT##SSEE”, and there are several limitations such as external connections are not permitted.

However, most importantly, WID databases do not have the 4GB limitation, and so practically speaking, the content size for a site collection is unlimited.

The database files are installed into “\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data” which is typically located on drive C. This can cause problems as many servers use another drive for storing data.

The easiest way of moving a content database from the default location to another location is to perform a backup of the web application using Central Administration and then restore to the new location.

Restore

Written by Nick Grattan

November 16, 2007 at 12:13 pm

Blocked file extensions in SharePoint

leave a comment »

SharePoint maintains a list of blocked file types based on the filename extension. The default list is documented here.

You can change this list using Central Administration. Each web application has its own list which will apply to all site collections in the web application.

To maintain the list run Central Administartion and navigate to Operations + Blocked File Types.

Written by Nick Grattan

November 16, 2007 at 10:54 am

Indexing PST files in SharePoint (MOSS) 2007

with 2 comments

SharePoint 2007 does not provide an IFilter for indexing PST files. These files contain email messages and PST files can be generated from Microsoft Exchange using EXMerge.exe or by exporting from Microsoft Outlook.

Here is one technique for indexing the contents of a PST. First, you need to extract messages from the PST into separate MSG files. A tool like Aid4Mail (www.fookes.com) will do this for you. You can then create a content type for indexing the folder in which the MSG files are located.

Written by Nick Grattan

November 3, 2007 at 2:01 pm

Finding IFilters for SharePoint Indexing

with 2 comments

Looking for an IFilter for a particular file type? Take a look at www.ifilter.org as a starting point. This site has links to IFilters for ZIP, RAR, CHM, RTF, StarOffice, OpenOffice and other files types.

* Thanks to Jackie at Kainos for pointing this out to me.

Written by Nick Grattan

October 17, 2007 at 11:07 am

Setting Regional Settings with PowerShell

with 8 comments

This  blog entry describes how to use Microsoft PowerShell with the SharePoint and MOSS 2007 object model. Here is an example script that allows the regional settings for a site to be changed and follows the C# example presented here.

$spsite=[Microsoft.SharePoint.SPSite](“http://localhost:9000“)
$rootWebSite=$spsite.RootWeb
$website=$spsite.OpenWeb($rootWebSite.ID)
$culture=[System.Globalization.CultureInfo]::CreateSpecificCulture(“en-GB”)
$website.Locale=$culture
$website.Update()
$website.Dispose()
$rootWebSite.Dispose()
$spsite.Dispose()

Save the file with a “ps1” extension, e.g. “locale.ps1”. The script can be executed in PowerShell by typing:

 ./Locale.ps1

Note that even if the script file is in the current folder you still need to use the “./” notation to qualify the filename.

Written by Nick Grattan

September 3, 2007 at 11:26 am