Prior to Exchange 2010 SP2 RU4, the only way to control where sent items where placed was to use the ‘DelegateSentItemStyle’ registry tweak. This had to be done on every single PC where you wanted this to happend, and it was only working for cached Exchange mode.
Then in Exchange 2010 SP2 RU4 we got the new feature to control where to place “Sent Items”. That said, the function has a bug but more about that later.
The cmdlet is Set-MailboxSentItemsConfiguration
Lets make an example:
In this company we have a shared mailbox “Job”. First we check the setting with
Then we change the behaviour for what will happend when the users sends mails as the mailbox “Job”.
Set-MailboxSentItemsConfiguration job -SendAsItemsCopiedTo SenderAndFrom
Now messages sent as this mailbox are saved both in the Sent Items folder of the actual user that sent the message and the Sent Items folder of this mailbox.
I changed this at a customer for 800+ shared mailboxes and what happend? A lot of users called and wanted the mail ONLY to be placed in the “sent items” of the shared mailbox.
Now comes the fun part. You can use the “Set-MailboxSentItemsConfiguration job -SendAsItemsCopiedTo From” – but it doesn’t work. Why? According to inside information this is a bug. If you call Microsoft Support, they will tell you that this is for future use, which is also what you can read at technet in the provided link in the beginning og this post.
But if it was for future use, why should we then be able to use this parameter, and why should it be possible for users to change it in the OWA?
Your next question might be, “what about the deleted items?”. That was what I asked myself. Unfortunately we haven’t got a Set-MailboxDeletedItemsConfiguration neighter in Exchange 2013. You still have to use the registry tweak for that “DelegateWasteBasketStyle”
But be careful when using this. You can read my blogpost about this here.
This was my first blogpost – hope you liked it.