Compartir a través de

When you install Service Pack 1 (SP1) of Office 2010, SharePoint Workspace 2010 is installed -- UPDATE

  • Artículo

(9/13/2011: Updated to add KB link)

Update, March 28, 2012: There is now an update available for this issue. Note that you must apply the update before applying SP1.

 

When you install Service Pack 1 (SP1) of Office 2010 over Office Professional Plus, SharePoint Workspace 2010 is installed automatically, even if it was not selected as part of the originally Office 2010 installation. SP1 provides an Add-In tool API for creating custom tools for Groove workspaces. Due to a bug in the SP1 installation process, the addition of this API and related functionality in Visual Studio Tools for Office (VSTO), triggers an installation of SharePoint Workspace if it is not already present, rather than just upgrading it if it is present.

This isn’t much of a problem for individual users who do not have Office Groove 2007 installed – they can just remove the component. However, it is more of an issue for two types of customers:

  • Enterprise installations that want to maintain a standardized environment 

    The added component may not be initially obvious, as the installation does not add program shortcuts to SharePoint Workspace anywhere. However, the executable files and  all supporting libraries are installed and registered, so if a user manually runs \Program Files\Microsoft Office\Office14\Groove.exe, SharePoint Workspace will start. More obviously, the user will see “Sync to SharePoint Workspace” in the Site Actions menu of SharePoint 2010 sites that support workspaces. 

  • Any user with Groove 2007 installed 

    The SharePoint Workspace  2010 installation will upgrade Groove 2007, and there is no reliable way to regress to Groove 2007 from SharePoint Workspace 2010. 

We are aware of the issue and working to get it resolved.

If you have not yet installed SP1

If you fall into one of the categories listed above, do not install SP1 directly. Instead, download the SP1 package, and then open a Support incident with Microsoft and request escalation to the SharePoint Workspace Support team. The Office Deployment team wrote a script to correct the downloadable SP1 package, and we can provide you with this script and instructions. Reference KB 2612800: https://support.microsoft.com/kb/2612800

Install the update described at https://support.microsoft.com/kb/2598245

If you have already installed SP1

If you have already installed the update and do not want to use SharePoint Workspace, simply uninstall the component.

If you have already installed the update over Groove 2007, there is no supported way to downgrade to that version. However, you may be able to recover. See What to consider when you upgrade from Groove 2007 to SharePoint Workspace 2010 for more information.

Comments

  • Anonymous
    January 01, 2003
    Glenn, I'm sure you realize that I cannot promise unreleased software. This is, however, an active bug, and the script is an interim solution. Personally, a revised service pack seems like the optimal resolution to me, but I'm looking at this from the perspective of Support, and may be lacking significant information about the development and distribution factors of other potential fixes. I'm working on a KB article now, and as soon as that is published, I will amend this post with the number, which you can use for reference. For now,  the SPW support team and Office Deployment teams are aware of this issue, so if you get a case to either team, the procedural time should be minimal.

  • Anonymous
    January 01, 2003
    Hi alistg, There are a few reasons why we are doing it this way. First, and most importantly, the script is an emergency measure, and has not been through a release level of QA or documentation. For that reason alone, we want customers running the script to be in contact with Support, so we can answer questions and help with any problems. It also can be a good opportunity -- if there is time -- to inquire why the customer does not want the application enabled. Finally, we will have an official, release-tested solution to this problem available very soon, and information posted on the Internet tends to persist. Once a solution is out, we don't want customers using this workaround unnecessarily because they found it first.

  • Anonymous
    January 01, 2003
    It was published yesterday evening: support.microsoft.com/.../2612800

  • Anonymous
    January 01, 2003
    Susan, This will happen with any version of Office Professial Plus. If your Office license does not include SharePoint Workspace, it will not. Good point -- I'll clarify that. One odd thing about this issue is that a significant number of customers affected will be ones who do not use the product I support. I'm used to all Office being Office Professional Plus.

  • Anonymous
    August 30, 2011
    If I'm reading this right, every consumer and enterprise install of Office 2010 (no matter what SKU) will have SharePoint Workspace now installed and will start to get updates for this.  Would it be possible to provide some sort of consumer fixit tool for consumers and then some sort of group policy guidance for removing this for enterprises?

  • Anonymous
    August 30, 2011
    Instead of  a script that fixes the package, can we please get a v2 of the Service Pack?   In the meantime, is there a KB article we can quote when we call support so that they can quickly check that this should be logged under a bug, and therefore won't decrement our premier support hours?

  • Anonymous
    August 30, 2011
    I'm not finding this on a workstation that was upgraded from Office 2007 to 2010, does this always occur or is there some other trigger?

  • Anonymous
    August 31, 2011
    Okay so the trigger is that you had a version of Office suite that included SharePoint Workspace but didn't originally install it in their build.  I'm Office 2010 Standard on SA here and thusly it's not installed.  Okay making more sense now.

  • Anonymous
    September 13, 2011
    Frances, when do you expect the KB article to be published and how do I get a case to either team? is there a link to raise this?

  • Anonymous
    October 25, 2011
    re: "open a support incident with Microsoft Customer Support, and then request escalation to the SharePoint Workspace team or to the Office Deployment team. These teams can give you a script to modify the downloadable SP1 package so that it does not install SharePoint Workspace" > This is ridiculous ! Since a whole loads of people are going to need this, why dont you just post that script to the web

  • it will save people having to log calls
  • it will save (an already over-worked) PSS from having to service the calls where there is no need for them to do so !
  • Anonymous
    December 28, 2011
    Hi, I've been dealing with this bug for over a year...still no viable solution. Please release that script...it won't hurt anyone I swear :P