Microsoft Office Tutorials and References
In Depth Information
Decommissioning on-premises Exchange
6. Go back to the Exchange Management Shell window, and enter the following
command to set the value of the ExchangeGUID property on the on-premises remote
Set-RemoteMailbox <alias of cloud mailbox to move> -ExchangeGUID <GUID>
7. Start an unscheduled directory synchronization process using the
StartOnlineCoexistenceSync command. Refer to Chapter 4, “Directory synchronization”, if
you need a refresher on how to do this.
8. After directory synchronization is complete, you can follow the steps outlined in the
preceding section to move the mailbox from the cloud back to on-premises.
Decommissioning on-premises Exchange
The subject of decommissioning on-premises Exchange is most applicable to
organizations that have created an Exchange hybrid environment. It might seem logical to consider
decommissioning all on-premises Exchange after all mailboxes and email workloads have
been migrated. However, it is important to note that if your organization wants to manage
Exchange Online with the EMC, a minimum of one Exchange on-premises CAS must still
exist in the forest.
If directory synchronization is implemented, Active Directory is then the source of
authority, and Microsoft recommends not removing the last Exchange 2010 on-premises server.
By removing the last on-premises Exchange server, you will be unable to make changes
to the mailbox objects in Exchange Online because the source of authority is defined as
The bottom line is that you should keep one Exchange 2010 CAS on-premises, for now. A
more detailed discussion about this topic is covered by the Microsoft Exchange team on
their team blog referenced in the following Inside Out sidebar.
INSIDE OUT Microsoft recommendation on decommissioning Exchange
You can read about the Exchange team’s recommendation to maintain on-premises
Exchange 2010 CAS and the reasons on the Exchange Team Blog located at http://
Search JabSto ::

Custom Search