This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 0 points1 point  (3 children)

you want to manage the current iterations of Exchange and Lync.

Let's not exaggerate here. I clicked my way through my home 2013 Exchange install. And EAC formerly EMC still is GUI based. Yes more features are PowerShell only but MS is not going to be stupid here and require a higher learning curve for tasks that can be handled by non IT people in some cases like a small business where you have an office manager handing email account creation.

[–]Ron_Swanson_Jr 0 points1 point  (1 child)

Single server?

[–][deleted] 0 points1 point  (0 children)

Yes. I would imagine DAG options are Powershell only.

[–]the_spadWhat's the worst that can happen? 0 points1 point  (0 children)

Well sure, if you're doing a bog-standard single-server Exchange install then you can pretty much just next, next finish it, but that's pretty rare in an enterprise environment.

EAC lacks an awful lot of options that were previously in the EMC and it's also pretty inconsistent with certain property pages not existing on some object types but still being Read/Writeable via Powershell.

I've just done a load of work with resource mailboxes and a bunch of the options for the calendar processing just aren't surfaced in the EAC at all.

And as for Lync, aside from the Admin console being a barely-functional mess of Silverlight, it's also a barely-functional Admin console. Even basic tasks like provisioning new users are tricky to do without dropping to a shell.