MySite Redirection and MOSS Service Pack 2

MOSS 2007 SP2 has a bug fix that it seems a number of people don’t want. It enables redirection from the userdisp.aspx page in a local site collection to the MySite portal page even when a portal site connection is not configured.

Thankfully, a quick feature scoped at the farm level can remedy the situation. The following feature disables profile redirection and also hides the “My Site” global navigation link. Note that this feature is scoped at the Farm level, making it applicable to all web applications/site collections within the farm.

The feature

feature.xml

<?xml version="1.0" encoding="utf-8"?>
<Feature  Id="6768ca75-6afb-4b70-80e6-7964abf4fb68"
          Title="Disable MySites Redirection"
          Description="Disables MySites redirection to person.aspx (pre-SP2 behavior) and removes the My Site global navigation link"
          Version="12.0.0.0"
          Hidden="FALSE"
          Scope="Farm"
          DefaultResourceFile="core"
          xmlns="http://schemas.microsoft.com/sharepoint/">
  <ElementManifests>
    <ElementManifest Location="elements.xml"/>
  </ElementManifests>
</Feature>

elements.xml

<?xml version="1.0" encoding="utf-8" ?>
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
    <Control Id="GlobalSiteLink1" Sequence="50" ControlSrc="" />
    <Control Id="ProfileRedirection" Sequence="50" ControlSrc=""/>
</Elements>

Reference

Users Not Found in People Pickers

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?

Retrieving User Profile Properties for the Current User

Retrieving a user’s profile properties can be achieved with the following block:

(more…)

Filtering Inactive User Profiles From an SSP

To filter inactive Active Directory users from a Share Services Provider, an updated “User Filter” is required. The following filter:

(&(objectCategory=Person)(objectClass=User)(!(userAccountControl:1.2.840.113556.1.4.803:=2)))

will automatically skip over inactive domain accounts when profile imports are occurring.

Performance Optimization WordPress Plugins by W3 EDGE