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.
Exchange Server 2013 no longer uses the MMC-based management console that we became familiar with in Exchange 2007 and Exchange 2010. Instead, the management console has been changed to a web-based management portal called the Exchange Admin Center.
In this video I take a quick look at the Exchange Admin Center.
For PowerShell-based administration we can still use the Exchange Management Shell, or just use PowerShell remoting. Remoting is simpler because it requires no management tools to be installed on the computer that you are connecting from. However you can still install the management shell on a workstation or server if you prefer.
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).
From a PowerShell console run the following commands, using the FQDN of a Client Access server in your organization:
PS C:> $session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://ex2013srv1.exchangeserverpro.net/PowerShell -Authentication Kerberos PS C:> Import-PSSession $session
If you need to provide different credentials for the connection use the following commands instead, and enter the credentials in the logon box that appears:
PS C:> $creds = Get-Credential PS C:> $session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://ex2013srv1.exchangeserverpro.net/PowerShell -Authentication Kerberos -Credential $creds PS C:> Import-PSSession $session
You can exit the remote session by running the following command:
PS C:> Remove-PSSession $session
If you’d prefer to install the management tools on the server, run the following setup command in an elevated command prompt from the folder containing the extracted Exchange 2013 setup files. This example is from a Windows Server 2012 R2 server.
C:Adminex2013cu5>setup /m:install /r:t /InstallWindowsComponents /IAcceptExchangeServerLicenseTerms
Welcome to Microsoft Exchange Server 2013 Cumulative Update 5 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for
installation.
Languages
Management tools
Performing Microsoft Exchange Server Prerequisite Check
Configuring Prerequisites COMPLETED
Prerequisite Analysis COMPLETED
Configuring Microsoft Exchange Server
Preparing Setup COMPLETED
Stopping Services COMPLETED
Copying Exchange Files COMPLETED
Language Files COMPLETED
Restoring Services COMPLETED
Language Configuration COMPLETED
Exchange Management Tools COMPLETED
Finalizing Setup COMPLETED
The Exchange Server setup operation completed successfully.
Hi Paul
i want to configure second virtual directory mail1.domain.com already we are using mail.domain .com
for failover my internet line user can shift to 2nd A record mail1.eastdeltasa.com.
how can i configure in exchange let me know please
Hi Paul,
I am having problem with Exchange 2013 ActiveSync. Only one active mobile client device wiped remotely every three weeks. All of the mobile device using same default mobile policy. All other active mobile device remain un-wiped as per policy. I could not fix the issue, I need some assistance to fix this issue
Hello sir,
I installed and configured step by step as you described, but when i came to web-based management portal (Exchange Admin Center) and entered my domain, username(administrator) and password, it displays “your mailbox cant be accessed using the address you entered. To obtain the correct address, please contact your helpdesk.” what shall i do?
Hi Paul,
Is there way to connect exchange server 2013 power-shell from different organization network. Or can we install 2013 management tools in desktop to connect other organization exchange servers.
You can use PowerShell remoting to connect to any Exchange server. You just need to know the name or IP address and be able to connect through any firewalls. The PowerShell steps are here:
https://technet.microsoft.com/en-us/library/dd335083(v=exchg.160).aspx
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. 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 finally realized that results were being translated on return; receiving string data instead of Exchange objects.
When PSRemoting to an Exchange server run (get-mailbox ).emailaddresses | gm. You’ll see the output is a string and includes prefixes. Running (get-mailbox ).emailaddresses.smtpaddress won’t return anything.
Connect to Exchange using EMS (either on the server or a machine with tools installed) and run the same command. You’ll see output as objects which can further be manipulated and piped. Since the return is objects, Exchange knows to remove the SMTP:, etc, prefix from the addresses and just display the values.
I don’t know why this isn’t stressed more by Microsoft or other blogs. A user who doesn’t 100% understand the nuances of PSRemoting vs. local access can be left scratching their head with inconsistent results.
Paul
Can you Manage the Exchange servers from the Server Center operations manager tools?
Pingback: Microsoft Exchange Server 2013 – Design, Deployment and Migration – MS EXCHANGE TIPS
We have our mailboxes moved to Exchange Online. We are still going to manage AD from on-prem. We are looking to repurpose the Exchange server. Can I load Exchange management tools on to another NON Exchange Server?
If so what do I need to do to install the tools on the alternate server?
You can install the tools anywhere you like, but you still need an Exchange server running.
Can you install the Management Tools for just help in Office 365 Hybrid Management if you don’t have an Exchange 2013 ?
I have a client that did a hybrid move into 365 from an Exchange 2010 setup but they wanted to decom the 2010 server and just have the management tools available for easier user management.
What would you suggest in this situation? Keep 2010 management tools installed somewhere? Install 2013 management tools somewhere? do I need a CAS to connect to? or how would this work?
No, the on-prem management tools require an on-prem server to connect to. In your client’s situation it is normal to retain an on-prem server for management purposes.
I had to say it but this doesn’t feel like forward movement… The speed of this interface is greatly hindering on any large size corporation. With a large enough forest you can wait upwards of a minute for it to populate at each interface. For instance when adding a new users email you have to do them one at a time and lack any mass add feature. So when adding them you have to wait for it to populate all users each time before it allows you to search the users. And on top of that you can’t navigate through your AD structures to limit the list. I find it be wasteful of my time at best.
User powershell commands for mass adds.
Pingback: Configuring Database Copies in an Exchange Server 2013 Database Availability Group | Blog Storm
Pingback: Adding Database Copies in an Exchange Server 2013 DAG
I’m still confused. 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).
We know how to get to EAC – and, for those asking, MS left a “bug” (omission) in the steps:
HERE is the ‘real’ UNC/URL – https://your-2013-exch-server/ecp/?ExchClientVer=15
(where “your-2013-exch-server” is the name of the server you are trying to manage)
Apparently, 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.
ANYWAY, I digress – above is the method to get to EAC.
So… how on earth do we get to “Exchange Management Tools?”
They appear to be installed; and you said we no longer use MMC. That’s all well and cool; BUT, if there’s a difference in EAC vs. 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?
I probably misunderstood – and they are one and the same. Tell me if I’m wrong – I usually am. Thanks!
p.s. Paul, please *ALWAYS* explain your “setup command line.” I know we are all geniuses, 😉 but nothing in your command line says “Install [management tools]” – 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.
“Exchange management tools” is a general term to refer to the various methods of managing Exchange Server 2013. The EAC is one of those. The shell is another. The Toolbox is another. The video does mention that.
The extra URL parameter you mention is not a bug. It is relevant for co-existence scenarios. It is covered in their FAQ (https://technet.microsoft.com/en-us/library/jj552409(v=exchg.150).aspx) as well as their migration guidance.
I don’t really know what “full non-MMC version of Exchange Management Tools” you’re thinking of.
Obviously, you’ve clarified; and, of course I meant: “IF there is” a separate piece of Exchange management… For example:
Basically, 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. 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.
You’ve clarified there is NOT a separate “thick” EAC piece. That’s all I meant – is there a “thick client, non-Web version of EAC,” so to speak. 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.
So, it looks like “EAC” is the only option for managing Exchange 2013 (along with, as you stated, Powershell and so forth); i.e., EAC “web client only;” no more thick console.
And I do consider it a “bug,” regarding them not mentioning the distinction between the URL needed to get to EAC (in a co-existence) situation; but, to each his/her own. Yes, they did mention it somewhere esle; but, NO, not in the standard “Microsoft upgrade steps” that I followed in my own upgrade – unless it was buried in some “far offshoot” of a link down which I didn’t travel.
Thanks again for so perfectly answering my question.
Hi Paul!
I bet you’re getting tired of my questions! I’m asking this here because I can’t find the answer online.
Is it possible to create an OWA website? Or does have to be a VD? What I’m trying to do is create 2 separate websites, one for OWA, and one for EAC.
Thanks!
OWA is a virtual directory. ECP (which hosts the EAC) is a virtual directory. Neither of them are “websites” in the sense of IIS.
It isn’t clear what the actual outcome is that you’re trying to achieve, or why you’re trying to do it.
Hi Paul,
Thanks for the reply. I was just an idiot who didn’t know how exchange worked with these VDs. I did some reading and now I understand.
What I was trying to achieve is to create 2 dns records, one that points to OWA, and one to ECP. and since they are both virtual directories it wouldn’t have worked. I thought I could do it if I created 2 separate websites. But turns out they always have to be a virtualdirectory.
I’ll check create redirect rules to get it working. the reason I’m doing this is for when a user types admin.domain.com it redirects to ECP, and when they type mail.domain.com it takes them to owa.
Thanks for all your help!
I installed the CAS and its working now.
Hi Paul,
I’m getting a 404 error when I try to access the management console. I only have the mailbox role installed is that why? I tried a couple of fixes from MS, but it didn’t really do anything.
I tried this command in managementshell “set-Owavirtualdirectory -identity “E15MBXowa (Exchange Back End)” -WindowsAuthentication $True -Basicauthentication $false -Formsauthentication $false” It didn’t work till I changed the identity to my server, which I believe how it’s done, but everyone else online posts it with E15MBX.
Then I tried this command “Set-EcpVirtualDirectory -Identity “E15MBXecp (Exchange Back End)” -WindowsAuthentication $true -FormsAuthentication $false” and instead of the 404 error I;m getting a failed to map path.
Any help would be appreciated! thank you for the great work!
Poor I’ll stay in 2010 until Microsoft not give new nice console to exchange not based on IE !!! 🙂
The EAC isn’t based on IE. You can use it with any web browser. Or use PowerShell like you’re already used to using with Exchange 2010.
Thanks for the information! Hopefully this will allow my scripts to make use of Exchange cmdlets in addition to the standard Powershell stuff.
Is there a EMS/PS command that you can run on a machine (not exchange server) to tell what version of Exchange tools (2007 / 2013) are installed locally?
I just look in Add/Remove Programs (or Programs and Features on newer OSes). Is that what you want?
Pingback: How to Install Exchange Server 2013
Hello Paul,
I’m trying to log in Exchange Admin center but instead of getting “Exchange Admin Center” on the credentials page I’m getting “Outlook Web App”.Any clue?
Thanks.
If I’m not wrong the URL should be https://FQDN/ecp?
Yes. Have you tried logging in and seeing whether OWA or EAC loads?
Hey Paul,
Yeah I logged in and it seems I’m in the OWA interface not EAC.
Thanks for some other excellent post. The place else may anyone get that kind of information in such an ideal manner of writing?
I have a presentation subsequent week, and I’m at the look for such info.
Pingback: Exchange Server 2013 RTM Cumulative Update 1 (CU1) Released
what about roles ? can you explain some one what are all the roles using for exchange2013.
Hi Shibu, you can read about the Exchange 2013 server roles here:
https://www.practical365.com/exchange-2013-server-roles
Paul,
What about Unified messaging and the edge transport roles?
thanks
That question is answered here:
https://www.practical365.com/exchange-2013-server-roles
I personally like the move away from the console as it was a pain having to update management servers, tools published via Citrix, etc.
One thing I loved about the console in 2010 SP2 was the fact you could type in values and view the powershell code before even commiting the values. Was great for documenting things.
Is this still possible with the web console? Can you view the powershell code before you commit anything as with 2010 SP2?
Hi Paul,
2 quick questions, 1 related to this video! You may want to move this question away from this topic?
1. What do you feel that the main drivers will be for customers/users to move from their 2007/2013 platforms? apart from general Microsoft support. What, in your opinion, will be the key selling points to 2013.
2. What software do you use to produce your videos?
Keep up the good work, appreciated here in the UK.
Regards,
David
p.s Ashes tickets bought yesterday!!!!
New twitter account: msexchangeuk
1) 2013 (and 2010 for that matter) have much better HA/SR capabilities than 2007 or earlier, and can save money due to the lower storage costs while also providing benefits such as large mailboxes. There are also a long list of improvements and new features such as DLP, builtin anti-malware, FAST search, deeper integration with products such as Lync and Sharepoint, and more. Microsoft publishes a lot of “whats new” material but some of the technical meat will emerge only as more and more customers deploy it and talk about it.
2) I use Camtasia from Techsmith.
Pingback: Exchange Server 2013 Room and Equipment Mailboxes
hi,
what’s the benefit for Microsoft while removing Exchange management console…?
Not sure I understand the question.
It makes sense to detach the Exchange management tools from a component like MMC, especially given some of the issues that have been caused with the Exchange management tools when other windows components were updated (the IE bug for example).
Pingback: Exploring Transport Rules in Exchange Server 2013
Pingback: Gwen Demulder » Blog Archive » Exchange 2013
interesting! atleast its will be quicker than MMC!!
i noticed that it said office 365 in the top corner.. is that because MS are forcing you down the Hybrid route?
i also see they have shelved the Hub transport role, is there still Transport Rules available?
We’re not being forced down the hybrid route, they’re just making management of hybrid scenarios easier.
Transport Rules are still available. They’re in the Mail Flow section under “Rules”.
Cheers Paul!
How Can DNS Server setup
Palsse Help Me
Hi Paul,
Really Nice. You are my Hero.