none
Outlook contact card name link goes to wrong SharePoint MySite URL

    Question

  • I have a two SharePoint 2010 environments, production and development (e.g. http://mysite and http://mysitedev). In Outlook 2010, when I hover over a name in an email to view the contact card and then in the contact card proceed to click on the person's name to view their profile page, it is currently opening up the link to their MySite on our development server. We need this URL to point to our production SharePoint MySite instance.

    Despite researching, it's unclear where the setting lives to change this URL (SharePoint, registry, AD, etc.). I have made sure that the production MySite is set as the default MySite locally for the Office apps (i.e. http://paulliebrand.com/2011/09/27/set-as-default-my-site-sharepoint-sites-or-my-sharepoint-sites-missing-in-office-2010-on-sharepoint-2007/). It also doesn't appear that a person's wWWHomePage attribute in AD has any bearing on this. Can anyone tell me what must be changed to correct this?

    Friday, December 14, 2012 12:38 AM

Answers

  • Responding to my own thread in case anyone else comes across this issue, I wanted to note that I was able to (mostly) figure this one out based on this article: 

    https://blogs.msdn.com/b/mcsnoiwb/archive/2012/05/30/how-is-the-link-to-people-s-my-site-from-outloook-provided.aspx?Redirected=true

    Basically, this link is stored locally in the Registry:

    [HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Common\Server Links\Published\My Site\Profile Site]
    "LinkType"=hex(b):00,00,00,00,00,00,00,01
    "IsMember"=dword:00000000
    "IsPublished"=dword:00000001
    "Url"="http://my:80/Person.aspx?user="

    This can be set by going to your MySite and clicking on the "Set as default MySite" link, in Internet Explorer only as this then launches an ActiveX control that sets this registry entry.

    Here's where it gets tricky. In my instance, the URL set was actually correctly pointing to my production environment. I had also used the "Connect to Office -> Add to SharePoint Sites" option in the ribbon of a document library on one of the sites of my development environment which changes this behavior completely. As the article indicates, when Outlook (and Lync, apparently) is actually creating the link used in the name bubble popup, it appears the default MySite settings subkey associated with the -first- added site alphabetically under [HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Common\Server Links\Published\] is used. Since all of the entries that are not "My Site" take the form of the site's URL ("http://site.foo/"), precedence is always going to actually use the added site's default MySite settings instead of those explicitly set under the "My Site" key ("h" before "M").

    This behavior probably goes undetected if you have just have one SharePoint farm as the settings would presumably match. But if you have added sites from multiple farms, this behavior is completely unexpected as your explicitly set default MySite settings are never going to be used (though you might get lucky and have the first listed site's default MySite settings match your desired configuration anyway).

    This seems to me to be a bug in the Office client handling and it would be nice if something could be filed.

    Thursday, December 20, 2012 7:44 PM

All replies

  • I'm fairly certain that it is the wWWhomePage attribute.  Do you have more than one domain controller in your organization?  It is possible the one you are changing is not the one that sharepoint or the user's outlook is looking at.

    Chris Givens CEO, Architecting Connected Systems Blog Twitter

    Saturday, December 15, 2012 3:35 AM
  • Responding to my own thread in case anyone else comes across this issue, I wanted to note that I was able to (mostly) figure this one out based on this article: 

    https://blogs.msdn.com/b/mcsnoiwb/archive/2012/05/30/how-is-the-link-to-people-s-my-site-from-outloook-provided.aspx?Redirected=true

    Basically, this link is stored locally in the Registry:

    [HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Common\Server Links\Published\My Site\Profile Site]
    "LinkType"=hex(b):00,00,00,00,00,00,00,01
    "IsMember"=dword:00000000
    "IsPublished"=dword:00000001
    "Url"="http://my:80/Person.aspx?user="

    This can be set by going to your MySite and clicking on the "Set as default MySite" link, in Internet Explorer only as this then launches an ActiveX control that sets this registry entry.

    Here's where it gets tricky. In my instance, the URL set was actually correctly pointing to my production environment. I had also used the "Connect to Office -> Add to SharePoint Sites" option in the ribbon of a document library on one of the sites of my development environment which changes this behavior completely. As the article indicates, when Outlook (and Lync, apparently) is actually creating the link used in the name bubble popup, it appears the default MySite settings subkey associated with the -first- added site alphabetically under [HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Common\Server Links\Published\] is used. Since all of the entries that are not "My Site" take the form of the site's URL ("http://site.foo/"), precedence is always going to actually use the added site's default MySite settings instead of those explicitly set under the "My Site" key ("h" before "M").

    This behavior probably goes undetected if you have just have one SharePoint farm as the settings would presumably match. But if you have added sites from multiple farms, this behavior is completely unexpected as your explicitly set default MySite settings are never going to be used (though you might get lucky and have the first listed site's default MySite settings match your desired configuration anyway).

    This seems to me to be a bug in the Office client handling and it would be nice if something could be filed.

    Thursday, December 20, 2012 7:44 PM
  • Hi,

    Thanks for having posted the bug fix and the explanation. I had the same problem. The MyProfile URL attribute in the registry was taken by the contact retriever from the first item in the list of server links in the registry, which is the acceptance SharePoint farm, and not the Production farm.

    Pierre 

    Friday, September 20, 2013 9:55 AM