如何使用New-MaiboxRestoreRequest

ZeLin Zhu 21 Reputation points
2021-06-22T09:46:23.907+00:00

大家好,我之前使用exchange2013,这台服务器中病毒后故障了,我重新搭了一台,并根据说明进行了还原,
https://learn.microsoft.com/en-us/powershell/module/exchange/new-mailboxrestorerequest?view=exchange-ps

就是在使用New-MaiboxRestoreRequest的时候卡住了,在exchange management shell中,运行这个命令,提示我没有此命令,
这个命令应该怎么安装,加载阿?

Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,328 questions
0 comments No comments
{count} votes

Accepted answer
  1. Xzsssss 8,861 Reputation points Microsoft Vendor
    2021-06-23T01:43:55.97+00:00

    Hi @ZeLin Zhu ,

    Good morning!

    Welcome to Q&A forum and thanks for your question! But please be aware that this forum is an English forum and we do not support Chinese threads.
    Basically you could translate your question to English or post your issue on https://social.technet.microsoft.com/Forums/zh-CN/home?forum=exchangeserverzhchs, this is for our Chinese users and we could provide you a better service.

    As for your question, please first check if you have the Disaster Recovery permission, it is contained in Organization Management role.
    Then please provide the cmdlet you used.
    Or try the following cmdlet:

    New-MailboxRestoreRequest -SourceDatabase "MBD01" -SourceStoreMailbox "Mailbox" -TargetMailbox user@Company portal .com -AllowLegacyDNMismatch

    108382-image.png

    Thanks for your understanding & have a good day!

    Best regards,
    Lou


    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. ZeLin Zhu 21 Reputation points
    2021-06-24T01:17:29.32+00:00

    thank for help!
    The problem has been solved. The cause of the malfunction is that I copied the code on the web page, and the code is not in the right format.
    When I type manually in PowerShell, I have no problem.