cegeland
asked on
How to change MySite URL?
Hi!
I'm having some issues with our Sharepoint 2010 Standard MySite. When the user opens the drop down meny in the upper right corner and selects "My Site" or "My Profile" they are sent to the wrong URL.
The web app hosting the MySite site collection is reachable using two access mappings;
http://servername:82 (Internal) and https://mysite.domain.com (Internet). Our problem is that the users are sent to http://servername:82 which only works when the user is connected to our office network/AD.
I've checked the "My Site Host" under "Manage Service Applications" --> "User Profiles" --> "Setup MySite" in the sharepoint CA, and it says http://servername:82, and I can't seem to be able to change it (I type in https://mysite.domain.com and hit "save", but the http://servername:82 is still there when i check it again).
The weird thing is that when the user tries to connect from the same web application (https://sharepoint.domain.com), using a different access mapping (https://sp.domain.com) - they are sent to the correct MySite URL.... So how can I change it so that all access mappings on our web app sends the users to the same MySite URL?.
Thanks :)
I'm having some issues with our Sharepoint 2010 Standard MySite. When the user opens the drop down meny in the upper right corner and selects "My Site" or "My Profile" they are sent to the wrong URL.
The web app hosting the MySite site collection is reachable using two access mappings;
http://servername:82 (Internal) and https://mysite.domain.com (Internet). Our problem is that the users are sent to http://servername:82 which only works when the user is connected to our office network/AD.
I've checked the "My Site Host" under "Manage Service Applications" --> "User Profiles" --> "Setup MySite" in the sharepoint CA, and it says http://servername:82, and I can't seem to be able to change it (I type in https://mysite.domain.com and hit "save", but the http://servername:82 is still there when i check it again).
The weird thing is that when the user tries to connect from the same web application (https://sharepoint.domain.com), using a different access mapping (https://sp.domain.com) - they are sent to the correct MySite URL.... So how can I change it so that all access mappings on our web app sends the users to the same MySite URL?.
Thanks :)
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
This error appears when I removed the access mapping for http://servername:82.
I removed the entry for http://servername:82 under content sources (Search Service Application) and added https://mysite.domain.com. Same web application, just different access mapping.
I wonder if it has something to do with the fact that login fails when I try to access https://mysite.domain.com from the Sharepoint server itself (works just fine from every other computer). If I accessed http://servername:82 whil I had the alternate access mappings I could connect just fine from the Sharepoint server.
I removed the entry for http://servername:82 under content sources (Search Service Application) and added https://mysite.domain.com. Same web application, just different access mapping.
I wonder if it has something to do with the fact that login fails when I try to access https://mysite.domain.com from the Sharepoint server itself (works just fine from every other computer). If I accessed http://servername:82 whil I had the alternate access mappings I could connect just fine from the Sharepoint server.
The start address https://mysite.domain.com cannot be crawled.
Context: Application 'Search_Service_Application_-_v2', Catalog 'Portal_Content'
Details:
Access is denied. Verify that either the Default Content Access Account has access to this repository, or add a crawl rule to crawl this repository. If the repository being crawled is a SharePoint repository, verify that the account you are using has "Full Read" permissions on the SharePoint Web Application being crawled. (0x80041205)
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
That was already done (had to do that to get search crawl working while using http://servername:82).
I believe it's got something to do with the server itself - since I cannot login to https://mysite.domain.com using farm admin account. This is only a problem when trying to access https://mysite.domain.com from the server itself - I can connect just fine from any other computer.
I believe it's got something to do with the server itself - since I cannot login to https://mysite.domain.com using farm admin account. This is only a problem when trying to access https://mysite.domain.com from the server itself - I can connect just fine from any other computer.
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
Ok - excellent, that did the trick. I am now able to crawl https://mysite.domain.com.
When I click "MySite" or "MyProfile" from the drop down I am now sent to https://mysite.domain.com which is correct.
The only problem left is when I search for people, or click any of the links on MySite they all refer to documents/sites listed under http://servername:82/ which now no longer exists.
Maybe a search index reset?
When I click "MySite" or "MyProfile" from the drop down I am now sent to https://mysite.domain.com which is correct.
The only problem left is when I search for people, or click any of the links on MySite they all refer to documents/sites listed under http://servername:82/ which now no longer exists.
Maybe a search index reset?
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
Will this solve the problem?