Masuk
 
AwalPerpustakaanWikiPelajariUnduhDukunganKomunitasForum
Resources for IT Professionals >
> 
> 
Publish links to Office Client Applications - Does it work?

Jawab Publish links to Office Client Applications - Does it work?

  • 05 Juni 2012 3:15
     
     
    Masuk untuk Memilih
    0

    When publishing a link to either a Document Library or a Data Connection Library in a User Profile Service Application, I can't figure out how to push that link to a client application. I've done the following: Installed Desktop Experience on the SharePoint server, navigated to the SharePoint site and launched my site as two different users, but nothing seems to work. This site is really not quite correct as the User Profile Service Application has absolutely nothing to do with the functionality actually working as the registry entries themselves address the issue without a User Profile Service Application ever being created. I could accomplish the same with GPO but not nearly as slick. Seems like this functionality carried over from MOSS/Office 2007 and is either half-baked or completely unbaked in the 2010 product. If anyone has actually got this to work with SharePoint 2010 and Office 2010, please tell me what I'm missing.

    http://martinmason.wordpress.com

     

Semua Balasan

  • 08 Juni 2012 21:00
     
     Jawab
    Masuk untuk Memilih
    0

    Hi Martin,

    So the Publish Links functionality is a client-side pull mechanism in which the Office client application sends a requests for the Published Links by making a call to publishedlinksservice.asmx (http://msdn.microsoft.com/en-us/library/websvcpublishedlinksservice.aspx) to determine what links are to be written to the registry of the client machine.

    In regards to publishing a Data Connection Library, there is more to this configuration and it is required to update the registry key as outlined in the following articles that were written for SharePoint 2007. This article explains the dependencies between both Office SharePoint and Excel Services and why it has to be configured this way.

    http://technet.microsoft.com/en-us/library/cc262899(TechNet.10).aspx#subsection7

    If you are encountering an issue with other published links not being pushed to your server, you may have another issue going on. One article I found outlined that if you are using Windows 2008 or R2, then you need to enable the Desktop Experience and WebDav features in order for published links to work properly. However please note that if the server is hosting SharePoint, it is not recommended to enable WebDav features as SharePoint utilizes its own WebDav service. If you enable the IIS WebDav, there can be conflicts between the services which would break WebDav functionality all together.

    Some other links that I found that also be relevant to your issue regarding how the 'Publish Links to Office Client Applications' feature works.

    http://technet.microsoft.com/en-us/library/cc263102.aspx
    http://blogs.msdn.com/b/sudeepg/archive/2009/09/03/published-links-to-office-client-applications-do-not-show-up-in-file-open-or-save-dialogs.aspx
    http://blogs.msdn.com/b/davidlean/archive/2010/11/15/how-to-see-sharepoint-2010-data-connections-from-excel-2010.aspx
    http://blogs.msdn.com/b/jorman/archive/2009/07/30/my-sharepoint-sites-memberships-general-overview-on-how-this-functionality-works.aspx

    Please let me know if this helps.

    Thanks!

    Adam Rudell | Technical Support Lead | SharePoint Technologies | Microsoft Corporation

     
  • 19 Juni 2012 10:01
     
     
    Masuk untuk Memilih
    0

    Hi Adam,

    Thanks. I was already familiar with most of those links. There's one issue that you're missing from the links above. In order for the pull mechanism to work, the Set default My Site has to be set. This functionality is inadvertently missing from Office 2010 clients. http://paulliebrand.com/2011/09/27/set-as-default-my-site-sharepoint-sites-or-my-sharepoint-sites-missing-in-office-2010-on-sharepoint-2007/

    There's just too many places you have to go to accomplish this simple task and little to no guidance from Microsoft's documentation. Therefore, I wrote up a blog post to describe what I found. http://martinmason.wordpress.com/2012/06/17/excel-2010-connection-files-on-the-network-sharepoint-data-connection-libraries-and-the-enterprise/ Let me know if everything stated there is correct.

    Martin

    http://martinmason.wordpress.com

     
  • 20 Juni 2012 15:37
     
     
    Masuk untuk Memilih
    0

    Hi Martin,

    So you are correct that when you use Office 2010 with SharePoint 2007, users will not be prompted for "Set default My Site". This is due to certain registry keys the SharePoint 2007 Server uses are not installed with Office 2010. In order to get this to work, you need to create the following registry keys to get this working as expected when integrating Office 2010 clients with SharePoint 2007 as described in the blog you located.

    [HKEY_CLASSES_ROOT\PortalConnect12.PersonalSite]
    @="PersonalSite Class"

    [HKEY_CLASSES_ROOT\PortalConnect12.PersonalSite\CLSID]
    @="{E7339A62-0E31-4A5E-BA3D-F2FEDFBF8BE5}"

    [HKEY_CLASSES_ROOT\PortalConnect12.PersonalSite\CurVer]
    @="PortalConnect12.PersonalSite.1"

    [HKEY_CLASSES_ROOT\PortalConnect12.PersonalSite.1]
    @="PersonalSite Class"

    [HKEY_CLASSES_ROOT\PortalConnect12.PersonalSite.1\CLSID]
    @="{E7339A62-0E31-4A5E-BA3D-F2FEDFBF8BE5}"

    Once the keys above are implemented, SharePoint 2007 will write to the following locations to store the MySite URL

    Vista and above
    HKEY_CURRENT_USER\Software\AppDataLow\Microsoft\Office\14.0\Common\Portal

    XP
    HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Common\Portal

    In reviewing your blog, everything looks good. The one thing I will mention though is in regards to your comments about SP1 removing the security updates. When you deploy SP1 to SharePoint 2010, it is required as well to deploy the June 2011 CU with it which would redeploy the updates that SP1 overwrites. Additionally June 2011 CU is stand alone and is not included with the other CUs such as August 2011 or December 2011. The best practice is to deploy SP1 w/ June 2011 CU and then install any additional CU that you may want to deploy.

    Let me know if this helps clarify some things and if you have any further questions.

    Adam Rudell | Technical Support Lead | SharePoint Technologies | Microsoft Corporation