Latest Posts

My 10 year old daughter came home from school today with a simple math problem that she had to solve and she asked if there was an easier way to solve the problem.

I recently presented at the SharePoint Saturday Denver event where I, rather rapidly, went through some SharePoint 2010 PowerShell stuff – the presentation was not meant as a general PowerShell overview but instead assumed that you already had at least a basic knowledge of PowerShell in general so that we could focus on SharePoint specific things.

The information in this post is specific to SharePoint 2010 Beta 2 and may need adjusting for the RTM version. In an effort to continue with my previous posts where I demonstrated how to build a basic farm and it’s site structure using XML configuration files and PowerShell for SharePoint 2010 I would like to now share how to create a search service application.

In a previous post I detailed how to use PowerShell to perform what would be otherwise done using PSConfig to create an initial SharePoint Farm. In this post I will continue the example and show how to create your web applications using a simple XML configuration file and a reusable script.

With SharePoint 2010 we now have the ability to create custom PowerShell cmdlets that can be deployed just like any other SharePoint artifact using SharePoint Solution Packages (WSP) created with Visual Studio 2010.

The information in this article is based on BETA 2 of SharePoint 2010 – there may be differences with the RTM release. Update 12/18/2009: I’ve updated the post to reflect BETA 2 changes and have considerably simplified the script removing all the dependencies on helper functions so that the core pieces required to build a basic farm are focused on rather than the complex elements to support tracing and error handling as I previously had it.

The information in this article is based on BETA 2 of SharePoint 2010 – there will likely be differences with the RTM release.` Finally, the NDA is lifted and we can openly talk about SharePoint 2010!

Not too long ago Microsoft introduced a security fix which addresses a possible attack vector in which malicious software tries to impersonate a local request, thereby bypassing certain constraints. The problem with this fix is that it introduces some issues for SharePoint servers, effectively resulting in 401.

I’ve been doing a lot of configuration driven PowerShell scripts lately and I had a bit of trouble figuring this bit out so I thought I’d write up a short post about it.

A lot of people that are using SharePoint 2007 (WSS or MOSS) for collaboration have either enabled self service site creation in which they allow their end-users to create a page using the scsignup.