none
power shell not find two users RRS feed

  • Question

  • I have two server exchange 2007 and migrated mailbox to new 2013. Part maibox I must run cmdlet "Set-MoveRequest <user@domain> –BadItemLimit 50" and move all successfully. But two users power shell not know say "Couldn't find a move request that corresponds to the specified identity..." This users are usualy created and not set anything to other users.
    Thursday, October 1, 2015 7:50 AM

Answers

  • Hi,

    Please can you confirm that the destination database is on Exchange 2013. I can see that you are moving the users to an Exchange 2007 mailbox database. 

    To get a list of mailbox databases on your Exchange 2013 server, run this command:

    Get-MailboxDatabase -Server Exchange2013Server1

    You then need to specify to move the mailboxes to one of these database. Replace "DB01" in the command below with one of the mailbox databases that were listed in the command above:

    New-MoveRequest -Identity 'tony@alpineskihouse.com' -TargetDatabase "DB01" -AcceptLargeDataLoss -BadItemLimit 50

    Let me know if this answers your question. 

    Thanks.


    Mark Gossa

    MCSE 2003, MCITP Enterprise Administrator 2008 R2, MCSA 2012 R2, MCTS Exchange 2010

    Blog: http://markgossa.blogspot.com

    Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

    • Proposed as answer by Mark Gossa Tuesday, October 6, 2015 7:00 PM
    • Marked as answer by mdvorak72 Wednesday, October 7, 2015 10:00 AM
    Monday, October 5, 2015 1:58 PM

All replies

  • Hi,

    To move a user from Exchange 2013 you can use the Exchange Admin Center (EAC) or the below command:

    New-MoveRequest -Identity 'tony@alpineskihouse.com' -TargetDatabase "DB01" -AcceptLargeDataLoss -BadItemLimit 50

    More information here: https://technet.microsoft.com/en-us/library/dd351123(v=exchg.150).aspx

    To use the EAC, see below:

    1. In the EAC, navigate to Recipients > Migration, and then click Add Add Icon.
      In the New local mailbox move wizard, select the user you want to move click OK and then click Next.
      On the Move configuration page, specify a name for the new batch. Select which options you want for the archive mailbox, and mailbox database location and click New.

    More information here: https://technet.microsoft.com/en-us/library/jj150487(v=exchg.150).aspx

    The problem you have is that Set-MoveRequest modifies an existing move request but it cannot find the move request because one doesn't exist. New-MoveRequest is used to create a new move request and you can set the BadItemLimit as per above. 

    Let me know if this answers your question. 

    Thanks.


    Mark Gossa

    MCSE 2003, MCITP Enterprise Administrator 2008 R2, MCSA 2012 R2, MCTS Exchange 2010

    Blog: http://markgossa.blogspot.com

    Posts are provided “AS IS” without warranty of any kind, either expressed or implied.


    Thursday, October 1, 2015 3:43 PM
  • power shell say: + CategoryInfo: InvalidArgument: (user@domain.com:MailboxOrMailUserIDParameter) [New/MoveReguest], RecipientTaskException

    Monday, October 5, 2015 10:32 AM
  • Hi,

    Please can you let me know the exact command you are using (but obviously replace with user@domain.com etc). Also, please post the entire PowerShell error.

    Thanks.


    Mark Gossa

    MCSE 2003, MCITP Enterprise Administrator 2008 R2, MCSA 2012 R2, MCTS Exchange 2010

    Blog: http://markgossa.blogspot.com

    Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

    Monday, October 5, 2015 11:37 AM
  • [PS] C:\Windows\system32>New-MoveRequest -Identity 'user@domain.xxx' -TargetDatabase "MAIL2\Storage3\Mailbox Database" -AcceptLargeDataLoss -BadItemLimit 50
    WARNING: When an item can't be read from the source database or it can't be written to the destination database, it will be considered corrupted. By specifying a non-zero BadItemLimit, you are requesting Exchange not copy such items to the destination mailbox. At move completion, these corrupted items will not be available at the destination mailbox.
    The Mailbox database "Mailbox Database" is not the same version as the cmdlet.
        + CategoryInfo          : InvalidArgument: (user@domain.xxx:MailboxOrMailUserIdParameter) [New-MoveRequest], RecipientTaskException
        + FullyQualifiedErrorId : [Server=SRV-15-EXCH,RequestId=a9dec561-f572-4429-830f-e911428bcba6,TimeStamp=5. 10. 2015
        11:50:11] [FailureCategory=Cmdlet-RecipientTaskException] 825608F7,Microsoft.Exchange.Management.RecipientTasks.N  ewMoveRequest
        + PSComputerName        : srv-15-exch.domain.xxx

    • Edited by mdvorak72 Monday, October 5, 2015 11:58 AM
    Monday, October 5, 2015 11:55 AM
  • Hi,

    Please ensure that you're running the command on an Exchange 2013 server. 

    Thanks.


    Mark Gossa

    MCSE 2003, MCITP Enterprise Administrator 2008 R2, MCSA 2012 R2, MCTS Exchange 2010

    Blog: http://markgossa.blogspot.com

    Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

    Monday, October 5, 2015 1:07 PM
  • Yes, I run command from Exchange Management Shell on Exchange server 2013 SP1 on MS Windows server 2012 R2. Same way I move problem few users from this db "Mailbox Database" on Exchange server 2007 to db "Mailbox Database 0" on new server. When I run Get-MailboxDatabase ("Mailbox Database" | Get-mailbox command) command list this last users.

    Run migration from EAC not move this users too and log is clear.

    Monday, October 5, 2015 1:32 PM
  • Hi,

    Please can you confirm that the destination database is on Exchange 2013. I can see that you are moving the users to an Exchange 2007 mailbox database. 

    To get a list of mailbox databases on your Exchange 2013 server, run this command:

    Get-MailboxDatabase -Server Exchange2013Server1

    You then need to specify to move the mailboxes to one of these database. Replace "DB01" in the command below with one of the mailbox databases that were listed in the command above:

    New-MoveRequest -Identity 'tony@alpineskihouse.com' -TargetDatabase "DB01" -AcceptLargeDataLoss -BadItemLimit 50

    Let me know if this answers your question. 

    Thanks.


    Mark Gossa

    MCSE 2003, MCITP Enterprise Administrator 2008 R2, MCSA 2012 R2, MCTS Exchange 2010

    Blog: http://markgossa.blogspot.com

    Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

    • Proposed as answer by Mark Gossa Tuesday, October 6, 2015 7:00 PM
    • Marked as answer by mdvorak72 Wednesday, October 7, 2015 10:00 AM
    Monday, October 5, 2015 1:58 PM
  • With specified "DB 01" power shell know this user and command is successfull. I now run same migration task from EAC but nothing change, user is still on old DB. But today morning is user suddenly with new DB.. Thanks wery much for help
    Wednesday, October 7, 2015 10:00 AM