locked
Move autosuspended Mailbox to another DB RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello Everyone,

    Currently we do have scenario, where all the users mailboxes are moved and autosuspended from Exchange 2010 to exchange 2016 on certain DB (DB01 to DB10), but the customer wants to move all the prestaged users from DB (DB05 to DB10) to another DB (DB01 to DB04). 

    Firstly, i would like to understand if moving is possible and what are the implication doing the move.

    Thanks,

    Raj 


    • Edited by Troy08 Friday, March 10, 2017 7:26 AM
    Friday, March 10, 2017 7:25 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Troy,

    If I got you question right, you want to change the destination of a mailboxmove that is on going, right?

    If that is the question, if you started the move from the 2016, you could try the following cmdlet:

    Set-MoveRequest -Identity User -TargetDatabase NewTargetDatabase

    But pay attention that this will only work if the status of the move is Queued, to check the status of the move, execute this cmdlet.

    Get-MoveRequest -Identity User

    If this cmdlet doens't work, your only option is to Complete the move and start a new one.


    Por favor, se te ajudei, não esqueça de marcar como resposta. Acesse meu blog: http://msexperts.blog.br ____________________________________________________________ Please remember to mark the replies as answers if they help.

    • Proposed as answer by Jason.Chao Monday, March 13, 2017 7:01 AM
    • Marked as answer by Troy08 Monday, June 19, 2017 5:50 AM
    Friday, March 10, 2017 6:03 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Troy,

    If I got you question right, you want to change the destination of a mailboxmove that is on going, right?

    If that is the question, if you started the move from the 2016, you could try the following cmdlet:

    Set-MoveRequest -Identity User -TargetDatabase NewTargetDatabase

    But pay attention that this will only work if the status of the move is Queued, to check the status of the move, execute this cmdlet.

    Get-MoveRequest -Identity User

    If this cmdlet doens't work, your only option is to Complete the move and start a new one.


    Por favor, se te ajudei, não esqueça de marcar como resposta. Acesse meu blog: http://msexperts.blog.br ____________________________________________________________ Please remember to mark the replies as answers if they help.

    • Proposed as answer by Jason.Chao Monday, March 13, 2017 7:01 AM
    • Marked as answer by Troy08 Monday, June 19, 2017 5:50 AM
    Friday, March 10, 2017 6:03 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Troy,

    If your move request is in queue  status then only below parameter ( Set-MoveRequest  )  work.

    for auto-suspend request you have to remove those request and create new batch or request. 

    • Proposed as answer by Hardik_Patel_ Monday, March 27, 2017 1:00 PM
    Sunday, March 12, 2017 5:47 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Troy08,

    I know this is an old post but I too ran into this sticky predicament  

    I altered my move request with the below params

    Set-MoveRequest -Identity Mailbox -SuspendWhenReadyToComplete:$false -PreventCompletion:$false

    The ran

    Resume-MoveRequest -Identity Mailbox

    and Voila it completed.

    Get-MoveRequest | Get-MoveRequestStatistics

    DisplayName                StatusDetail    TotalMailboxSize                        TotalArchiveSize PercentComplete
    -----------                     ------------       ----------------                          ----------------    ---------------
    Mailbox                          Completed    925.9 MB (970,868,902 bytes)                            100


    Tuesday, March 19, 2019 7:04 PM