which country user step here?

Tag Cloud

MOSS (47) SharePoint 2007 (37) SharePoint 2013 (27) SharePoint 2010 (23) MOSS admin (17) PowerShell (17) admin (17) developer (17) List (15) WSS (14) sql query (14) MOSS SP2 (13) end user (11) scripting (11) wss V3 (11) Moss issue (8) permission (8) search (8) sql (8) RBS (6) Service Pack (6) database (6) reportadmin (6) workflow (6) Excel (5) client object model (5) CU (4) Client Code (4) Command (4) Cumulative Updates (4) IIS (4) Patch (4) SharePoint designer (4) stsadm (4) ASP.NET (3) Content Database (3) Groove (3) Host Named Site Collections (HNSC) (3) SharePoint 2019 (3) Tutorial (3) alert (3) batch file (3) codeplex (3) error (3) incomming email (3) restore (3) upload (3) user porfile (3) Caching (2) Folder (2) Index (2) Internet (2) My Site Cleanup Job (2) My Sites (2) News (2) People Picker (2) Share Document (2) SharePoint 2016 (2) View (2) Web Development with ASP.NET (2) add user (2) authentication (2) coding (2) column (2) deploy solution (2) domain (2) download (2) enumsites (2) exam (2) export (2) issue (2) june CU (2) load balance (2) mySites (2) network (2) office 365 (2) orphan site (2) performance (2) profile (2) project server (2) query (2) server admin (2) theme (2) timer job (2) training (2) web master (2) web.config (2) wsp (2) 70-346 (1) 70-630 (1) AAM (1) Anonymous (1) Approval (1) Cerificate (1) Consultants (1) Content Deployment (1) Content Type (1) DOS (1) Document Library (1) Drive Sapce (1) Excel Services (1) Export to Excel (1) Feature (1) GAC (1) Get-SPContentDatabase (1) Get-WmiObject (1) HTML calculated column (1) ISA2006 (1) IT Knowledge (1) ITIL (1) Install (1) Link (1) MCTS (1) Macro (1) Migration (1) NLBS (1) Nintex (1) Office (1) Open with Explorer (1) ROIScan.vbs (1) Reporting Services (1) SPDisposeCheck.exe (1) SPFx (1) SQL Instance name (1) SSRS (1) SharePoint Development (1) SharePoint Online (1) SharePoint admin (1) SharePoint farm (1) SharePoint on-premises ( 2016 FP2 and 2019 ) (1) Shared Services Administration (1) Site Collection Owner (1) Site template (1) Steelhead (1) URLSCAN (1) VLOOKUP (1) WSS SP2 (1) XCOPY (1) abnormal incident (1) admi (1) app (1) application pool (1) aspx (1) audit (1) availabilty (1) backup (1) binding (1) blob (1) branding sharepoint (1) cache (1) calendar (1) connection (1) copy file (1) counter (1) crawl (1) custom list (1) domain security group (1) event (1) excel 2013 (1) facebook (1) filter (1) fun (1) group (1) iis log (1) import (1) import list (1) improment (1) interview (1) keberos (1) log in (1) metada (1) migrate (1) mossrap (1) onedrive for business (1) operation (1) process (1) publishing feature (1) resource (1) security (1) send email (1) size (1) sps2003 (1) sql201 (1) sql2012 (1) sub sites (1) system (1) table (1) task list (1) today date (1) vbs (1) video (1) web part (1) web server (1) widget (1) windows 2008 (1) windows 2012 R2 (1) windows Azura (1) windows account (1) windows2012 (1) wmi (1)

Monday, June 22, 2009

Configure MOSS 2007 to use Multiple My Site Web Applications

As you may know when a MOSS 2007 farm is provisioned, one of the first tasks that you have to perform is to create a Shared Service Provider (SSP). One of the components of the SSP is a My Site host location however the SSP is associated with a single My Site Web application by default. Recently I was asked if it was possible to use multiple My Site Web applications within a single MOSS 2007 farm. This could be useful for operational/performance/capacity planning purposes, this is totally possible and I’ll fully outline the steps required.

In the example the farm that I’m using the SSP (including My Site http://mysite ) and Intranet Web application have been created (http://intranet)

1. The first step is to create a Web application for the new My Site host location, I’ll not bore you with the steps, there are outlined here if you have never done this before - http://technet.microsoft.com/en-us/library/cc263256.aspx it’s important that you choose a friendly URL, I have selected http://mysite2

2. Once the Web application has been created we need to create a Site Collection at the root (/). To do this:

a. Launch Central Administration

b. Select Application Management

c. Select Create Site Collection

d. Select the MySite 2 Web Application from the Web application drop down

e. Give this an appropriate title for example My Site 2

f. Ensure that / is selected for the Web site address – http://mysite2/

g. Within the template selection select the Enterprise tab and select MySite host location

h. Enter an appropriate Site Collection administration – Click OK to create the Site Collection

3. We now need to configure the new My Site host location as being trusted, to do this launch the SSP administration site (link should be available from the quick launch within Central Administration)

4. Within the User Profiles and My Sites section select Trusted My Site host locations

5. The Trusted My site host locations should be empty, to add an entry for the new My Site host location click New. Enter the URL for the new My Site host location and an optional description.

You may be wondering how exactly do we configure new My Sites to be created within this new location? The answer is using an audience. If you are unfamiliar with the concept of audiences you may find the following article useful -http://blog.tomaselfving.com/2007/05/audience-targeting-in-moss-2007.html

A brief description is “Audiences are used to target content to users based on their jobs or tasks within the organization. Users in an audience will see audience-specific content on the site that is not available to other users.”

You then need to either use an existing audience or create a new audience specifically to direct users to the appropriate My Site host location. For example If I have a company with offices in six major cities I may decide to create a My Site Web application for each, then create an audience for each office and configure the Target Audience for each Trusted My Site Host Location to point to the relevant office. The audience compilation (which can run on a schedule) could use the AD attribute Office for example.

When a user logs into http://intranet and click the My Site link for the first time it will look at the audience that the user is a member of and then direct them to the appropriate My Site based upon their location (at least in this example – one thing I haven’t tested is the behavior when a user is a member of multiple audiences and that are associated with trusted My Site host locations– one for a rainy day perhaps J

this article is from http://sharepoint.microsoft.com/blogs/fromthefield/Lists/Categories/Category.aspx?Name=My%20Site


Frobnitzz said...
This comment has been removed by the author.
Jos said...
This comment has been removed by the author.
Jos said...

make sure you also set the 'MySite Settings':

[X] Enable My Site to support global deployments

to allow the SSP to properly refer requests for user user profiles

If a user is member of the multiple audiences/groups the first one matchin the the trusted MySite host locations will be used.