E2K7 set up is largely accomplished using commandlets. While it is far more powerful than E2K3, setting it up, especially in an environment where co-existence with E2K3 is to be maintained, requires a thorough understanding of a number of technologies - DNS, managing UCC Certs, domain redirects and much more, in addition to Exchange and its entire architecture.
It is not for the inexperienced to set up. If an organization has complex messaging needs, and or requires the universal messaging capabilities inherent to E2K7, then I would encourage people to seek out a solid Exchange hosting partner, or a partner that can help you set it up. We do both and compete with Microsoft and others in this context. I've written about our set up here, http://blog.libertech.net/blogs/lketchum/archive/2007/07/06/hidden-exchange-2007-outook-2007-connection-tests-and-monitoring.aspx as you can see from my article at the time, it was not clear to me what Microsoft was trying to do. Now I know... they wanted to keep all but the most capable out of the channel. No ding on Latch's guys, but I'm not surprised they had a tough time. We've helped a great many people deploy it and so many are too inexperienced to have succeeded with pre E2K7 SP1 installs. I understand it is far easier now.
|