update microsoft exchange 1029 to microsoft exchange SE

Please note that our forum is a public platform, and we will modify your question to hide your personal information in the description. Kindly ensure that you hide any personal or organizational information the next time you post an error or other details to protect personal data.  

Hi @Tien Ngo

Thank you for sharing your concern.  

First, I would like to clarify that this is a user‑to‑user support forum. The moderators participating here do not have access to backend systems, nor can we directly intervene in Microsoft product functionality. Our role is limited to providing technical guidance and sharing best‑practice recommendations based on reported issues, requests, and scenarios. 

I understand that you are requesting Engineer Support to assist with upgrading your DGG Exchange Server 2019 to Exchange Server SE. However, due to my role and permission scope, I am unable to directly check your case status or transfer your request to the engineering team. 

Currently, the support team may be handling a large number of tickets or in the process of assigning your request to the appropriate engineer. I kindly ask for your patience and recommend allowing them a little more time to complete the assignment. 

I hope your case will be resolved soon. Thank you for your understanding. 

If you have any additional concerns, feel free to comment below. I would be more than happy to assist. 

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. 

I have Case [Moderator note: personal info removed]   Your question was succe... - TrackingID#[Moderator note: personal info removed] 

i need some one call me.

To complete the upgrade of the second Exchange Server 2019 to Exchange Server Subscription Edition (SE), use a supported upgrade path and, for direct assistance, re-engage Microsoft Support referencing the existing work done on the first server.

1. Confirm that the second server is eligible for in-place upgrade

• Exchange Server SE RTM is code-equivalent to Exchange Server 2019 CU15, with only licensing text, product name, and build number changed.
• An in-place upgrade is supported only from Exchange Server 2019 CU14 or CU15.
• If the second server is on an earlier CU, first update it to CU14 or CU15, then proceed to Exchange SE.

2. Decide on the upgrade method for the second server

• In-place upgrade (preferred when possible):
  • From Exchange 2019 CU14 or CU15, run the Exchange SE setup directly on the existing server, just as when installing a cumulative update.
  • Follow the same best practices as documented in “Upgrade Exchange to the latest Cumulative Update.”
• Legacy upgrade (if changing hardware/OS or if in-place is not suitable):
  • Install a new Exchange SE server into the organization.
  • Move all mailboxes and services from the second Exchange 2019 server to the SE server.
  • Uninstall/decommission the old 2019 server after migration.

3. Validate prerequisites on the second server

• Ensure Active Directory meets the “requirements for Exchange 2019 and SE.”
• Confirm the operating system is listed under “supported operating systems for Exchange Server.”
• Install the latest Windows updates.
• Verify the Remote Registry service is set to Automatic and not Disabled.

4. Obtain and prepare Exchange Server SE media

• Download the Exchange Server SE ISO (ExchangeServerSE-x64.iso) from the Microsoft Download Center as described under “Get Update for Exchange Server SE.”
• Optionally verify the SHA256 hash matches the documented value to ensure file integrity.

5. Perform the upgrade on the second server

• For in-place upgrade from Exchange 2019 CU14/CU15:
  • Mount the Exchange SE ISO.
  • Run Setup (GUI or command line) and follow the prompts as for a cumulative update, ensuring all prerequisite checks pass.
• For legacy upgrade:
  • Deploy the new SE server according to “Planning and deployment for Exchange Server.”
  • Move mailboxes, public folders, and services from the second 2019 server to SE.
  • After validation, remove the old 2019 server from the environment.

6. Licensing and product key behavior

• Exchange Server SE RTM does not require a new product key. The existing Exchange 2019 key continues to work after both legacy and in-place upgrades.
• A future SE cumulative update will introduce a new product key requirement; check the same documentation periodically for updated guidance.

7. Use guided tooling for the second server

• Use the Exchange Server Deployment Assistant (https://setup.cloud.microsoft/exchange) to generate a scenario-specific checklist (for example, mixed 2019/SE or hybrid with Microsoft 365) and apply it to the second server as was done for the first.

8. Reconnect with Microsoft Support for hands-on help

• Since an engineer already assisted with the first server, contact Microsoft Support again and reference the existing case number or describe that the second server needs the same 2019 → SE upgrade steps.
• If the original case is closed, open a new support request and clearly state that one Exchange 2019 server has already been successfully upgraded to SE and the remaining server requires the same treatment.

For long-term planning, Exchange Server 2019 is on an end-of-support path. The recommended on-premises strategy is to move remaining Exchange 2019 servers to Exchange SE, or use SE as the remaining on-premises server if mailboxes are migrated to Microsoft 365.

References:

• Upgrading to Exchange Server Subscription Edition (SE)
• Exchange Server 2019 and 2016 end of support roadmap
• Release notes for Exchange Server SE
• What's new in Exchange Server SE
• Exchange Server 2019 and SE prerequisites
• Announcing General Availability (GA) of Exchange Subscription Edition (SE) Release to Manufacturing (RTM)