When I wrote about how the Exchange 2013 Administration Center (EAC) simplifies the management of Database Availability Groups (DAGs), Scott Schnoll, that well-known and much-travelled evangelist of Exchange high availability, pointed out quite correctly that none of Exchange’s management tools include any business logic whatsoever as all depend on calling whatever Exchange Management Shell (EMS) cmdlet is appropriate to manipulate information an object. This has been the case since Exchange 2007 embraced PowerShell and launched Exchange on the path that it has since followed. Not being picky at all, my sources within the EAC team tell me that they run EMS in a slightly different manner than an administrator does through an EMS window. It’s all to do with the way that browsers send commands to servers. At least, that’s what I remember from a lunch-time conversation at MEC in Orlando. Or maybe I was too concerned with eating to remember accurately. In any case, Scott’s point is well made.
.jpg?width=700&auto=webp&quality=80&disable=upscale)
