Consider the following scenario:
- You have an Microsoft Exchange Server 2013 or 2016 environment that contains two or more mailbox servers.
- Your Active Directory Forest contains two or more domains.
- Your Exchange Servers and user objects are located in different Active Directory domains.
- You manage your recipients through Exchange Management Shell (EMS) by setting “Set-ADServerSettings -ViewEntireForest $true”.
In this scenario, when you run a PowerShell cmdlet/parameter combination, the cmdlet is unsuccessful, and you receive an error message that resembles the following:
Error on proxy command 'Set-Mailbox -Identity:'email@example.com' -LitigationHoldEnabled:$False' to server Ex01.corp.contoso.com: Server version
15.0x.xxxx.xx, Proxy method RPS:
The operation couldn't be performed because object 'Ex02.firstname.lastname@example.org' couldn't be found on 'Ex02.corp.munich.contoso.com'..
+ CategoryInfo : NotSpecified: (:) [Set-Mailbox], CmdletProxyException
+ FullyQualifiedErrorId : Microsoft.Exchange.Configuration.CmdletProxyException,Microsoft.Exchange.
The following are some cmdlet/parameter combinations that may be affected:
Set-Mailbox -LitigationHoldEnabled $false
This behavior is by design when the specified mailbox is located on a different server than the server that EMS is connected to.
To work around this behavior, specify the -DomainController parameter with the cmdlet. For example, specify a Domain Controller from the Active Directory domain where the associated user object is located, such as the following:
Set-Mailbox -Identity:'email@example.com' -LitigationHoldEnabled:$False -DomainController dc1.sub.corp.contoso.com