Forum Discussion
CUCOOPE
Nov 12, 2021Copper Contributor
Exchange: The execution of cmdlet Set-SyncMailUser failed.
Hi. We have a hybrid environment and recently we've encountered a problem on converting a disabled email account to shared mailbox. It was shown this error message: Exchange: The execution of ...
- Nov 17, 2021
Thierry Chapuisat At last I hard-matched the guid between Azure and the on-prem ad.
Thierry Chapuisat
Nov 12, 2021Brass Contributor
Hi,
Did you try the Scenario 1 ?? :
https://docs.microsoft.com/en-us/exchange/troubleshoot/user-and-shared-mailboxes/mailbox-exists-exo-onpremises
Did you try the Scenario 1 ?? :
https://docs.microsoft.com/en-us/exchange/troubleshoot/user-and-shared-mailboxes/mailbox-exists-exo-onpremises
- CUCOOPENov 12, 2021Copper Contributor
Thierry Chapuisat I guess so since the cmdlet in scenario 1 is similar to what I followed in the guide. However, the cmdlet
Enable-RemoteMailbox "user identity" -RemoteRoutingAddress "user@contoso.mail.onmicrosoft.com"Failed and the error
This task does not support recipients of this type. The specified recipient <user> is of type RemoteUserMailbox. Please make sure that this recipient matches the required recipient type for this task.will be shown.
- Thierry ChapuisatNov 12, 2021Brass ContributorYo ca try to change manually the recipient type display and the remote recipient type on your local ad.
http://www.mistercloudtech.com/2016/05/18/reference-to-msexchrecipientdisplaytype-msexchrecipienttypedetails-and-msexchremoterecipienttype-values/- CUCOOPENov 17, 2021Copper Contributor
Thierry Chapuisat At last I hard-matched the guid between Azure and the on-prem ad.