Exchange 2013 migration: final steps!
Good morning, all! Environment is two sites, one legacy Exchagne 2010 standalone server at each site (one about to be decomissions, other close to it), and an Exchange 2013 DAG spanning both sites, one Ex2013 server per site with its own client database (sites replicating to each other). Just about all of our migration from 2010 to 2013 has been completed, and I'm almost at the final steps. The public folder migration is the last step, but the below question arose.
All user mailboxes have been migrated successfully (for the most part), and in looking at the list of remaining mailboxes I see these:
x Discovery Search Mailbox (Discovery Mailbox)
x Microsoft Exchange (System Mailbox)
x Microsoft Exchange Approval Assistant (System Mailbox)
x Microsoft Exchange Approval Assistant (FederatedEmail)
Do these mailboxes need to be migrated to Exchange 2013? I haven't seen these documented anywhere in the migration process except for one blog, and I'm hesitant to migrate them based on just the one resource. I'm assuming these system mailboxes already exist on our 2013 system, and I don't want to compromise an already well-running Ex2013 DAG by moving over some kind of legacy mailbox that will just sit there. On a side note, I'm not sure what the "Federated Email" entry is there for; we don't have a Federation set up in our 2012 forest (2008 functional level).
Comments welcome! Thanks!
SteveInNV
All user mailboxes have been migrated successfully (for the most part), and in looking at the list of remaining mailboxes I see these:
x Discovery Search Mailbox (Discovery Mailbox)
x Microsoft Exchange (System Mailbox)
x Microsoft Exchange Approval Assistant (System Mailbox)
x Microsoft Exchange Approval Assistant (FederatedEmail)
Do these mailboxes need to be migrated to Exchange 2013? I haven't seen these documented anywhere in the migration process except for one blog, and I'm hesitant to migrate them based on just the one resource. I'm assuming these system mailboxes already exist on our 2013 system, and I don't want to compromise an already well-running Ex2013 DAG by moving over some kind of legacy mailbox that will just sit there. On a side note, I'm not sure what the "Federated Email" entry is there for; we don't have a Federation set up in our 2012 forest (2008 functional level).
Comments welcome! Thanks!
SteveInNV
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER