The article How to install the OneDrive for Business sync client for SharePoint 2013 and SharePoint Online recommends you uninstall SharePoint Workspace before installing OneDrive for Business, but then implies you can run the two together, if Office 2010 is upgraded to SP2 (Service Pack 2) before you install OneDrive for Business. This post addresses the usual questions about this configuration.

Is it supported?

This configuration is not recommended. However, the following instances are supported:

• An installation of the standalone client that complies with the guidelines in How to install the OneDrive for Business sync client for SharePoint 2013 and SharePoint Online.
• An MSI installation of Office Pro Plus 2013 that complies with the guidelines in How to use Office 2013 suites and programs (MSI deployment) on a computer that's running another version of Office.

Are there any issues if I follow these procedures?

The only established issue is with starting a sync from a remote library – for example, your OneDrive for Business library, or a SharePoint Team site library. When you click Sync from the library, the operation should start the sync application most recently installed or repaired. For Office compatibility guidelines, this should always be the more recent version. However, we have seen cases in which SharePoint Workspace is started instead. If you run both sync clients, you may need to create syncs manually from the client UI.

Because Office 2010 updates may violate the version order of installation repair, it is possible that other issues may occur that lead to cache corruption in a sync or difficulty opening Office files from the cloud in a local application. You should be able to prevent this by always repairing the 2013 client after Office 2010 updates are applied. 

What can I do if I installed OneDrive for Business before updating Office 2010 to SP2?

Save any unsynced data, uninstall OneDrive for Business, repair the Office 2010 installation, and then reinstall OneDrive for Business.

As of the  October 2013 update to SkyDrive Pro (KB2825633), the server version is detected, and the version restriction is enforced.

In most cases, this will prevent people from accidentally getting into a situation where they are relying on an unsupported configuration, or spending a lot of time trying to debug something that won't work. However, people whose SharePoint 2010 libraries have synced should plan for that sync stopping.

Here's what you will see:

•  If you attempt to create a new sync to SharePoint 2010 with the updated SkyDrive Pro application, you will receive this error:

Sorry, we can't sync this library because it's hosted on a SharePoint 2010
server. For more information, please get in touch with your help desk.

• If you have a working sync between SharePoint 2010 and SkyDrive Pro, and then you update the application, the library may stay in sync initially. However, any change to the library schema will cause the sync to fail.

To sync SharePoint content to your computer, you should use the SharePoint client software of the same version, if available. 

• To sync SharePoint 2010 content, use SharePoint Workspace 2010.
• To sync SharePoint 2013 content, including most content hosted on Office 365 SharePoint Online, use SkyDrive Pro 2013.

Historically, the previous version has also worked, although this may not always be true. Currently:

• You can sync SharePoint 2013 content to SharePoint Workspace 2010
• You can sync SharePoint 2010 content with the Groove 2007 SharePoint Files tool

 ORIGINAL POST:

Nesting folders is a traditional approach to organizing data in the Windows file system, but in SharePoint, organization is more commonly done via views or pages. In a few cases, folder structures in a document library may cause problems with SharePoint Workspace sync, and the symptoms can be misleading. Here are the issues we have seen:

Nested folders moving to the root of the library in the workspace

If you create a document library and give it a nested folder structure in SharePoint Server 2007, then upgrade the server to SharePoint 2010, SharePoint Workspace may not be able to interpret the folder structure when you sync the library to SharePoint Workspace. The folders will move to a flat structure. For example, this:

Library
  Folder1
     Subfolder1
     Subfolder2
     Subfolder3
  Folder2

will become this in the workspace:

Library
  Folder1
  Folder2
  Subfolder1
  Subfolder2
  Subfolder3

A hotfix for this issue is available here:

Description of the SharePoint Workspace 2010 hotfix package (x86 Groove-x-none.msp, x64 Groove-x-none.msp): February 28, 2012
https://support.microsoft.com/kb/2597939

“Path not found” when you create a nested folder structure in SharePoint Workspace in one operation

If you drag and drop nested folders containing a file into SharePoint Workspace, or created a nested folder structure containing a file while offline in SharePoint Workspace, the Office Upload Center may return the following error:

Upload failed: Path not found

This happens because folder creation and file transfer are processed by two different Office modules. In some cases, the upload center attempts to transfer the file before the folders for it are available. To prevent this, pause uploads in the Upload Center before transferring the nested folder structure, or before coming online. This pause does not affect folder creation. Once the folder structure is created on the SharePoint server, resume uploads to transfer the files.

“Harmonica version not found” or files appearing to “jump” to the root of the library

Consider the same folder structure as above, with all the files in the subfolders.

Library
  Folder1
     Subfolder1
     Subfolder2
     Subfolder3
  Folder2

The site was created in SharePoint 2010 (or you applied the hotfix) and the library syncs accurately. However, at some point, while you are editing a file, someone deletes and recreates the folder and subfolder that the file was synced from, and then recreates them, along with the previous version of the file you are editing. Now this happens:

1. You save your changes to the file, but the upload fails. In the workspace, the Error Tools/Resolve tab appears.
2. You click Resolve Conflict or Error. This takes you to the Microsoft Office Upload Center, which shows the error "Upload failed. Server file updated."
3. Since you know you are the only person who should be editing this file, you click Resolve, click Choose, and then click Keep My Version.

Instead of your edits overwriting the copy on the server, you end up one of these states:

If the changes to folder structure occurred while you were online in SharePoint Workspace:

• Upload center looks as if the sync worked – the file is no longer shown as pending upload.
• The workspace shows both the current and previous versions of your file in the root of the library, and your subfolder is gone. In Error Tools/Resolve tab, clicking Resolve Error may cause a notification that “errors were encounter while synchronizing….” to appear briefly. Clicking More Info displays the error “Harmonica version not found.”
• The server shows the previous version of your edited file in the root of the library, and your updated version in the subfolder.

If the changes to folder structure occurred while you were offline in SharePoint Workspace, and you have applied the hotfix:

• Upload Center reports "Upload Pending."
• The workspace shows both the current and previous versions of your file in the root of the library, and your subfolder is gone. In Error Tools/Resolve tab, clicking Resolve Error may cause a notification that “errors were encounter while synchronizing….” to appear briefly. Clicking More Info displays the error “Harmonica version not found.”
• The server shows the previous version of your edited file, but in the root of the library. Your changes never upload.

If the changes to folder structure occurred while you were offline in SharePoint Workspace, and you have not applied the hotfix:

• Upload Center reports “Path not found.”
• The workspace shows the edited version of your file in the root of the library, and your subfolder is gone. In Error Tools/Resolve tab, clicking Resolve Error may cause a notification that “errors were encounter while synchronizing….” to appear briefly. Clicking More Info displays the error “Harmonica version not found.”
• The server shows the original version of your edited file, but in the root of the library. Your changes never upload.

Note: Without the hotfix, you may also see this issue with only one folder layer.

In all of these cases, the only way to resume synching the document library is to disconnect the library from the workspace and then reconnect it, so the workspace has the new folders and folder IDs.

If you need to make this sort of change on the server, advise people who are synchronizing the library to a workspace to disconnect it before you delete and replace content. Also, if you use an Explorer view to work with folders on SharePoint, be careful that you are not deleting and recreating folders as part of that process, by dragging them out and then back in.

Alternatives to nested folders

In some cases, you may want to consider different ways of organizing your data. A SharePoint document library should be a fairly narrow category, that will not usually require extensive subdivision. You may have files in one library that should be distributed among multiple libraries, or mingled projects that would be clearer if each had its own subsite. Some data is easier to organize in a list. If you are new to SharePoint (or stumbled into it unprepared), the article SharePoint 2010 Usage Best Practices is a good place to start.

When working with Views, keep in mind one limitation of SharePoint Workspace – it does not recognize views that sort, group, or filter by columns that do not apply to all content types. For example, you cannot sync a view that sorts by File Type, as folders do not have a value for File Type.

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.

• Office 2010 Service Pack 1 (SP1)
• An SDK for SharePoint Workspace 2010
• The June Cumulative Update (CU) for Office 2010

These updates provide significant fixes and enhancements that you have been asking for. Here are the details, by package.

 SP1 for Office 2010

Office 2010 Service Pack 1 (SP1) provides the following fixes and enhancements for SharePoint Workspace:

Extensions to the document download limit

Prior to SP1, SharePoint Workspace restricted its use of the Office Document Cache (ODC) to keep the cache at or below 1800 files, and would begin to warn the user about the impending limit at 500 files. SP1 increases the overall limit to 10,000 files. In addition, SharePoint Workspace SP1 displays ODC usage in an easy-to-read meter viewable at the time of workspace creation and from the File tab, providing relevant information to the user less intrusively than the pop-up warning.

Add-In tool API

SP1 provides an Add-In tool API for creating custom tools for Groove workspaces. The SDK for this API is available in a separate download. Note that these add-in tools can be used only in 2010 Groove workspaces. The new API does not provide programmatic access to SharePoint workspaces, Shared Folders, or the general application UI.

For more information on Office 2010 SP1, see this article -- Description of Office 2010 SP1

SDK for add-in tools

The Software Development Kit (SDK)  for SharePoint Workspace helps developers create add-in tools for Groove workspaces in SharePoint Workspace 2010, SP1.

Download the SDK from https://www.microsoft.com/download/en/details.aspx?id=26642.

See the documentation at https://support.microsoft.com/default.aspx?scid=kb;en-US;2553023.

 The June Cumulative Update (CU) for Office 2010

The June CU contains fixes completed too recently to get into the service pack release. It resolves the following SharePoint Workspace issues:

• When multiple SharePoint Files tools in a Groove workspace are set to synchronize automatically, synchronization may fail and remain inoperable.
• If you have "/" or "\" characters in an account name, the Active Directory auto-configuration or Outlook auto-configuration fails.
• Windows Firewall exception query returns an error if exception is not a local policy.

For more information on the Office 2010 June CU, see this article -- Office 2010 Cumulative Update for June 2011

We recommend applying SP1 and then the June CU.

Firewall error at startup - again

Some of our customers in more security-conscious domains have been noticing an issue with the SharePoint Workspace firewall exception check. At every startup, many users are getting a warning message that starts like this:

SharePoint Workspace is unable to communicate through your firewall and will run with limited functionality. To resolve this problem, enable SharePoint Workspace as a Windows Firewall exception...

(How it continues from there depends on your configuration.)

However, despite this message, SharePoint Workspace works through the firewall.

Why does this happen?

We want to warn the user if SharePoint Workspace is blocked by Windows Firewall, so when the program starts up, it makes the following checks:

• Is Windows Firewall enabled?
• If so, is there an exception for SharePoint Workspace in the local firewall policy?

If Windows Firewall is enabled and SharePoint Workspace doesn't have an exception in the local firewall policy, it returns an error to warn the user that program functionality may be limited.

But it works!

SharePoint Workspace only checks the local policies. Many organizations - especially ones that maintain tight security - manage firewall exceptions at the IT level and distribute them via domain policy. If you have a domain policy that pushes a Windows Firewall exception for SharePoint Workspace to domain members, the startup check will not see it. However that exception will work, allowing SharePoint Workspace to communicate through the Windows Firewall.

How do I stop it?

Although program functionality is not affected, this message still worries end users, and by requiring a user acknowledgment, it delays program startup. We recognize that this is a problem for many customers. For the moment, the best workaround is to duplicate the domain firewall exception to the local policy branch.

To determine if you use blugro2, follow these steps:

1. On the File tab, click Info, Click Connection Settings, and then click Communications Manager.
2. In Communications Manager, click Network Settings.
3. In Advanced Network Settings, under the Network Diagnostics tab, click to expand Home Relay devices. You may have multiple devices.
4. If you see the hostname blugro2relay.groove.microsoft.com, you use blugro2 as a relay.

Not all accounts on blugro2 were affected. If your account uses blugro2, and you believe you may be experiencing presence or synchronization issues, stop and restart Groove or SharePoint Workspace.

SharePoint Workspace 2010 might crash on startup or during account configuration under the following circumstances:

• You upgraded to Office 2010 from Office 2003 or an earlier version of Office.
• Your operating system is Windows XP SP3.
• Your computer is NOT a tablet system.

The cause of the problem has to do with an incompatibility with Handwriting Recognition software that was installed with an earlier version of Office, and that might still reside on your system even after uninstalling the earlier version.

To resolve this issue, you can uninstall the Handwriting Recognition software as follows:

1. Click Start and then click Control Panel.
2. Click Regional and Language Options.
3. Click the Languages tab.
4. Click the Details button to open the Text Services and Input Languages dialog box.
5. Click Handwriting Recognition.
6. Click Remove, and then click OK.

Depending on the state of the system, you may need to reboot to complete the change.

SharePoint Workspace 2010, supports single sign-on authentication. Groove 2007 and previous Groove products required a password at startup, and you either had to provide this password each time, or configure Groove to remember it and risk forgetting it yourself. Now, SharePoint Workspace will link your SharePoint Workspace account to your Windows login, and once you are logged into Windows, you will be able to start up SharePoint Workspace without being prompted for a password.

A brief note on security

So, what is the effect on security? Surprisingly positive! I'm not going to cover that in detail, as Paul Cannon and Leon Alexandrou have a great post on it here: https://blogs.msdn.com/sharepoint_workspace_development_team/archive/2010/02/18/sharepoint-workspace-and-single-sign-on.aspx. One point they don't cover is the rise of malware that harvests passwords as the user types them. As that sort of thing has become more common, the risks associated with individual application authentication prompts have increased. Also, be aware that your account still has a password internally -- it just happens to be a very long one that Windows provides for you. If someone took all the Groove data files off your computer and moved them to all the right places on their own computer, they would not gain access to the data by installing Groove over it. See the linked post for more information.

Behavior at First launch

Obviously, with single sign-on, there's not a lot to see. If SharePoint Workspace 2010 is a new installation, then the first time you start SharePoint Workspace, you are be prompted to create or install an account, as before, but that account creation process is a little shorter, because you are not prompted to set a password. When the account is created, SharePoint Workspace generates an internal password that is accessed through your Windows account, after you log into Windows. It will use that password behind the scenes when you start SharePoint Workspace.

If you are upgrading from Groove 2007, this is a little different. The first time you start SharePoint Workspace, you will be prompted for your Groove 2007 account password. If you do not remember it, you will be prompted to reset your password. Once you have provided the password, or the reset has completed successfully, SharePoint Workspace converts your account to use single sign-on.

Importing your account

If you subsequently import your account on another computer, SharePoint Workspace will display a password prompt. If you upgraded from Groove 2007 and remember your 2007 password, you can enter it here. Otherwise, click Reset Password and follow the instructions in the confirmation email you receive. Again, your account on this computer will be linked to the current Windows account.

Single sign-on with domain management

In an unmanaged environment, single sign-on links the SharePoint Workspace account to the active user's local Windows account. However, it is possible for an administrator to configure Groove Manager and Active Directory so that a SharePoint Workspace account is linked to the active user's domain account instead.

Configuration

Configuring the servers

Here are the basic steps administrators must take to integrate single sign-on with domain accounts.

1. Install Groove Server Manager 2010. In Directory Configuration, opt to connect to an Active Directory server, and provide the name of the Active Directory Forest.
2. Configure Active Directory for integration with SharePoint Workspace provisioning by adding the schema extension for use in the Active Directory Users and Computers (ADUC) tool. (For details, see https://technet.microsoft.com/en-us/library/ee681773(office.14).aspx.)
3. Enable automatic account configuration by creating a Group Policy Object (GPO) that assigns domain members to the Groove Manager. (For details, see https://technet.microsoft.com/en-us/library/ee681783(office.14).aspx.) 

After you have completed this configuration, qualified users who install SharePoint Workspace will have SharePoint Workspace accounts linked to domain accounts instead of to local Windows accounts.

Requirements on the desktop

To benefit from the above configuration, the following conditions must be met on the computer that will run SharePoint Workspace:

• The computer is joined to a domain that is in the Active Directory Forest that the Groove Manager is integrated with.
• The person who will use SharePoint Workspace logs in to the computer using a domain account that has the GPO designating a Groove Manager.
• The person who will use SharePoint Workspace is the person who starts SharePoint Workspace for the first time. (If SharePoint Workspace is installed by someone other than the person who will use it, the installer must not start the application after the installation completes.)

When the user launches SharePoint Workspace for the first time, SharePoint Workspace will contact the assigned Groove Manager and fetch the user's account.