08-27-2010 06:43 AM
Solved! Go to Solution.
03-25-2011 08:21 AM
Nope and i don't think it will ever change to be honest
08-27-2010 06:52 AM
08-27-2010 07:17 AM
08-27-2010 08:06 AM
08-27-2010 08:31 AM
08-31-2010 01:15 AM
10-18-2010 01:07 PM
Any idea when this is going to be resolved, re: shared VV are read only? that's not the advertised functionality, and what would be the bloody point of a shared vault with full read/write/delete access. Users can't even create a folder to organize data in the shared vault mailbox.
10-18-2010 01:20 PM
I will mail Product Management internally, however, in the Setting Up Exchange Server Archiving Guide that comes on the media, it does say it's read-only for secondary mailbox/vault/archives :
Page 67
<snip>
The user can synchronize archives other than their primary mailbox archive to
the Vault Cache, if they have the necessary permissions. Each archive that is
synchronized to a Vault Cache has its own Virtual Vault, if Virtual Vault is enabled.
In Virtual Vault, access to archives other than the user's primary mailbox archive
is read-only.
</snip>
10-18-2010 01:42 PM
So adding permissions to the Vault Mailbox archive are meaningless then? Seems kind of odd that this would be by design. So a shared Vault Mailbox is only good for importing a bunch of PST's perhaps, and then viewing them.
10-18-2010 01:54 PM
when you say shared vault, you mean someone elses vault that you have access to or a shared archive? because shared archives are unstructured and don't allow for folders any way.
10-18-2010 02:06 PM
Yeah, I'm talking about Shared Archives, and just noticed about not being able to create folders in such an archive.
I have a client that was hoping to use the Shared Archives for Projects and store project related emails and materials but it's becoming a rather pain in the ... Drag and drop doesn't work, and only "Store in Vault" and selecting that Vault appears to work.
Guess they needed to have some room for improvement for EV10, hint hint.
So, probably do do what they want to do, is have a shared Mailbox that is being archived, Add the additional mailbox to the Outlook Profile (after granting full access), and setting permissions on the Vault archive to allow the users to be able to sync and get the virtual vault. Plus set up a policy to archive everything asap...
now repeat for 1900 projects, with 10,000 users...
Must remember, can't add structure to unstructured data... new term to replace the old addage that you can't make a silk purse out of a sow's ear....
10-18-2010 02:22 PM
try creating a new shared archive and immediately set the structured column from 0 to a 1, thats what we're doing with out PST imports in to a shared archive, the downside being that some of the naming conventions in AE will show strangely, for instance you will now see a Top Of Information Store where as regular archives will not show that, but again thats because you are changing how a shared archive works
it's worth giving that little hack a try, worst case scenario is it doesnt work or doesnt work well enough for your needs
10-19-2010 08:29 AM
FYI --->
From an Enterprise Vault Engineering point of view, I wouldn't recommend database modifications such as the ones that JesusWept2 outlined.
10-19-2010 08:31 AM
Agreed it is not a supported configuration in the slightest (There are technotes out there which say its not supported) and can have adverse effects, especially in the future if functionality changes and what not, so is not advisable
03-25-2011 08:14 AM
I am getting ready to upgrade from 8.04 to 9.02... Does anyone know if this functionality has changed?
03-25-2011 08:21 AM
Nope and i don't think it will ever change to be honest
03-25-2011 08:22 AM
Seems silly.
03-25-2011 09:41 AM
JW2 is right, the functionality hasn't changed, and it won't be changing in EV 10 either.
08-10-2011 04:21 PM
If you create an Outlook profile that opens ONLY the shared mailbox you're trying to manage, you can modify the Vault content - move / modify / delete / etc.
08-10-2011 11:12 PM
Yep NaturesRevenge, that's the only way to do it currently.