By now, you've seen a few of our Spotlight on Exchange 2010 postings. If you have, hopefully you're excited about the great work that has been going on to make Exchange 2010 the best version of Exc...
Updated Jul 01, 2019
Version 2.0
Blog Post
Overall, just frustrating. To me it seems as if MS is trying to make this appear so difficult that they can have an esier time suggesting BPOS as an alternitive to reduce complications and migration costs. Exch2007 RTM was horrible, the early adopters had a miserable time with support. WIth this new "feature" (which I have to agree with the above is only a shortcut), we can imagine the headaches of this version.
If MS cant fix the CAS scenario (so I only need to have one CAS version, as in previous version the lates was alwasy backwards compatible) it doesnt make much sense at all to migrate unless you do a big bang. It would make publishing OWA a nightmare in a mixed environment.
Personnally Id rather have Microsoft go back to the days of delivering software late but having most of the features and interporbility intact.
Just Frustrating, looks like we will stay 2007 for some time.
If MS cant fix the CAS scenario (so I only need to have one CAS version, as in previous version the lates was alwasy backwards compatible) it doesnt make much sense at all to migrate unless you do a big bang. It would make publishing OWA a nightmare in a mixed environment.
Personnally Id rather have Microsoft go back to the days of delivering software late but having most of the features and interporbility intact.
Just Frustrating, looks like we will stay 2007 for some time.