When you install MOSS (not evaluation copy) part of that process is creating a Shared Service Provider. This is essentially a set of services like User Profile store, Search, BDC, MySites etc… These services can be consumed from one or more SharePoint Web Applications (and other apps outside of SharePoint if you like).

One of the services that an SSP provides is details on where users MySites are located. This is because if you have, for example, multiple Portals then you usually only want a person to have one MySite. So by having multiple web applications consuming from one SSP you can achieve this.

However, by default when you create an SSP the MySite location is set to be under that SSP. I think an example will help here…


Your organisational portal site is on http://OrgsIntranet

Your SSP must be on another URL domain or port so let say… SSP1 is on http://OrgsIntranet:12345

What this will mean, by default, is that your users MySites are at http://OrgsIntranet:12345/personal/

As you can probably imagine, this is not ideal for all organizations. In fact for most organizations that will only ever have one main portal this is not ideal.

The reason we host MySites on another web application is so that no matter what site you are on, when you hit the “mysite” link at the top of the page, it will take you to the right place and that place is not dependant on any individual portal.

In an ideal world you would have an address like http://my or http://mysites as a DNS name for your SSP … so that the address makes sense and you could run it on port 80 like everything else. It makes the URL look nicer I guess.

Anyway! So for orgs with only one main portal they might want their urls to look something like:

Org Main portal: http://OrgsIntranet

MySites : http://OrgsIntranet/personal/

So how do you go about configuring this? …


I am assuming you have your intranet/portal at http://OrgsIntranet and the mysites location is currently at http://OrgsIntranet:12345/personal/

First you have to make sure you have 2 managed paths set up in the http://OrgsIntranet web application. To do this jump into central admin, “Application Management” tab, “Define Managed Paths”. Make sure you are working on the right web application once you are in that screen.
Create an Explicit inclusion for path “mysite”
Create a Wildcard inclusion for path “personal”
Jump back into the “Application Management” tab & choose “Create site collection”
Create a new site (call it MySiteHost if you like), pick “Create site that this URL” and choose “mysite”, also pick the “My Site Host” template (important).
Once that site is created jump back into Central Admin, go into your Shared Services Provider configuration, go into the “My Site settings” page
Set “Personal site provider” to “http://OrgsIntranet/mysite/” and “Location” to “personal”, click OK.
Done! Now when your users click on the “mysite” link their MySite will be created in the right place.

Leave a Reply

Your email address will not be published. Required fields are marked *

Related Posts


Azure – Your account is temporarily locked to prevent unauthorized use

Here is the another common error message when dealing with directory and password synchronization.  Error Message: Your account is temporarily locked to prevent unauthorized use. Try again later. Contact Customer Support if the problem persists Read more…


Verify Service Status Remotely Using Local Account – PowerShell Script

I have modified one of my previously published script – Stop, Start, Disable Service Remotely–PowerShell Script (http://portal.sivarajan.com/2011/05/stop-start-disable-service.html) to use Local account (instead of a domain account) to verify the status of the service.   Input Read more…


Collect Computer Information From Active Directory– PowerShell Script

This PowerShell script can be used to collect computer information from Active Directory.   I am searching only Windows XP and Windows 7 machines.  You can update these values  by modifying $OS1 and $OS2 variables. $OS1 Read more…