mylifeinaminute.com

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

• How to bypass MySite redirection introduced with the SP2 when you display user details?

Recently, we came across a need to migrate an existing (SharePoint 2007) RTM content database to a new farm, which had SP1 pre-installed.  After taking a full backup of the existing database (through SQL Server), the backup was restored in the new farm.

Note: I should also mention that the database was migrating from SQL Server 2000 to SQL Server 2005.

After resetting the SharePoint servers, browsing to the site in question brought the following error:

Server error: http://go.microsoft.com/fwlink?LinkID=96177

At this point, we detached the content database in question (Central Administration » Application Management » Content databases). Once the database was successfully detached from the farm, it was reattached using the following STSADM command:

stsadm -o addcontentdb -url ‹URL› -databasename ‹DBNAME›

Reattaching the content database with the above command completely successfully, and as an added benefit performed an inplace upgrade, bringing the database schema up to SP1.  This might prove to be a helping hand when it comes to migrating to MOSS 2007 SP1 if your wish is to start with a new farm, but retain your original content.