Differences between Groove and SharePoint Server 2007 / SP Service

[gocrm]

I have asked MS pre-sales about this and was not getting the right answer.

1) What are the differences between Office Groove and Groove Server 2007?

2) What are the differences between Groove Server 2007 and SharePoint Server
2007? Looks like they also have a Groove Server version.

What I don't understand is why Microsoft go and buy out Groove software and
add it to the MS product lines. Both products seems to serve the same
purpose, which is to collaborate? Does this mean Microsoft will potentially
phase out SharePoint?

Thanks for your help.

 

[gocrm]

Thank you very much. So in your humble opinion, I could actually deploy both
Groove and SharePoint Servers and they will compliment each other? I haven't
seen an organization that utilize both servers as of yet. So far, I see
companies use either one or the other. Would you please be so kind as to
suggest what collaboration environment would benefit from having both Groove
and SharePoint in place?

By the way, what are the real differences between SharePoint Services and
SharePoint Servers? If you happen to know, that would be great.

 

[c1sbc]

1). Office Groove - that is the 'client' and can run on hosted servers (part
of the client license). Groove Server - contains the Management, Relay and
DataBridge servers (on 64b W2K3 servers). The Groove Management/Relay server
is for deploying/managing your own clients (usually in an Enterprise). The
Databridge is to integrate external datasources within Groove workspaces.
These can be shared by other (invited) Groove clients.

2). Groove client has a SharePoint files tool that will permit Groove & SP
sites to share files. The Groove Server and SP Server are very different
products but they can all be integrated (based upon the requirements).

Groove client and SharePoint Server are complementary products. Each has a
different user base - SharePoint is 'web-based' whereas the Groove client has
standalone (offline) capabilities with a very secure foundation. I don't see
one replacing the other.

The Office Groove site has more info - (product guide)
http://office.microsoft.com/en-us/groove/FX100487641033.aspx

SBC

 

[c1sbc]

you could have SharePoint users (non-Groove clients) share files with Groove
clients and vice-versa. Groove has 'offline' capabilities whereas SP not so
(alebit 3rd-party solutions are available).

SP comes in two flavors: WSS 'services' and the 'portal' MOSS server. The
latter is a seperate product ($) and WSS comes free (download) add-on with a
W2K3 server (std & ent eds). A Groove client tool (SharePoint Files) tool
will work with WSS & MOSS.

SBC

 

[Schultz IT Solutions]

Hello gocrm,

With Groove you can work together as a team and communicate on project
issues and create project deliverables. With SharePoint you can
define/enforce workflows for documents (like the finalizing/publishing
process and so on) and publish them.
Groove is (to us) a more informal "collaborate to create working-progress
results" approach, whereas SharePoint is for the formalized, workflow
oriented and process driven approach.
The Microsoft Groove Product-Flashpresentation kind of says it (when the
project manager publishes a press release from Groove to SharePoint to
initiate workflow to get the signoff from senior management).

Both products therefore have their target usergroups (which do not have to
be identical).

 

[c1sbc]

a picture is worth a thousand words -

http://www.groove.net/images/products/server_overview.jpg


SBC