Groove Advisor: The Groove Blog

Groove Advisor is for IT professionals, developers, and users of Groove 2007.

Browse by Tags

Related Posts
  • Blog Post: How to integrate Groove with a .NET Framework Application

    John Hancock ( www.johnchancock.com ) is a Senior MCS consultant with a background in building, and writing about, .NET apps. He has recently been working with Groove, and published a great article on MSDN about integrating Groove with a custom .NET Framework application. You can download the code sample...
  • Blog Post: Two new whitepapers posted to Technet

    Two new Groove whitepapers are now available on Technet: Microsoft Office Groove: Backup Options in an Enterprise presents information to help the reader understand the unique backup and restore requirements of Microsoft Office Groove by presenting the data storage model Groove uses, reviewing...
  • Blog Post: Groove Security, meet SharePoint Security.

    If you are looking at Groove and SharePoint, at some point the security questions start coming up...Does Groove support SharePoint ACL's in the SharePoint Files Tool? Who can edit content in the tool? Who can get access to the tool? Is this a violation of the SharePoint security model? Groove Security...
  • Blog Post: What you need to know about Groove Server

    There's a new article in Computerworld talking about Groove Server 2007. "Office Groove Server creates the functional magic between Groove clients and extends management, communication and data integration..." Jonathan Hassell. Read the whole article here: What You Need to Know About Microsoft...
  • Blog Post: Welcome to the Groove Advisor!

    Readers probably know some of the Groove history , and know that Groove was acquired by Microsoft in 2005, and now ships with Office 2007 . It probably comes as no surprise that one of our biggest post-acquisition challenges has been navigating Microsoft. You don't go from 170 heads to >70,000 heads...
  • Blog Post: Groove vs. SharePoint

    I get asked a lot about Groove and SharePoint. They both support collaboration, right? Why do I need both? Can 't I just do all my work in _______? While each is a strong product in its own right, they are really targeting different types of activities. Deploy them together, and you can get some...