I had a chance to participate in Microsoft Office System Webcast: Tips and Tricks for Groove 2007, Provide Anywhere, Anytime Access to People and Information (Level 100) delivered by Paul Cannon, Microsoft Groove Product Manager, on 09/16/2008 and help out in answering questions in the background. Paul did a great job in delivering a lot of useful information in one short hour and made it very interesting. During the session, there was a question on Groove vs. OneNote which I thought is something worth further discussion.
Based on the story I have heard, OneNote is a Microsoft home-grown product developed due to the need for a tool to quickly and easily capture, organize, and share information from meetings. OneNote to me is an effective tool for digital notes taking. I love and use it very extensively to organization the mass amount of information I need to manage everyday on meetings minutes, status reports, research and drafts, presentation story-boarding, my technical notes, personal journals, important emails, etc. In OneNote 2007, many functions and capabilities are added including sharing information and working with others, and it appears there is some overlap between OneNote and Groove which can share files as well.
One important distinction between OneNote and Groove is the fundamental issue each is trying to address. Fundamentally, OneNote is for (digital) notes taking while Groove is for collaboration. I imagine the originally design focuses or requirements, between OneNote and Groove, must be noticeably different. The ease of information capturing is, in my view, a main focus on notes taking, while seamless content synchronization is essential to collaboration. Taking notes does not necessarily imply information sharing or teamwork, while collaboration suggests there is something in common or synchronized among the team members.
I see taking and sharing notes are not necessarily the same with collaboratively developing contents. Further sharing information is one activity in collaboration, while collaboration is much more than just information sharing. Collaboration is about establishing common operating picture as it is frequently stated in the context of emergency management and military operations. Collaboration is a state and not simply a shareable file or a deliverable system. When I say Groove is for collaboration, I mean Groove is a solution to facilitate all members of a team to reach a state that is situation-aware and informed decisions can be made accordingly. It has much to do with sharing and communications. It is also about knowing, sharing, and discussing what happens, when it happens, what to do with it, who to do it, and how all within a relevant context. For all these needs, Groove offers out-of-box capabilities including presence awareness, automatically data synchronization, always-on encryption, workspace tools, instant messaging, VoIP, SharePoint and InfoPath integration, API, and SDK.
This is not to suggest, between Groove and OneNote, one is better than the other. I see they are simply trying to solve different business problems and should be employed accordingly to maximize an information worker’s productivity.
This post assume you have some experience of Groove admin console.
With Groove domain policy settings, an administrator can enforce corporate policies on Groove collaborations. First, we must deploy the Device Management Key to our Groove clients, such that a Groove domain policy becomes enforceable. Two ways there are to configure a managed client:
With the Device Management Key deployed, a desktop however needs to be in a lockdown environment to ensure once the key is in place, stays in place.
Figure 1. Groove Device Management Key
Figure 2. Enable Groove client manageability during account configuration
Next, restricting collaboration based on trust relationships by adding and cross-certifying Groove domain certificates using the interface. Here in Figure 3. the interface is shown for your reference and no cross-certified certificate is included.
Groove Server 2007 Manager is a Certificate Authority which establishes the trust hierarchy in Groove PKI. Groove PKI is a term signifying the PKI automatically deployed within and specific to an associated Groove domain during account configuration process. Since all Groove internal communications are Groove PKI-based, a client in current domain can exchange keys, establish a secure channel, and communicate with only those clients trusting a cross-certified certificate. In other words, a Groove user can send out a workspace invitation to both trusted and non-trusted clients. A non-trusted client however cannot establish a secure channel and consequently will not be able to successfully communicate within Groove with the sender of a workspace invitation and join the associated workspace. This, in essence, prevents a Groove user in current domain from collaborating with a target, however not cross-certified, Groove user in other Groove domain.
Certainly once the settings are save in the default policy templates or customized ones. We will then assign the policy templates to an intended group or account.
Figure 3. Cross-Certified Certificates
Figure 4. Restricting collaborations with only those from certified domains
In this screencast, I talked about the deployment options available in Groove and how to relate Groove infrastructure, Groove and SharePoint integration, and the associated collaboration model with Microsoft's vision. To see it in full screen, double-click the display area.
Blain Barton, a seasoned IT professional, an interesting and dynamic speaker, and one of the most respected IT Evangelists in Microsoft technical communities is hosting a PowerShell series in Second Life. I know many of you known him and attended his events around the country in the past years are fans just like one I am, and we always get a good laugh and learn something new from him at the same time. I know this PowerShell series will be as informative and interesting as many other great presentations Blain has delviered. For more information, follow the link below.