Unable to open shortcuts when moved/copied to shared mailbox or public folder
I need a solution to prevent users to move or copy EV shortcuts to shared mailboxes or public folders.
Since the Enterprise Vault archive task updates only moved/copied items within the own archive, we see often permission problems, when users try to open shortcuts in shared mailboxes. The cause of this is always the same: moved or copied shortcuts from an users mailbox. It is not easy to identify whether the shortcuts are ok, or not, or to which archive they belong, and Enterprise Vault does not handle the “bad” shortcuts as orphaned ones.
Several technotes says: you have to train the users to prevent this situation. But since it is a very common way to share information by moving or copying mail items between mailboxes, the users are doing this as well with shortcuts. Why is Enterprise Vault not able to handle this correctly?
So we need at least a solution, which allows users to move or copy shortcuts within their own mailboxes, but not to shared mailboxes or public folders. How can we achive this?
We are using V9.0.2 and Outlook 2010 and plan to upgrade to V11; does V11 still have the same behavior?
The behavior is the same in EV 11. It really comes down to an Exchange issue to prevent the message class from being copied into the public folder. I am pretty sure you can block messages from public folders based on subject but I don't think you can block them based on message class.