I’m working on this cool new offering for my company and of course we use Microsoft Office Groove 2007 to quickly and easily share documents, presentations and such, without having to use an intermediary website like SharePoint or an internal fileshare over a VPN. I was invited to this particular Groove workspace as a ‘participant’ (my security role for this workspace) and for the place where you can put your files that basically comes down to permissions you see in the screenshot.
At first, those permissions seemed to work fine, because I couldn’t delete a document that was put there by someone else. In this case however, I was asked to update this particular document and I chose to save the updated document under a different name in the workspace. Now I had 2 documents in the same folder, 1 old en 1 new. There was also an “OLD” folder in the workspace, so I decided I would move the old document to the OLD folder and this is where I hit the security restrictions, and after some fiddling, the loophole:
Because you don’t have the “Delete files/subfolders” permission as a ‘Participant’ in Groove, you can’t delete someone else’s files. This prevented me from moving the old document (which was owned by someone else) to the OLD folder. However I could copy the document to the OLD folder since the security permissions do allow that, so now I only needed to delete the old document in the root folder.
I tried to open the document, make a change to it and save it back again to Groove, but even though the “Modified By” value was updated (to myself) I didn’t became the owner of the document and still couldn’t delete it – Groove’s security model scores again.
Next however I tried something devious (and it worked): I created a file with the same name as the document that I wanted to delete from Groove and dragged that file to the workspace. Groove asked me if I wanted to overwrite the file and needless to say I happily clicked ‘yes’ and presto! I was now the owner of the file and I could delete the file!
It seems that Groove sees an overwrite action only as a ‘Modify files’ action and not as a ‘Delete files/subfolders’ action. I will report this to Microsoft so they can fix this; in the mean time you can remove the ‘Modify files’ right from the participant role if you’re afraid that some of your Workspace members want to take advantage of this loophole.
7 Comments »
Ok, I know that this for the most of you not so interesting but for me as an Dutch man its interesting to see that Groove is in my native language.
What was called workspaces are now called “werkruimte” in Dutch. So I see that Microsoft has changed al the terms that we were used to.
But i’m happy to see that the troubleshooting functionality are still in English. So a home relay device is still a home relay device and not a “thuis doorstuur apparaat”(see below)
see ya,
Jeroen
No Comments »
Today i was at a Groove overview session at Microsoft Tech-Ed: IT-Forum.
The session was great but there are only two more sessions about Groove.
You see a lot of sharepoint sessions but just a few Groove sessions.
This product is new to Microsoft so i hoped that it was more pushed by our MS friends.
Groove looks to be the thick client for sharepoint. So why just not hop on the running train and give more indept sessions about Groove Client an all of the servers that groove has.
The Q and A in the room showed that people really are looking for a product like groove.
So i hope that next year Groove will be the booming product at Tech-Ed.
If i can help i will.
(ok i’m a groove adapt i confess).
See ya
Jeroen Jansen
2 Comments »
Â
Groove EMS 2007 changed the way it shows the user authentication ID.
In the old version 3.1 it showed in the member section the user properties including its authentication ID.
Within the 2007 version this is not visible if the user is already activated.
It will show the ID if the user is an pending member awaiting to be authenticated.
Below you will see screendumps showing the difference:
Groove 3.1 version member information
Groove 2007 member information
Groove 2007 Pending member information
Â
Hopefully it will help you with your search for your Authentication ID
See ya
Jeroen Jansen
PS. Thx Kevin for pointing this out
No Comments »
Last week we made a log about blogging with Word 2007 beta2, now this beta is publicly available at Microsoft.
 http://www.microsoft.com/office/preview/beta/overview.mspx
The requirements to run Office 2007 beta2 are :
Operating systemÂ
Microsoft Windows XP Service Pack (SP) 2 or later or Microsoft Windows Server 2003 (or higher) required
Computer and processorÂ
500 megahertz (MHz) processor or higher; 256 megabyte (MB) RAM or higher; DVD drive; 1 gigahertz (GHz) and 512 MB of RAM or higher is required to run Microsoft Office Outlook 2007 with Business Contact Manager
Hard diskÂ
2 gigabyte (GB) necessary for install; a portion of this disk space will be freed after installation if the original download package is removed from the hard drive
Monitor resolution
Minimum 800×600; 1024×768 or higher recommended
Internet connectionÂ
Broadband connection, 128 kilobits per second (Kbps) or greater, for download and activation of products
Additional components
Microsoft Internet Explorer 6.0 with service packs, Microsoft Exchange Server 2000 or later required for Outlook 2007 users. To install Outlook 2007 with Business Contact Manager, you will need to first install Outlook 2007
Â
Read all requirements (also for Office server) on http://www.microsoft.com/office/preview/beta/sysreq.mspx
No Comments »
Entries (RSS)