New answers tagged my-site
0
You could implement a new Alternate Access Mapping.
Some refs:
http://www.codeproject.com/Articles/530934/SharePoint-Alternate-Access-Mapping-Configuration
http://www.youtube.com/watch?v=3s_uY983LXM
1
OR...you could NOT use PORT numbers for your MySite web application and either create a unique URL like http://mysite or http://my (or whatever works for your organization and culture). Then set trusted sites.
OR, If the users are non-domain users (the new domain will trip an auth prompt when you switch hosts) you could create the MySite host under a ...
1
You need to configure ADFS with SharePoint. Essentially its a type of Claims Authentication with a conceptual walkthrough mentioned here
This is an excerpt from MSDN that explicitly mentions the flow of a single user from one web app to another in SharePoint
Visiting Two SharePoint Web Applications
In this walkthrough, John visits the a-Portal ...
0
http://msdn.microsoft.com/en-us/library/hh446525.aspx
This gives you a pretty good overview of what you need to do. In a nutshell:
1) Set up SharePoint on Claims Authentication, each web application authenticating to Active Directory (or a custom provider if you'd rather)
2) Configure the Security Token Service so everyone is on the same page
Not easy ...
2
A powershell script that will create a profile for every AD user, then
creates there My Site
[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint")
[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.Office.Server")
[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint.Portal")
$dom = ...
0
You'll have to create a SharePoint solution in which you make feature stapling.
You can find plenty of info about feature stapling for all versions of SharePoint on Google and Bing.
1
I finally solved my issue with the following code in a Feature in the activate method.
SPSite site = properties.Feature.Parent as SPSite;
SPWeb web = site.RootWeb;
try
{
using (SPLimitedWebPartManager manager = web.GetLimitedWebPartManager("person.aspx", PersonalizationScope.Shared))
{
......
......
manager.AddWebPart(new ...
0
If I remember correctly there are one or two hidden webparts on default.aspx that initiate the process, and also bring up the modal "let's get social"
Top 50 recent answers are included
