Today, I really like the move the Exchange team made from a .NET Framework/Remote PowerShell based Exchange 2010 Management Console (EMC) to the new browser/HTML5 based Exchange Admin Center (EAC).
Back in November 2011 where I heard that the Exchange team had decided to ditch the EMC as we know it and instead move to a browser based management interface, I must admit, I was a little skeptical about this move. How on earth would they manage to move all the configuration options included in the EMC to a browser based management interface? A month later, where I also saw the new EAC in what can be considered a very early beta version of Exchange 2013, I began to see the opportunities that a move to a browser based management interface would provide.
Now that I work with EAC in the Exchange 2013 RTM version, I often halt and think wow, this is a cool and much better way to do this than the approach we used in the EMC days!
Let me give you an example. Unless you used cmdlets to configure virtual directories, it was a pain to configure or look at the property page for these as you first had to select the particular server holding the respective vdir and then you had to select the tab representing the vdir.
Now check how this is done in the Exchange 2013 EAC.
Here we can select a “All Servers” view or change it to a specific server. In addition, we can select the type of vdir we want to have listed.
Unlike Exchange 2007/2010 we can also manage the EWS and Autodiscover vdirs from here plus select multiple vdirs simultaneously.
Let’s face it, the move to EAC has made it much easier and quicker to do configuration via a management interface. Besides that, it’s also much easier to add new configuration options.