Managing The New Exchange

re: Managing The New Exchange

Steve — Mon, 05 Nov 2012 19:06:29 GMT

EAC JUNK, Exchange 2013 JUNK, Microsoft is going down hill.

put the EMC back, why mess with a good thing, web based management sucks

re: Managing The New Exchange

Comps Consulting — Sat, 13 Oct 2012 12:45:04 GMT

Way to go Microsoft! You couldn't have ruined a perfectly good administrative interface (EMC) anymore than what you have done by changing to the EAC. This new interface sucks! I'm very disappointed in this Preview. I hope the decision makers take a poll and ask their consumers (us) what they want, instead of craming this crappy web based interface down our throats without at least giving us a choice or say so in the matter. Same thing with Windows 8 and Server 2012. Why the hell would you get rid of the start menu? Bill, please come back, we need you !!!!

re: Managing The New Exchange

DavidJCarr — Thu, 04 Oct 2012 13:15:32 GMT

Why was the decision made to use a web based interface for managing Exchange vs a MMC?

re: Managing The New Exchange

Ryan — Tue, 04 Sep 2012 20:12:59 GMT

Few questions, will we be able to do the following within EAC, or will we be forced to use remote PowerShell?

- Full and/or Send As permissions?

- Mail Forwarding

- Mailbox Creation

re: Managing The New Exchange

Kestutis — Mon, 27 Aug 2012 13:14:25 GMT

Addionally, it seems that Exchange 2013 console (EAC) drops PowerShell learning tools and context-sensitive menus... In OWA 2013 we can find context-sensitive menus, but not in EAC... Hopefully EAC will include these features in RTM!

re: Managing The New Exchange

Neil — Tue, 14 Aug 2012 17:41:39 GMT

Will there be support for MAPI in Exchange 2013

re: Managing The New Exchange

Jarrett — Mon, 13 Aug 2012 21:56:03 GMT

Bad move. Here's what I read: "We didn't have time to get our act together, and we're being pressured into moving to a kludgey web-based system so we can claim integration between Lync, Exchange and SP, so we ripped out a bunch of stuff we didn't have time to do right. Go team!"

re: Managing The New Exchange

Greg Taylor [msft] — Mon, 13 Aug 2012 18:43:09 GMT

@ Marius and Arjen - There are no major changes planned to support multi-tenancy using the on-prem product in 2013 - the strategy will closely follow what we did for 2010.

So no, we will not be building in features to create tenants and organizations for those who want to use the on-prem product to provide hosted Exchange.

There are some differences in how some features work in 2013, and there are some improvments we have made which will be the subject of a future post at some point I'm sure, and the hosting guidance will be updated for 2013, but for now you should think of multi-tenancy with 2013 as similar to that with 2010 SP2 and ABP's.

Greg

re: Managing The New Exchange

Andrew Saucci — Mon, 13 Aug 2012 12:52:36 GMT

It looks as though EAC is a web browser-based interface. What a horrid mistake. I have yet to see a browser-based interface that was any good at all, much less better than an MMC equivalent. Browser-based interfaces are inherently slow, klunky, and awkward. Why is inferior stuff replacing what little good software is out there?

re: Managing The New Exchange

Frosty — Mon, 13 Aug 2012 01:18:31 GMT

Until such time as MS fixes bugs such as Outlook 2010 having hundreds and thousands of Sync Errors, I won't be paying any attention to any future functionality chest-beating; fix the bugs first please! My company will be staying on Exchange 2007 until this sync issue is fixed. If we get to the point where we need to upgrade and it is not fixed, we will abandon MS altogether.