I have read articles on how to prepare and put an E2K13 DAG member into maintenance mode.  I have just completed putting a DAG member into maintenance mode; however, when I ran cmdlet: Set-MailboxServer <servername>  -DatabaseCopyActivationDisabledAndMoveNow   which is supposed to take care of activating databases on the other node member , it did not work and I had to manually move the databases to another node member.

Am I running the correct cmdlet or can you tell me what I may have done wrong:

Articles read: 
http://blogs.technet.com/b/nawar/archive/2014/03/30/exchange-2013-maintenance-mode.aspx

http://technet.microsoft.com/en-us/library/dd298065(v=exchg.150).aspx#Pm

http://vanhybrid.com/2013/11/28/script-putting-exchange-server-2013-into-maintenance-mode/

http://letsexchange.blogspot.com/2013/03/exchange-2013-maintenance-mode.html

Hi,

Whats the error when you run that cmdlet?

Set-MailboxServer <servername>  -DatabaseCopyActivationDisabledAndMoveNow  $True

Note: Setting this parameter -DatabaseCopyActivationDisabledAndMoveNow  to $true won't cause databases to move to a server that has the DatabaseCopyAutoActivationPolicy parameter set to Blocked.

Before running that cmdlet, please check the type of automatic activation available for mailbox database copies on the specified Mailbox server.

Get-MailboxServer <ServerName> | Select DatabaseCopyAutoActivationPolicy

Best Regards.

I followed the process order from these technotes.

http://blogs.technet.com/b/nawar/archive/2014/03/30/exchange-2013-maintenance-mode.aspx

http://technet.microsoft.com/en-us/library/dd298065(v=exchg.150).aspx#Pm

http://vanhybrid.com/2013/11/28/script-putting-exchange-server-2013-into-maintenance-mode/

http://letsexchange.blogspot.com/2013/03/exchange-2013-maintenance-mode.html

Prior to doing the MoveNow   I did check the databasecopyautoactivationpolicy and it was unrestricted with no block.

Next maintenance I will check again one more time and resubmit if I still have the issue