Exchange 2019 Migration
3 TopicsDAG Exchange 2016 -> 2019 Migration, Certificate Question
Hello folks! I have a question regarding a migration from an existing Exchange 2016 2-Node DAG to an Exchange 2019 2-Node DAG (O/S Server 2022) and the Certificate for Exchange Services (mapi,ecp,oab,ews and so on....). The existing Exchange 2016 server both use the same RSA 2048bit certificate. I´m considering whether to issue an ECDA P-384 certificate for the new Exchange 2019 servers. This certificate would also serve as the basis for the later upgrade to Exchange SE. Could the different certificates cause problems during the migration?Solved108Views0likes1CommentExchange archive mailbox migration license issue
Hi all, I have a situation where my environment is in a hybrid state with users ready to migrate. Some users are over 100GB but less 240GB, the Microsoft article on migrating large mailboxes says i have to provision the cloud archive first, but the documentation on this says i need a license. What's confusing me is if assign a license before they migrate this creates a whole new mailbox and all sorts of screwy thing happen and you have to clean up etc.. so, you instead assign the license after the migration.., but the cloud archive docu. is saying I need to assign a license for the cloud archive first. Has this changed where i can create the Cloud archive on-prem and migrate without needing a mailbox? am i missing something?202Views0likes1CommentExchange 2019 Outlook Not connecting
Hi, I have migrated all mailboxes from exchange 2016 to exchange 2019. Shutdown 2016, but outlook 2016 still trying to connect to old exchane 2016 Server. If i do a outlook email connectivity test it shows old MAPI URL. If I do another test It shows New one. I am confused how it is getting old mapi url even though the server is shutdown. Need your valuable assistance. My autodiscover url is same for both old and new server.1.1KViews0likes0Comments