Groove and Sharepoint integration

[Bryan Campbell]

Has anyone used the Groove 2007/Sharepoint connector? If so I have a couple
of questions regarding this:
1. Since Groove can share workspaces outside the firewall and doesn't
require domain authentication how does Sharepoint validate credentials to
support document library synchronization?
2. Does Sharepoint only support document library synchronization with
Groove (sort of like SyncToy) or does it also support other document types?
3. Can Groove flag changes to files that can be automatically synched to
Sharepoint (e.g. a Project Plan)?
4. I read that Groove supports full version control using Sharepoint. Has
anyone used this?

Thanks for any help and experiences on this.

 

[Justin Rodino]

Hi Bryan,

Lots of Groove quesitons from you recently I'll answer inline.

Has anyone used the Groove 2007/Sharepoint connector? If so I have a couple
of questions regarding this:

Used it a bit - but never in anger so "your milage may vary"

1. Since Groove can share workspaces outside the firewall and doesn't
require domain authentication how does Sharepoint validate credentials to
support document library synchronization?

It will authenticate with the credentials of whomever has SharePoint
access. i.e. If I have a portal and you don't, but I invite you to my
Groove workspace, it will synchronise with my credentials. it also
requires a one-time setup from someone "inside". (see the synchronise
button in the next few answers also)

2. Does Sharepoint only support document library synchronization with
Groove (sort of like SyncToy) or does it also support other document types?

What were you meaning when you say "document types"? The Document
Workspace holds document types and configurations therein. Essentially
each "SharePoint" tool within the workspace works very similar to the
file store, but allows for further synchronisation back to the WSS/MOSS
portal in question.

3. Can Groove flag changes to files that can be automatically synched to
Sharepoint (e.g. a Project Plan)?

Depending on SharePoint is configured, it will have the revisions of
when the files were last amended/updated/added to the portal in
question. Also, there is a Synchronise button which is part of the
library, so if you don't have access to the library but I do, I can
choose to sync it back and forth, etc.

4. I read that Groove supports full version control using Sharepoint. Has
anyone used this?

Again, similar to three, depending on how you have SharePoint configured
for version control is how Groove will sync back/handle it.

If you want, I can create a SharePoint Groove session and add you to it
to show you how it will work and let you "tinker" as you will not have
access to my MOSS infrastructure, however you will be part of the Groove
Workspace.

HTH,

Justin

 

[Bryan Campbell]

Thanks for the detailed reply Justin this is really helpful. As you can
probably tell we're in the midst of an analysis on Groove and how to best use
it particularly with our investments in Sharepoint.

I had a chance to see the Sharepoint synchronization and as you pointed out
it works through a proxy of a credentialized user and all updates to the
Sharepoint site are 'owned' by this person even though the original document
might have been provided by someone else. I know you can setup an
'automatic' posting mechanism but it seems that there are some risks
particularly if the person in the delegate role is unavailable for a period
of time (vacation, etc.). Have you had any experiences with this?

BTW... I would be interested in seeing a 3rd party Groove to Sharepoint
experience, if you wanted to ping me with an email ([email protected])