Thanks to you, I now know there is not but, IF there were such a thing I would want to know how to access it – that’s all I was saying, in a nutshell. That’s all I meant – is there a “thick client, non-Web version of EAC,” so to speak. You’ve clarified there is NOT a separate “thick” EAC piece. So, that was all I was referring to in case I might be missing out on some “thick” piece that may have more features than EAC. Obviously, you’ve clarified and, of course I meant: “IF there is” a separate piece of Exchange management… For example:īasically, a number of tools in the past have come in “thick” (non-web) client as well as “thin” (web) client – sometimes with the “thick” piece having a few more features than the “thin” piece. Paul, please *ALWAYS* explain your “setup command line.” I know we are all geniuses, ? but nothing in your command line says “Install ” – I’m sure it’s maybe the “/r:t” or something – but, when you put out a cryptic, abbreviated command, it helps “us geniuses” when you are kind enough also to say, “Ok, this option means blah, this other parameter means blah-blah,” etc. I probably misunderstood – and they are one and the same.
Management Tools – where is the distinction and how do I get to the full “non-MMC” version of Exchange Management Tools – NOT the EAC the real live ‘tools ’ which are supposed to be a separate animal – right? That’s all well and cool BUT, if there’s a difference in EAC vs. They appear to be installed and you said we no longer use MMC. So… how on earth do we get to “Exchange Management Tools?” HERE is the ‘real’ UNC/URL – (where “your-2013-exch-server” is the name of the server you are trying to manage)Īpparently, it has something to do with running multiple versions of Exchange – so you have to specify the “ExchClientVer=15” piece, to make it happy and go to the true 2013 EAC.ĪNYWAY, I digress – above is the method to get to EAC. We know how to get to EAC – and, for those asking, MS left a “bug” (omission) in the steps: In Microsoft documentation, it says you can use “EAC” *OR* “Exchange Management Tools ” which would indicated they are two separate animals (though granted, no more MMC as the catalyst to get to them). local access can be left scratching their head with inconsistent results. A user who doesn’t 100% understand the nuances of PSRemoting vs. I don’t know why this isn’t stressed more by Microsoft or other blogs. Since the return is objects, Exchange knows to remove the SMTP:, etc, prefix from the addresses and just display the values. You’ll see output as objects which can further be manipulated and piped. Running (get-mailbox ).emailaddresses.smtpaddress won’t return anything.Ĭonnect to Exchange using EMS (either on the server or a machine with tools installed) and run the same command. You’ll see the output is a string and includes prefixes.
When PSRemoting to an Exchange server run (get-mailbox ).emailaddresses | gm. I finally realized that results were being translated on return receiving string data instead of Exchange objects. I would run into odd scenarios where commands didn’t run as I expected unless I was on the server but never could figure out why, especially for double dotted notation or piped commands.
I wanted to mention that it wasn’t very clear WHY I needed to install management tools when I could just remote shell to a server.
To connect to a remote Exchange 2013 server using PowerShell you need to be running Windows 7 SP1, Windows 8 (or higher), Windows Server 2008 R2 SP1, or Windows Server 2012 (or higher).įrom a PowerShell console run the following commands, using the FQDN of a Client Access server in your organization: However you can still install the management shell on a workstation or server if you prefer. Remoting is simpler because it requires no management tools to be installed on the computer that you are connecting from. In this video I take a quick look at the Exchange Admin Center.įor PowerShell-based administration we can still use the Exchange Management Shell, or just use PowerShell remoting. Instead, the management console has been changed to a web-based management portal called the Exchange Admin Center. With the release of the Exchange Server 2013 a lot of people in the Exchange community are talking about the big changes to the management tools.Įxchange Server 2013 no longer uses the MMC-based management console that we became familiar with in Exchange 2007 and Exchange 2010.