Quantcast
Channel: Exchange Server 2013 - Setup, Deployment, Updates, and Migration forum
Viewing all articles
Browse latest Browse all 7129

After Using Database Portability to Move to New Server Unable to Decomission Old Server

$
0
0

I have a failing Exchange 2013 server.  I used database portability to move the failing server's data base to a new Exchange 2013 server.  This process essentially involves repairing the database (which was successful) and copying it to the new server and mounting it.  The copy of the database on the failing server is left in a dismounted state.  At the end of the portability process, the attributes of the users are updated so that their mailboxes are accessed from the database on the new server.

When I attempt to remove Exchange from the failing server, I am informed that the database contains "one or more mailboxes, mailbox plans, archive mailboxes, public folder mailboxes, or arbitration mailboxes."  Using various get- powershell commands, I discovered that the Arbitration mailboxes still point to the old server.  (I don't have any public folders or archive mailboxes.)

I don't want to "move" the Arbitration mailboxes, because they should already exist on the new server's database.  So what do I do to get the Arbitration user accounts (I guess they are accounts) to point to the mailboxes on the new server?

More broadly, are there any other snags I'm going to run into while trying to decommission this server?



Viewing all articles
Browse latest Browse all 7129

Trending Articles