<div>
command to find how the user on the database <br />
get-mailbox -database &lt;database&gt; or get-mailbox -server &lt;server&gt;<br />
<br />
get-mailboxdatabasecopy to check which is active and passive<br />
<br />
to fail over for exchange 2013<br />
<br />
<a href="https://technet.microsoft.com/en-us/library/dd298067(v=exchg.150).aspx" rel="ugc">https://technet.microsoft.com/en-us/library/dd298067(v=exchg.150).aspx</a><br />
<a href="http://exchangeserverpro.com/exchange-2013-database-switchover/" rel="ugc">http://exchangeserverpro.com/exchange-2013-database-switchover/</a><br />
<br />
exchange 2010 just google it.<br />
<br />
you also need to change the activation preference on dag for any database on server 307<br />
<br />
<a href="http://sion-it.co.uk/tech/exchange-2010/change-dag-database-activation-preference/" rel="ugc">http://sion-it.co.uk/tech/exchange-2010/change-dag-database-activation-preference/</a>
</div>


<div>
Hi, <br />
<br />
I am not sure if I am understanding your answer. I want to accomplish two different things:<br />
<br />
1. Run a command/script to find disabled mailboxes and move them to an specific server and database for example server307. We have a DAG and multiple DBs A/P. So is there a way to run a single command from a server to look for disabled mailboxes and move them to a different DB/server or should I run the command/script from every individual server using a scheduled task? <br />
<br />
2. There is an scenario that we want to manage, if the users re-hired and come back their mailboxes will be re-enabled and linked to their AD account. If that happens we don't want to the mailboxes to run from server 307 (this is just an journaling server for archival). Is there a way to prevent mailboxes from running in a enabled mode in a specific server or database? <br />
<br />
I hope this clarifies a little better the original question.
</div>


<div>
Let me clarify - the users are disabled from AD and their mailboxes change to whatever state they are placed to once the AD account is disabled. The ps or script will be looking for those mailboxes and moving them to the archive server/database.
</div>


<div>
1. you know disabled mailbox do not equal to disable user?<br />
<br />
anyway, the quickest way is to run powershell<br />
Get-Mailbox | ?{$_.ExchangeUserAccountCo<wbr />ntrol -eq 'AccountDisabled'} | new-moverequest -targetdatabase &quot;server307orwhateveryouput<wbr />&quot;<br />
<br />
you can run this script in a schedule mode.<br />
<br />
to reverse, <br />
Get-Mailbox -database &quot;server307orwhateveryouput<wbr />&quot; | ?{$_.ExchangeUserAccountCo<wbr />ntrol -ne 'AccountDisabled'} | new-moverequest<br />
<br />
<br />
<br />
2. disable user with a mailbox is possible combination. Shared mailbox usually are in this situation. Even you disabled a user, if the mailbox have provided full access/delegation access to some one else, the mailbox is still active. So i am not sure what do you really want to achieve.<br />
<br />
I don't see a business requirement to move those mailboxes to a centralised location. it just create manual process that don't benefit much from administrator point of view. further, when the user been deleted, the mailbox will be deleted. <br />
<br />
Anyway, if you able to have a business requirement maybe i can figure something for you
</div>


<div>
The reason is retention just an internal policy that we need to be in compliance with. We want to move all the mailboxes (disabled users) to an specific server and database. The reason for us to move those mailboxes is because this server is just an archive server that will concentrate disabled user/mailboxes, we can't not delete them because of HIPA policy. <br />
<br />
If the users are re-hired and their accounts re-enabled we do not want their mailboxes to run from the archival server. It will be great if there was a way to prevent those mailboxes from running actively from the archival server, I am not sure if that's possible, however we can run a script and move them out of the server overnight via schedule tasks. <br />
<br />
Another question - Is there a way to run the move command and &quot;move&quot; the mailbox to the server/database with the least amount of mailboxes or the smaller database?
</div>


<div>
by default<br />
<br />
The TargetDatabase parameter specifies the identity of the database that you're moving the mailbox to. If you don't use this parameter, the automatic distribution logic will select a random database from the Active Directory site where you are running the command.<br />
<br />
once a few week, you can run rebalance the database, script provided by microsoft <br />
<a href="http://www.stevieg.org/2010/09/balancing-exchange-databases/" rel="ugc">http://www.stevieg.org/2010/09/balancing-exchange-databases/</a>
</div>


<div>
to move user out, you do the following<br />
<br />
Get-Mailbox -database &quot;server307orwhateveryouput<wbr />&quot; | ?{$_.ExchangeUserAccountCo<wbr />ntrol -ne 'AccountDisabled'} | new-moverequest
</div>


<div>
Hi, <br />
<br />
So a couple of things: <br />
<br />
If AD account is disabled then mailbox becomes orphan. In that scenario - is the mailbox going to be show up as disconnected mailbox in the EMC? <br />
<br />
In our case since we disable the AD accounts but we keep the mailboxes active we just need to move them to the archive server. <br />
<br />
I guess that the best approach will be to run a Powershell command to find disabled AD accounts with active mailboxes and move those mailboxes to the Archive server. <br />
<br />
Any idea how to get that done via Powershell?
</div>


<div>
if AD account is disabled - mailbox will still working. <br />
to make mailbox become orphan, you need to delete the AD account, then it will show up as disconnected mailboxes. <br />
<br />
and yes, to find disabled ad run this, <br />
<br />
Get-Mailbox | ?{$_.ExchangeUserAccountCo<wbr />ntrol -eq 'AccountDisabled'} | new-moverequest -targetdatabase &quot;server307orwhateveryouput<wbr />&quot;<br />
<br />
<br />
to move them out if they are enabled, do the followwing<br />
Get-Mailbox -database &quot;server307orwhateveryouput<wbr />&quot; | ?{$_.ExchangeUserAccountCo<wbr />ntrol -ne 'AccountDisabled'} | new-moverequest
</div>


<div>
Should the Get-mailbox move command be run on each server that's member of the DAG since its looking for disabled AD accounts?
</div>


<div>
get-mailbox command will work on the whole environment. you don't need to run specificly for every server, unless you want to avoid it to run on the archiving server<br />
<br />
Get-Mailbox | ?{$_.ExchangeUserAccountCo<wbr />ntrol -eq 'AccountDisabled' -and $_.database -ne &nbsp;&quot;server307orwhateveryouput<wbr />&quot; } | new-moverequest -targetdatabase &quot;server307orwhateveryouput<wbr />&quot;
</div>


<div>
Actually I believe it's a good idea to run it from the archiving server so that the production servers are not being taxed. <br />
<br />
If I can get the scheduled tasks &nbsp;configured on the archiving servers should I do something like this:<br />
<br />
1.) PS to find disabled AD accounts and moved their mailboxes to the archiving server<br />
<br />
Get-Mailbox | ?{$_.ExchangeUserAccountCo<wbr />ntrol -eq 'AccountDisabled' -and $_.database -ne &nbsp;&quot;server307orwhateveryouput<wbr />&quot; } | new-moverequest -targetdatabase &quot;server307orwhateveryouput<wbr />&quot; <br />
<br />
2.) What's the PS command that I should run from the archiving server to be able to find the enabled AD accounts and move their mailboxes out of the Archiving server to a different server/database? <br />
<br />
Thank you!
</div>


<div>
Ok - I will test it and get back to you. I was reading the following article <a href="https://technet.microsoft.com/en-us/library/ff872148.aspx" rel="ugc">https://technet.microsoft.com/en-us/library/ff872148.aspx</a><br />
<br />
I was wondering if there is a way to prevent mailboxes to be linked to an AD account when they are part of the archiving server and a specific database in that server. For example don't link the AD account to the mailbox if the mailbox is part of server307 and database1.
</div>


<div>
the url you said do not have any information on prevent mailbox to be linked to AD account.<br />
<br />
you only can prevent a mailbox to be created on those database, but not prevent a mailbox with AD account.<br />
in fact if there is a mailbox, there is a AD account. if not it will be become orphaned mailbox (and subject to deletion policy)
</div>


<div>
I see...are you aware of any way to be able to send an email message with the mailboxes that are going to be moved to the archive server? Maybe a way to pipe that into the an email via Powershell? That would be great!
</div>


<div>
sure, you can use this following command<br />
<a href="https://technet.microsoft.com/en-us/library/hh849925.aspx" rel="ugc">https://technet.microsoft.com/en-us/library/hh849925.aspx</a><br />
<br />
i am not going to elaborate on such but you can achieve it in many ways on what you want upon your business requirement<br />
<br />
but move a mailbox is definitely have minimal impact to end user. it is online move instead of a offline move.
</div>


<div>
I am having a hard time getting the mail notification to work. Any chance you help out? Thank you!
</div>


<div>
probably it is best to put out what you have done so i can advise you easily?<br />
<br />
<br />
<br />
if not, it is best to open a new question as it attract better resource to work on this.
</div>


<div>
<div class="content wysiwyg-content">
I am trying to figure out a way to move the disabled mailboxes from the server/database that have been disabled to server 307 database-03. Maybe via powershell and schedule task? Anyone has any suggestions on how to get this accomplished? &nbsp;<br />
<br />
We have a DAG so the databases are active passive in multiple servers, I am guessing the PS should be able to find out if the mailbox is running from the active DB? <br />
Also is there anyway to set a limit on all mailboxes on server 307 (they are disabled) so that if a user gets re-enabled, they won’t be using this server 307 as a “production” server. How can this be accomplished?
</div>
</div>


I am trying to figure out a way to move the disabled mailboxes from the server/database that have been disabled to server 307 database-03. Maybe via powershell and schedule task? Anyone has any suggestions on how to get this accomplished?  

We have a DAG so the databases are active passive in multiple servers, I am guessing the PS should be able to find out if the mailbox is running from the active DB? 
Also is there anyway to set a limit on all mailboxes on server 307 (they are disabled) so that if a user gets re-enabled, they won’t be using this server 307 as a “production” server. How can this be accomplished?

Exchange move disabled mailboxes - Powershell / Set a limit to prevent disabled mbx to be enabled on a specific server

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

Windows PowerShell is a task automation and configuration management framework from Microsoft, consisting of a command-line shell and associated scripting language built on the .NET Framework. PowerShell provides full access to the Component Object Model (COM) and Windows Management Instrumentation (WMI), enabling administrators to perform administrative tasks on both local and remote Windows systems as well as WS-Management and Common Information Model (CIM) enabling management of remote Linux systems and network devices.

Powershell

Within Internet message handling services (MHS), a message transfer agent or mail transfer agent (MTA) or mail relay is software that transfers electronic mail messages from one computer to another using a client–server application architecture. A MTA implements both the client (sending) and server (receiving) portions of the Simple Mail Transfer Protocol (SMTP). The terms mail server, mail exchanger, and MX host may also refer to a computer performing the MTA function. The Domain Name System (DNS) associates a mail server to a domain with mail exchanger (MX) resource records containing the domain name of a host providing MTA services.