mylifeinaminute.com

This one is a little old, but still relevant. If you’ve ever struggled with trying to convey what SharePoint is to your users, refer them to this video.

Ah yes, the people picker again. I recently inherited an environment where the previous administrator was kind enough to not document anything, especially the items he/she had been playing with in development.

When trying to designate a user as a Primary Site Collection Administrator in Central Administration, I was unable to query for subsets of domain users on a single web application. After checking all of the usual suspects (Peoplepicker-searchadforests I’m looking at you) with no success, it was off to the not-so-usual suspects.

It turns out the previous admin was kind enough to set the Peoplepicker-searchadcustomfilter property on the main portal site collection. After setting the property to null

stsadm -o setproperty -pn peoplepicker-searchadcustomfilter -pv "" -url [URL]

all was once again right with the world.

Now where did I leave my sledgehammer?

The title says it all. Get patching. Hit up the security bulletin for downloads.

Reference

• Microsoft Security Bulletin MS10-070 – Important
• Microsoft Security Response Center
• Microsoft SharePoint Team Blog

The Microsoft SharePoint team has released specific guidance for a workaround for the recently announced ASP.NET vulnerability (Security Advisory 2416728). With a slight modification, this guidance will also apply to SharePoint 2007.

For SharePoint 2010, the relevant web.config entry will look like:

 <customerrors defaultredirect="/_layouts/error2.aspx" mode="On" redirectmode="ResponseRewrite"></customerrors>

While for SharePoint 2007, the web.config entry will read:

 <customerrors defaultredirect="/_layouts/error2.aspx" mode="On"></customerrors>