This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(76.8, 75%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBE%3C/text%3E%3C/svg%3E)
I am reaching out to the community as Microsoft has ended support two days ago for any help / guidance with Exchange Server 2013. We are looking to remove all the local Exchange servers (we have server roles for CAS and MBX). From what I've already read through on other threads, is that we need to remove the DAG and any associated mailboxes that exist on-prem. However, I don't have clarity on if having CAS and MBX not on the same server poses a problem from the MS comment "Do not uninstall the last server" (https://learn.microsoft.com/en-us/exchange/manage-hybrid-exchange-recipients-with-management-tools). Does it matter which server is the "last" server part of Exchange. There is another server that I plan to have for recipient management (Exchange Server 2019 Tools).
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(284.8, 17%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EYS%3C/text%3E%3C/svg%3E)
Hi @Brandon Epler ,
However, I don't have clarity on if having CAS and MBX not on the same server poses a problem from the MS comment "Do not uninstall the last server" (https://learn.microsoft.com/en-us/exchange/manage-hybrid-exchange-recipients-with-management-tools). Does it matter which server is the "last" server part of Exchange
Per my understanding, the method in the document is not applicable to your scenario, as one of its requirements is "You're running only one on-premises Exchange server and only for recipient management.":
Given this and also considering that Exchange 2013 has reached the end of support, personally I'd suggest migrating to Exchange 2019 first and then use the new method in the aforementioned document to shut down the last Exchange server.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment". Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hello, Thank you for the response. As I mentioned, the plan will be to have an on-prem Exchange server running 2019 management tools for recipient management. When that condition is met, the only server existing would be Exchange 2019 (management tools). All other servers would be removed from the environment (CAS and MBX) and we'd only be left with the one server.
Hi @Brandon Epler , Thanks for the clarification. This should work, but as mentioned in the linked article above, the last Exchange server can only be shut down rather than uninstalled. And regarding your concern about CAS and MBX roles on different servers, according to this blog, I suppose the las server role should be a CAS role.