Recap of SharePoint Saturday Houston

SharePoint Saturday Houston was May 1. I’ve been pulling my thoughts together for a couple of weeks now.  I want to evaluate each aspect of the event in highlight. I am not going to discuss each bullet point on a blog. If you have questions or varying opinions, I’d sure love to hear them in the comments.

Let’s begin with facilities. The Norris Center is an awesome facility for a conference this size.

  • It has 5 rooms for tracks, each holding 50 to 100 people
  • It has an enormous lunch room
  • It is well run
  • They had great food and plenty of it: snacks, excellent lunch, and refreshments in every room all day

The quality of speakers was remarkable. 

  • I’m not going to name any names. 🙂
  • We had a good balance of local representatives and people from around the region, and a few from each coast
  • We had great topics with people who are considered some of the experts in their fields
  • We had general, case study, architecture, administration, and developer’s covered

The schedule.

  • Here’s where I fess up. I was part of the committee who decided to have tracks go until 6pm. That was a mistake.
  • We would have been better off with one less time slot and a little longer presentation sessions.
  • Nonetheless, the session content was great, we had plenty of time to sit down and eat, and we still had time to give away the swag!

Supporters (Vendors)

  • The vendors were awesome.  They contributed the funds to make this happen. And from what I heard, they felt it was a good investment.
  • They did a great job of engaging with the guests
  • They did not make you feel obligated to talk to them (SPC, PDC, etc, the vendors were a bit more grabby)
  • I feel like they respected people and valued their time.


  • Volutneers were great.
  • I think we needed just a couple more “runners” if you will.
  • They were helpful and very accomodating.

Overall, this was a great event. I am glad that I was able to be a part of it!

See you at Houston TechFest on October 9, 2010!

Why the TaxonomyPicker.ascx is no longer used

So some good SharePoint folks have stumbled into an error pertaining to the TaxonomyPicker control. (Links are at the bottom.)

My guess here is that the TaxonomyPicker.ascx control was left behind – obsolete. Nothing Taxonomy-related is found in Microsoft.SharePoint.Portal. For Taxonomy – or managed metadata – look to the Microsoft.SharePoint.Taxonomy.dll found in the 14\ISAPI folder.

The fact is, I don’t see any place in SharePoint where the control is being used. It has probably been replaced with the page TaxonomyTreePicker.aspx.  It is used when you are filling in metadata for a field of type TaxonomyField (gui calls it “Managed Metadata”).

Here is this page in action:

If you look at the source (Right click and View Source on the form), you’ll see the traces pointing back to the TaxonomyTreePicker.aspx file.

So why does the error matter? Well, when you run an IISRESET or reboot, IIS will try to load the usercontrols into memory. I don’t like manually editing files, especially usercontrols. So I’m going to leave it alone.


Disable Shutdown Event Tracker

When prepping your development environment, you may wish to disable the Shutdown Event Tracker. It’s this dialog: 

To disable it, simply open up group policy editor by Start > Run > Type gpedit.msc and Enter.
Navigate to Computer Configuration > Administrative Templates > System.
Find the “Display Shutdown Event Tracker” setting shown below:   

Now select the Disabled box and click OK. 

To apply this new change to the current user session (aka, you don’t have to log off to apply the setting), open a command prompt and type: 

gpupdate /force 


Tomorrow I am flying out to Washington, D.C., in order to speak at SharePoint Saturday DC, aka, SPSDC. It should be a fun time. I look forward to presenting on MMS and all the wonderful questions and insights that attendees bring.

If you are going to SPSDC, but sure to say hi.

STSADM to PowerShell mapping

For those joining me in learning powershell for SharePoint, here is a handy reference on technet mapping the ststadm commands to PowerShell commands.

SQL Server R2 RTM

SQL Server 2008 R2 officially RTM’d.

I’ve been working with the SQL CTP and SharePoint Beta, and the BI story is pretty incredible.  Here’s a quote that’s pretty accurrate (it’s not as easy as they make it sound, but the BI capabilities are still pretty impressive).

With the release of SQL Server 2008 R2, Microsoft is introducing powerful new managed self-service BI capabilities, bridging the gap between IT professionals and end users by leveraging familiar tools such as Microsoft Excel 2010 and Microsoft SharePoint Server 2010. With the new BI technology named PowerPivot, end users can bring data from virtually anywhere and manipulate large datasets with ease while still enabling IT to monitor and manage user-generated BI solutions.

As soon as the code his MSDN, it’ll be time to rebuild the SharePoint 2010 SQL server.

TechNet blog found here:  
Press Release found here:

Use PowerShell to Get ManagedPaths in SharePoint 2010

Just a quick post here. I wanted to get a list of all Managed Paths in my SharePoint 2010 farm.

So I first saw


Next, I found it’s parameters by using

get-help get-spmanagedpath

Note: If you use it without a parameter, it prompts you for the web app url. Kind of neat. The PowerShell ISE actually displays a dialog window, while the PS> cmd prompt asks for a parameter.

Knowing that I could get a list of web applications from somewhere, I found


And then piping each webapplication’s “url” property to another commandlet will get me what I’d like. And that is a listing of all managed paths in my farm.

get-spwebapplication | foreach { Get-SPManagedPath -WebApplication $_.url }

From there, it was all playing with the script to save both the web application url and the managed path. Here’s what I came up with:

And here is the code if you need to copy and paste it.

write-host "------ BEGIN -----"
write-host ""
Add-PSSnapin Microsoft.SharePoint.Powershell
$a = New-Object System.Collections.ArrayList
$webapps = get-spwebapplication
foreach ($webapp in $webapps)
    $paths = Get-SPManagedPath -WebApplication $webapp.url;
    foreach ($path in $paths)
        $a.Add( $webapp.url + $ );
#Write out the results if you need them
write-host ""
write-host "------ END -----"

Next stop, creating a managed path with PowerShell.

Where is the link to Create a Managed Path in SharePoint 2010 Central Administration?

This morning I was wondering: Where did my Central Admin link to Managed Paths go?

If you’ve been looking around for the link to Define a Managed Path in SharePoint 2010, stop looking. It’s not on the Central Administration “Control Panel” page(s). Instead, when you go to create a new Site Collection, there is a link.

If you are like me, you have a predefined set you want to use. Until I get the PowerShell commands posted, use this:


To remember it, all pages in CA are either in _admin or in _layouts. This one is admin, and then Site Collection Prefix (or scprefix.aspx).

I only post this just as a tip in case you were going crazy looking for it!