Microknowledge

Server Virtualization for the SharePoint/.NET Developer

Virtualization is often thought to be an infrastructure topic,  Recently, my colleague Liz Hatch and I presented a virtualization walkthrough to the Boston .NET User Group.  At KMA, virtualization provides us with the essential scale to support relatively dense server volumes with a comparatively small physical footprint.  We work principally on the Microsoft Virtual Server/Hyper-V platform, although most of the basic concepts are valid in VMware,  Xen, or other virtualization hosts.

At KMA, virtualization allows us to support multiple operational needs:

· Multiple Software development systems

· Testing environments that replicate an entire ecosystem, including login servers, database, web, mail, and clients

· Demonstrations and proof-of-concept environment

In a virtualized environment, a single server can simultaneously support one or multiple guest systems.

In Hyper-V, each guest OS hard disk is maintained on the host as a .VHD file.  As a result, its easy to snapshot, copy and rollback a server before or after deplying test software or running an new build.

IN addition to running Windows, there’s another possible approach.  Hypervisors provide the essential support for server hardware to support multiple guest operating systems, but without a host operating system.  Hypervisors make the most efficient possible use of the server hardware, since they don’t need to support a multiuser GUI, desktop applications, etc.  However, we’ve found the comparative ease of use of Windows 2008 R2 makes allowing our developers to self-support their own development environments. 

In large enterprise environments, production systems operate under stringent control to support high availability.  However, this can mean that lower availability is thought to be OK for test or development regions.   Hyper-V makes it easy for a developer to maintain, apply, and rollback their own virtualized images without relying on an overextended (or nonexistent) infrastructure support team.  For developers, the “dev region” IS production.

In our virtualization design, we emphasize centrally hosted virtual servers as opposed to Windows 7-hosted Virtual PCs.  The ubiquity of high speed Net connections, along with multiple VPN connections make accessing our central server core from the office, home, client site, or mobile location seamless.  (For those few locations without remote connectivity, we make light use of local Virtual PC hosts for self contained demonstrations.)  Central servers provide better security, backup, power, memory usage, and performance.

In addition, multi-instance applications like Microsoft Office SharePoint Server 2007 (MOSS) or SQL Server 2005/2008 allow us to achieve even greater server density on each single server.

In a departure from past practice, we no longer name guest servers to designate their host OS.  (I had once used designators like VDEVSQL08-H03 to show that the server was hosted on “H03”.)  But guest OS are no longer tied to a single host.  Modern virtual machine management, like VMware vMotion System Center Virtual Machine Manager, make it easier than ever to switch a running guest OS to a new host on the fly, with no down time.  As a result, hard coding the host name into the guest system name is no longer relevant.

Even with greater server density, multiple guests systems can rapidly consume more RAM than the host system supplies.  Developers need to designate always-on vs. on demand systems, and work cooperatively to temporarily shut down or suspend unused systems.

I’ll have more on virtualization tips and tricks in a future post.  Until then, thanks for reading.

Eight things to look for in SharePoint 2010

I am eagerly awaiting my first hands on experience with the new SharePoint 2010 servers next week at Microsoft's Ignite sessions in Atlanta.  Before I finally see the system myself, I thought I’d note a few things, off the top of my head, that I’m hoping to find in the new product.

· Two way data exchange via the Business Data Catalog

· Richer end user form design for SharePoint lists, and support for a relational data model, child grids, etc., without InfoPath

· Better tools for bundling and applying changes to existing objects that have already been deployed to production.

· Simpler debugging for web parts, especially ASP.NET

· In line editing of page content

· Better Web 2.0 style social networking for the enterprise -- especially adding micro blogs, or status-presence indicators at the team and individual levels.  This means more Facebook/Twitter type updates – which foster essential social cohesion among dispersed collaborative teams.

· Real blog editing with better permalinking URLs for external sites and in line editing.    (I’d be using SharePoint for this blog if it were better at those two things!)

· Silverlight based native support for streaming media, especially video.

I have a few wish list items for Project Server 2010 as well that I’ll post another time -- but a better security model that doesn’t split administrative tasks between WSS and Project Server would be one.

I promise to share my news as soon as the NDA period is over.  Until then, thanks for reading.

SharePoint Centralized custom master pages and navigation - Part IV: Setup and Installation

Today, we'll wrapup our walkthrough of Sharepoint customization and deployment.  We're going to cover automated installation of packaged SharePoint WSP files.  We've already covered the topics below on master pages, features, and packaging:

· [Part I] Master page customization to add centralized navigation support to the master page (as well as some other changes to enable Ajax for a related project).  The navigation was based on Marian Dumitrascu’s article at http://www.codeproject.com/KB/sharepoint/SharedNavigationProvider.aspx

· [Part II] Centralized publishing of common master pages, using Heather Solomon’s techniques outlined at http://heathersolomon.com/blog/articles/servermstpageforsitecollect_feature.aspx

· [Part III] Packaging of the feature as a WSP file, using the WSPBuilder application from Codeplex (http://www.codeplex.com/wspbuilder)

· [Part IV] Automated installation of the solution package, using the SharePoint Installer from Codeplex (again!) at http://www.codeplex.com/sharepointinstaller

Deployment

If you don’t want to use command line tools to deploy your file, you can use the handy Sharepoint deployment utility (also from Codeplex!) at http://www.codeplex.com/sharepointinstaller/  to create a setup ZIP file with your wsp file.  The installer is relatively straightforward.  Extract the contents to a new folder, and then revise those contents as needed.  Here are the changes you need to make inside the sample file:

· Remove the sample wsp

· Adjust the text of the EULA as appropriate.

· Edit setup.exe.xml to change the following values:

o   FeatureID – use the GUID generated above for the feature.  It needs to match the value in feature.xml.

o   SolutionID – this is the GUID in the solutionid.txt file from the WSPBuilder project

o   SolutionFile – the full name of your WSP

o   Solution Title – As appropriate

o   Solution Version – Incrementing this number is a good practice on successive deployments.  It will help your server decide how to handle a reinstallation for a higher version – should it be an upgrade or a repair.

o   Logo Image – Optional.  You’ll need to add the file and adjust the size to get it to fit.  60X35 has been a good size for me.

o   FeatureScope = Site

That’s it!  Zip up those files into a new Zip file and you’re done.  Users can then take that zip file and install the solution on the farm just be extracting the contents and clicking setup.exe.

One last note – how do you test the deploy if you’ve been working on a server that already has the solution installed?  You’ll need to clean out the old files:

· Make a backup copy of the current feature folder I the 12 hive

· Deactivate the feature from any site collections where it was tested

· Use stsadm –o uninstallfeatuure –name CustomMasterPages to uninstall the feature

· IISReset

· You may still have orphaned copies of the master page in the site collection gallery.  It’s usually impossible to delete them directly, but, there’s a trick that usually works/

o   Using SharePoint Designer, navigate to the _catalogs\MasterPage gallery.

o   Create a temporary folder

o   Move the custom master pages to the folder

o   Delete the folder

· Remove the custom feature folder

Now you can use the installer to deploy your new master page feature to the Sharepoint farm.

Once the feature is installed, any changes you make to the deployed master pages in the 12 hive will be immediately reflected in all sites where the feature is activated and the pages are used.   You could also repackage and redeploy the new files.

Hope this was a good exercise for you.  Remember the steps:

· Customize the master pages to support centralized navigation

· Use a feature to publish a central set of master pages

· Package the feature as a WSP file

· Automate the installer to use setup.exe

Good luck, and please let me know if you have any questions!

SharePoint Centralized Custom Master Pages and Navigation - Part III: WSP Packaging

We're continuing our series on SharePoint customization to focus on packaging our new feature for ease of deployment.  Parts I and II have already covered master page customization and feature creation.  Today we'll show you how to use Visual Studio to generate a WSP solution for your Sharepoint feature.

· [Part I] Master page customization to add centralized navigation, based on Marian Dumitrascu’s article at http://www.codeproject.com/KB/sharepoint/SharedNavigationProvider.aspx

· [Part II] Centralized publishing of common master pages, using Heather Solomon’s techniques outlined at http://heathersolomon.com/blog/articles/servermstpageforsitecollect_feature.aspx

· [Part III] Packaging of the feature as a WSP file, using the WSPBuilder application from Codeplex (http://www.codeplex.com/wspbuilder)

· [Part IV] Automated installation of the solution package, using the SharePoint Installer from Codeplex (again!) at http://www.codeplex.com/sharepointinstaller

Packaging

At this point, we're almost done.  However, there are two additional steps to package this as a complete deployment – packaging and installation.

For packaging, we’ll use the fine WSPBuilder tool to package the feature as a wsp file.  WSPBuilder can be downloaded from Codeplex at http://www.codeplex.com/wspbuilder.  It installs as a project template into Visual Studio 2008.

Now that our feature is ready, start a new project in Visual Studio as a Visual C# / WSPBuilder project.  You’ll see that the template generates a new solutionid.txt GUID for you automatically.  This is different from the feature GUID above.  We’ll use both in the final step.

You’ll  also see the 12 folder has already been created for you.  You will need to create the hierarchy of templates \ features \ [featurename], and under that the en-us and masterpages folders.  (There's no need to create the empty folders such as PageLayouts.)

Now, use the right mouse  Add | Existing Item… context menu to copy the feature.xml and provisionedfiles.xml to the FeatureName folder of your project.  Next, import the master page to the masterpages folder, and the preview image (if you used one) to en-us.  Last, use the Tools | WSPBuilder | Build WSP menu item to create your package.  (By default, your WSP file will be in the root folder of the solution.)

 

Project Server 2010 Previews Now Available

This week, Microsoft unveiled Project Server 2010 at thier Project Conference in Arizona.  At the same time, they released preview FIrst Look demo videos online at http://www.microsoft.com/project/2010/en/us/default.aspx

Project Server 2010 shares many of the same interface elements as Sharepoint 2010, so its a good preview of what to expect on the SharePoint side.  Some major highlights:

• Web based editing. Most projects can be edited directly online, and inline without using MS Project. Project Server gets rids of the older ActiveX controls in favor of new broswer scripoting tools. In addition, functions from Project Professional or form elsehwere in the system are surfaced in the ribbon.  Overall, a cleaner and smoother look and feel.
• Integrated portfolio management and demand management (from Portfolio Server). Supports capturing essential data to approve a project at the outset, using easily customized templates. It also lets you optmize the portfolio based on available funds, business deviers, resource constraints, and what-if scenarios.
• Report Center allows for the simple creation and integration of enterprise dashboards and gauges using Excel Services, the new Sharepoint Reporting system, and SQL Reporting Services.

SharePoint Centralized Custom Master Pages and Navigation - Part II: Publishing the feature

Today we're going to continue our walk through a practical integration and deployment exercise.    This began as a project to add centralized global navigation schemes to a custom SharePoint master page.  We're going to extend that today to use publishing features to share the master page itself across multiple site collections.  Each of these is covered in a separate post:

· [Part I] In the first post, we introduced master page customization to add centralized navigation support to the master page

· [Part II] Centralized publishing of common master pages, using Heather Solomon’s techniques outlined at http://heathersolomon.com/blog/articles/servermstpageforsitecollect_feature.aspx

· [Part III] Packaging of the feature as a WSP file, using the WSPBuilder application from Codeplex (http://www.codeplex.com/wspbuilder)

· [Part IV] Automated installation of the solution package, using the SharePoint Installer from Codeplex (again!) at http://www.codeplex.com/sharepointinstaller

Defining Common Master Pages

This technique in this section is adapted from, and indebted to, Heather Solomon’s excellent article on the topic at http://heathersolomon.com/blog/articles/servermstpageforsitecollect_feature.aspx

1.  In your server’s “12 Hive” (usually c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12) go to the Features directory inside the TEMPLATE folder.    Copy the PublishingLayouts folder to a new folder in the root of Features.  The folder name will become the name for your new feature.  Here, we’re using CustomMasterPages.

2.  Open the new folder, and clean out all subfolders, leaving only Feature.xml and ProvisionedFiles.xml. To create a clean file set, at a minimum clear out the contents of each sub folder in the directory (en-us

3. Copy/paste content from original master pages to new pages outside the database [Notepad].  See above for typical edits.

4. Edit the ProvisionedFiles.xml file in Notepad.  We are going to delete most of the content and keep only the OSGMasterPages Module tag and the PublishingLayoutsPreviewImages Module tag.  [See text below.]  We use one node for each master page file (this solution has three master pages.)

<!-- _lcid="1033" _version="12.0.6301" _dal="1" -->

<!-- _LocalBinding -->

<Elements xmlns="http://schemas.microsoft.com/sharepoint/">

    <Module Name="OSGMasterPages" Url="_catalogs/masterpage" Path="MasterPages" RootWebOnly="TRUE">

    <File Url="001.master" Type="GhostableInLibrary">

    <Property Name="ContentType" Value="Title 001" />

    <Property Name="PublishingPreviewImage" Value="~SiteCollection/_catalogs/masterpage/$Resources:core,Culture;/Preview Images/0016.gif, ~SiteCollection/_catalogs/masterpage/$Resources:core,Culture;/Preview Images/0016.gif" />

    <Property Name="MasterPageDescription" Value="Description 001" />

    </File>

    <File Url="002.master" Type="GhostableInLibrary">

    <Property Name="ContentType" Value="Title 002" />

    <Property Name="PublishingPreviewImage" Value="~SiteCollection/_catalogs/masterpage/$Resources:core,Culture;/Preview Images/0016.gif, ~SiteCollection/_catalogs/masterpage/$Resources:core,Culture;/Preview Images/0016.gif" />

    <Property Name="MasterPageDescription" Value="Description 002" />

    </File>

    <File Url="003.master" Type="GhostableInLibrary">

    <Property Name="ContentType" Value="Title 003" />

    <Property Name="PublishingPreviewImage" Value="~SiteCollection/_catalogs/masterpage/$Resources:core,Culture;/Preview Images/0016.gif, ~SiteCollection/_catalogs/masterpage/$Resources:core,Culture;/Preview Images/0016.gif" />

    <Property Name="MasterPageDescription" Value="Description 003" />

    </File>

    </Module>

    <Module Name="PublishingLayoutsPreviewImages" Url="_catalogs/masterpage" IncludeFolders="??-??*" Path="" RootWebOnly="TRUE">

    <File Url="0016.gif" Name="Preview Images/0016.gif" Type="GhostableInLibrary">

    </File>

    </Module>

</Elements>

9.Create a preview image in the language folder (in this case, en-us).  Local Drive:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES\CustomMasterPages\en-us.  As you can see above, we are using a file named 0016.gif.

Next, open Feature.xml file in Notepad. 

· Change the Feature ID to a unique GUID.  You can generate GUIDs in Visual Studio, (Tools - Create GUID - Registry Format - Copy).   If you don’t have Visual Studio, get it!  In the meantime, you can also use a neat online site to get a new one at http://www.guidgen.com.   Paste the new GUID into the Feature ID node (don’t keep any brackets).

<Feature Id="FDFCD4C4-F0D9-43b5-8739-A33681049657"

· Update the title:  Title="Custom Master Pages"

· Update the description: Description="Custom master pages for use across multiple site collections."

· Change the Hidden state to False: Hidden="False"

Save the Feature.xml file.   You should wind up with something like this.

<!-- _lcid="1033" _version="12.0.4518" _dal="1" -->
<!-- _LocalBinding -->
<Feature  Id="1e5ad034-4b11-4dcc-9e73-0208740d45a5"
  Title="Custom Master Pages"
  Description="Custom master pages from XXXXX to use in multiple site collections"
  Version="12.0.0.1"
  Scope="Site"
  Hidden="FALSE"
  DefaultResourceFile="core"
  xmlns="http://schemas.microsoft.com/sharepoint/">
    <ElementManifests>
    <ElementManifest Location="ProvisionedFiles.xml"/>
    </ElementManifests>
</Feature>

At this point, we could use stsadm -o installfeature -name YourFeatureDirectoryName to install the feature, and then activate and test it.  But we’re going to go further and package the solution for automated installation.

Page Not Found Error

If you get any odd “file not found” or “page not found” errors, you may have used SharePoint Designer (SPD) to modify the master pages.  SPD may change the code automatically to remove the tilde and leading slash from some of the console registrations in your master page.

Original:

<%@ Register TagPrefix="wssuc" TagName="DesignModeConsole" src="~/_controltemplates/DesignModeConsole.ascx" %> 

SPD Alterations: 

<%@ Register TagPrefix="wssuc" TagName="DesignModeConsole" src="_controltemplates/DesignModeConsole.ascx" %>

To avoid this, don’t  open master pages for final editing using Sharepoint Designer.  Use Notepad  or similar tools to work on the file outside the content database.

SharePoint Centralized custom master pages and navigation - Part I: Master Pages

There are a lot of academic Sharepoint exercises that cover the elements of this project, but today we're going to walk through a practical integration and deployment exercise.    This is a great real example of WHY you’d want to centralize master pages definitions in the first place.

One of our clients wanted to start breaking their burgeoning site hierarchy into a set of separate site collections and contents databases largely to keep their database sizes reasonable.  However, their site is highly branded, so they wanted to minimize the extra admin work of synchronizing Sharepoint master pages among multiple collections.  In addition, they had several changes they wanted to make to their master pages to enable Ajax-based controls on their sites.   They also wanted to have all the sites point to one primary site collection to define global navigation, so that changes made there would also replicate without further administration.

For this project, we had already installed the binaries for the third party Ajax control and a custom theme for the site.  Also, the Publishing infrastructure is required on all sites where this is deployed, so MOSS is a requirement.

As a result, this project became an integration and customization drawing upon several significant online code sources,  We're going to cover each of these in a separate post:

· [Part I] Master page customization to add centralized navigation support to the master page. The navigation was based on Marian Dumitrascu’s article at http://www.codeproject.com/KB/sharepoint/SharedNavigationProvider.aspx

· [Part II] Centralized publishing of common master pages, using Heather Solomon’s techniques from http://heathersolomon.com/blog/articles/servermstpageforsitecollect_feature.aspx

· [Part III] Packaging of the feature as a WSP file, using the WSPBuilder application from Codeplex (http://www.codeplex.com/wspbuilder)

· [Part IV] Automated installation of the solution package, using the SharePoint Installer from Codeplex (again!) at http://www.codeplex.com/sharepointinstaller

Master Page Customization and Centralized Navigation:

Please visit http://www.codeproject.com/KB/sharepoint/SharedNavigationProvider.aspx for a comprehensive discussion of the centralized navigation. 

Essentially, that article provides a DLL that you add to the Global Assembly Cache on all your servers.   Once the DLL is installed, you will add a section to web.config to define a new SiteMap provider:

<add name="SharedNavigationProvider"  SourceSite="http://[sourcesite]" NavigationType="Global" EncodeOutput="true" type="DataQ.SharePoint.Providers.SharedNavigationProvider,    SharedNavigationProvider, Version=1.0.0.0,  Culture=neutral, PublicKeyToken=fc448b9e121af773" />

Then you add will update your current master page(s) to add a control to point to the new navigation data source.   We strongly recommend copying the content of your base master pages to a new file that lives, for the moment, outside the SharePoint site.  Using SharePoint Designer to make these edits can have unintended consequences, so we’ll use notepad for now.  [More below!]

Underneath the TopNavigationDataSource control, add this control noted below.  TIP: don’t just replace the existing navigation data source.  It needs to “live” inside the Template_Control node, and the new source needs to be outside.  Lastly, you’ll update the ASPMenu navigation to point to the ID of the new data source, here “topSiteMap2”.  [There are other changes that may be required for DisplayValues, etc. – please see Marian’s article for more details.

<asp:ContentPlaceHolder id="PlaceHolderHorizontalNav" runat="server">

   <SharePoint:AspMenu

     ID="TopNavigationMenu"

     Runat="server"

     DataSourceID="topSiteMap2"

     EnableViewState="false"

     AccessKey="<%$Resources:wss,navigation_accesskey%>"

     Orientation="Horizontal"

     StaticDisplayLevels="1"

     MaximumDynamicDisplayLevels="1"

     DynamicHorizontalOffset="0"

     StaticPopoutImageUrl="/_layouts/images/menudark.gif"

     StaticPopoutImageTextFormatString=""

     DynamicHoverStyle-BackColor="#CBE3F0"

     SkipLinkText=""

     StaticSubMenuIndent="0"

     CssClass="ms-topNavContainer">

  <StaticMenuStyle/>

  <StaticMenuItemStyle CssClass="ms-topnav" ItemSpacing="0px"/>

  <StaticSelectedStyle CssClass="ms-topnavselected" />

  <StaticHoverStyle CssClass="ms-topNavHover" />

  <DynamicMenuStyle  BackColor="#F2F3F4" BorderColor="#A7B4CE" BorderWidth="1px"/>

  <DynamicMenuItemStyle CssClass="ms-topNavFlyOuts"/>

  <DynamicHoverStyle CssClass="ms-topNavFlyOutsHover"/>

  <DynamicSelectedStyle CssClass="ms-topNavFlyOutsSelected"/>

   </SharePoint:AspMenu>

  

   <SharePoint:DelegateControl runat="server" ControlId="TopNavigationDataSource">

  <Template_Controls>

  <asp:SiteMapDataSource

  ShowStartingNode="False"

  SiteMapProvider="SPNavigationProvider"

  id="topSiteMap"

  runat="server"

  StartingNodeUrl="sid:1002"/>

  </Template_Controls>

   </SharePoint:DelegateControl>

<asp:SiteMapDataSource

  ShowStartingNode="False"

  SiteMapProvider="SharedNavigationProvider"

  id="topSiteMap2"

  runat="server"/>

</asp:ContentPlaceHolder>

There were some other updates that were needed to these master pages, notably adding an assembly reference and script manager for a third party Ajax control.  These two lines went before the first HTML tag:

<%@ Register TagPrefix="wssuc" TagName="DesignModeConsole" src="~/_controltemplates/DesignModeConsole.ascx" %>

<%@ Register TagPrefix="XXXXXX" [deleted] %>

And this line goes after the first <FORM> tag

<asp:ScriptManager runat="server" ID="ScriptManager1" />

Remember earlier when we discussed the importance of editing in Notepad?  Sharepoint Designer can rewrite the src tag of the DesignModeConsole reference to remove the tilde, which causes errors when the page is deployed to the site.  If you are seeing errors, make sure the wssuc tagprefix entries are properly formatted as noted above.

September 2009 Update: SharePoint 2007 Internal Version Numbers

Another two months!  Microsoft has just released the August 2009 Cumulative Updates for  Sharepoint.  And this time, the “August” updates actually were released in August (the June 2009 Updates don’t match the file release dates.)

Again, if you ever need to confirm which update/revision of SharePoint you are running, without accessing the binary files themselves, these version numbers correspond to the version numbers reported in SharePoint Central Administration.  You can find this by going into the Operations tab, and under Topology and Services, select Servers in Farm.

We'll be getting our first peek at the binaries for the SharePoint 2010 platforms later this month, and will be developing version release tables for those as soon as we can, too.

SharePoint 2007 Version/Release	Microsoft Support KB Reference	Version Number from Central Admin	Release Date
MOSS 2007 or WSS 3.0 August 2009 Cumulative Update	KB973409/KB973410	12.0.0.6514	25 August 2009
MOSS 2007 or WSS 3.0 June 2009 Cumulative Update	KB971537/KB971538	12.0.0.6510	20 July 2009
MOSS 2007 or WSS 3.0 April 2009 Cumulative Update	KB968851/KB968850	12.0.0.6504	30 April 2009
MOSS 2007 or WSS 3.0 SP2	KB953334/KB953338	12.0.0.6421	28 April 2009
MOSS 2007 or WSS 3.0 Cumulative update	KB956056/KB956057	12.0.0.6327	16 September 2008
MOSS 2007 or WSS 3.0 Infrastructure Update	KB951695/KB951297	12.0.0.6318	15 July 2008
MOSS 2007 or WSS 3.0 post-SP1 hotfix	KB948945	12.0.0.6303	21 February 2008
MOSS 2007 or WSS 3.0 post-SP1 hotfix	KB941274	12.0.0.6301	31 January 2008
MOSS 2007 or WSS 3.0 post-SP1 hotfix	KB941422	12.0.0.6300	26 February 2008
MOSS 2007 or WSS 3.0 SP1	KB936984/KB936988	12.0.0.6219	8 December 2007
MOSS 2007 or WSS 3.0 Security Bulletin MS07-059	KB942017	12.0.0.6039	9 Octoer 2007
MOSS 2007 or WSS 3.0 August 24, 2007 hotfix package	KB941422 (updated)	12.0.0.6036	24 August 2007
MOSS 2007 or WSS 3.0 RTM [Released To Manufacturing]	N/A	12.0.0.4518	16 November 2006
MOSS 2007 or WSS 3.0 Beta 2 TR	N/A	12.0.0.4407	2006
MOSS 2007 or WSS 3.0 Beta 2	N/A	12.0.0.4017	2006