Microsoft
MicrosoftI appreciate you may not have this information yet, but think about all your customers that have started planning the work that is going to be required to perform at least 1 but perhaps 2 exchange migrations/upgrades which we are considering. Put the time constraint that will also exist if you release the software in Q3 and do not move the end of support date - 14/10/25, you will have a lot of business's frantically performing migrations or in-place upgrades. The timelines are very tight. I think Microsoft can be considerate of this and extend the Support end date to at least the end of the year.
Please can you share your thoughts on this and potential dates when you will have a release date to help with the planning.
Thank you!
Paul
I Agree with this comment. Our environment is not even upgradable due to legacy software preventing us keeping us from moving forward to Forest functionality level 2012 R2. for us the upgrade is nearly almost out of the question. has anyone tested to upgrade to 2019 itself ? it's a requirement to be 2012 R2 functionality level at minimum. i'm sticking to 2016 CU 23 long term. Spinning a lab to see what breaks during Raising of Functionality level.
