Today we are announcing the availability of Cumulative Updates (CUs) for Exchange Server 2016 and Exchange Server 2019. These CUs include fixes for customer reported issues along with all previously ...
Updated Apr 21, 2022
Version 9.0
Blog Post
Nino_Bilic
Great to see this topic finally show up.
It's been a headache to explain 'why do we still need this Exchange server when we have EXO'. Now we can replace it with some VM with PS Tools.. which isn't great and still doesn't match the idea of 1 of Ignite sessions if I recall correctly:
"all this would be done from Azure portal", but I can see the reasoning of doing it via powershell:
first that's why it's hybrid not on-cloud and
second implementing things in portal might require more time to evaluate, process and even after implementing it in GUI, something more complex would probably still require running some CLI for the more advanced options.
2 questions for the topic:
1. Do you see any long term issues of disabling last Exchange server and formating the VM or should it be archived 'just in case'?
2. What happens in case you have domain with sub-domain, where exchange was installed in main root domain, and those are in adsync with 2 azure tenants:
domain.local with exchange installed > azuretenant1
sub.domain.local > azuretenant2
Could this be managed with 1 vm host with powershell and being able to swap between tenants or those should be separate installations? In this case I would not perform step "Active Directory clean up"
Thank you,
Regards,
Hubert