kdababy.blogg.se

Find and delete duplicates in outlook 2016 powershell
Find and delete duplicates in outlook 2016 powershell





find and delete duplicates in outlook 2016 powershell

+ FullyQualifiedErrorId : 10E0541D.SetMailbox + CategoryInfo : NotSpecified: (WC:MailboxIdParameter), TaskArgumentException

find and delete duplicates in outlook 2016 powershell

If you try to turn it on for any other type of mailbox, you will still run into the familiar error message: MessageCopyForSentAsEnabled can only be set on shared mailboxes or user mailboxes. To turn the settings on for all user and shared mailboxes: Get-Mailbox -RecipientTypeDetails UserMailbox,SharedMailbox | Set-Mailbox -MessageCopyForSendOnBehalfEnabled $true -MessageCopyForSentAsEnabled $true To turn the settings on for all user mailboxes, use: Get-Mailbox -RecipientTypeDetails UserMailbox | Set-Mailbox -MessageCopyForSendOnBehalfEnabled $true -MessageCopyForSentAsEnabled $true For example, to turn this on for a single user mailbox you can use: Set-Mailbox HuKu -MessageCopyForSendOnBehalfEnabled $true -MessageCopyForSentAsEnabled $true Well, no more! The parameters can now be used for both shared and user mailboxes. This in turn meant that we still had to address issues with delegates for user mailboxes, say a secretary sending mail on behalf of a VP.

find and delete duplicates in outlook 2016 powershell find and delete duplicates in outlook 2016 powershell

+ FullyQualifiedErrorId : 36931497.SetMailbox + CategoryInfo : NotSpecified: (huku:MailboxIdParameter), TaskArgumentException MessageCopyForSentAsEnabled can only be set on shared mailboxes If you tried to configure the setting for any user mailbox, you were greeted by the following error message: PS C:\> Set-Mailbox huku -MessageCopyForSendOnBehalfEnabled $true -MessageCopyForSentAsEnabled $true For a brief overview on the different methods and details on said parameters you can refer to the EHLO blog post here: Īs you can see from the article above, while the new method proved very useful and easy to control, it was only available for shared mailboxes. Over the course of the last few years and Exchange versions, Microsoft offered us different workarounds for this issue, the latest one being the use of the MessageCopyForSentAsEnabled and MessageCopyForSendOnBehalfEnabled parameters. One of the major issues with it was the fact that any messages send on behalf of say a shared mailbox weren’t copied to the mailbox, thus other people working with it were unaware of the action. The ability to send messages on behalf of somebody else has been around for a long time, but it has it quirks.







Find and delete duplicates in outlook 2016 powershell