Exchange2013
2 TopicsHow to test mail flow in Exchange 2019 in an existing Exchange 2013 environment.(Solved)
Hi experts, I'm trying to complete the upgrade process from Exchange 2013(on-premise) to Exchange 2019(on-premise). I did all the steps that are explained in Best Practice for Upgradeand the Upgrade Assistant from Microsoft experts. Also, I'd like to thank you for them. But what is my question? There are 2 Exchange 2013 servers in my domain with more than 2000 users. I installed new Exchange servers and all work fine in the organization. Regarding our business, I can not take a risk and start mailbox migration directly and would like to test all things in the new environment first, like OWA, Outlook, and all related things to the new environment. I created some databases on the new servers and some users on them to test mail flow on these servers. The problem that I have is, that I can connect directly to new servers in OWA to newserver.mydomain.com and work with test users, and mail flow there works fine. But when I try to use Outlook to test, it can not find new servers. I think my issue is autodiscover record in DNS but I can not change it at the moment, because the old environment is working. When I change this record on the new servers to itself(newserver.mydomain.com) and try to configure a profile on Outlook manually and set the mail servers on the new server directly, Outlook still can not find the servers. What is your suggestion to have a test way in my case? I searched so many articles to find a way but it seems in this way, there is no solution. I don't want to create a new zone for the test, because in the External mail flow test, I will need an SSL certificate. I appreciate any help or ideas that you can provide. Kind Regards, HassanSolved4.2KViews0likes8CommentsExchange Server 2013 Upgrade to Exchange 2019 - AD Forest Function Level 2008R2
Dear Experts, I am working on upgrade my existing Exchange Server 2013 environment to Exchange 2019 and during the verification of the pre-requisites which is forest function level to be 2012 R2 whereas in my case it is 2008R2. I have some legacy application and Database servers in my environment which runs on windows 2008R2 and if i upgrade the forest level to 2012 R2 the users will not be able to login. Please correct? The question is 1- Any idea to upgrade the current environment while not upgrading the forest function level 2- Should I focus to upgrade to Exchange 2016, all pre-requisites successfully passed. BSolved1.3KViews0likes3Comments